aboutsummaryrefslogtreecommitdiffstats
path: root/arch/arm/plat-omap/include
Commit message (Collapse)AuthorAgeFilesLines
* [espresso] OMAP4: UART: add DEBUG_LL support for espressoZiyan2016-04-301-0/+3
|
* OMAP: process tput request made before PM init.John Grossman2012-10-261-0/+12
| | | | | | | | | | | | | Because driver load order is uncertain, drivers could request bus throughput constraints before the PM subsystem had initialized. The constraints would be recorded, but would have no effect on the actual L3 clock. This change suppresses attempts to set L3 scaling before PM has initialized, and causes the PM subsystem to apply any pending bus throughput constraints immediately after it has initialized itself. Change-Id: If2a1f5315b8c1b084e4e4b3ce8e6844d92dd59b6 Signed-off-by: John Grossman <johngro@google.com> Signed-off-by: Ruslan Bilovol <ruslan.bilovol@ti.com>
* board: tablet: usb: coexisting both HSIC and PHY in single kernel binaryRuslan Bilovol2012-10-051-0/+1
| | | | | | | | | | | | | Added kernel command line parameter 'omap4_tablet_uses_hsic' that allows to have both HSIC and PHY in single kernel binary for Tablet2, this allows to enable HSIC changing only kernel command line Usage: pass 'omap4_tablet_uses_hsic' to kernel through command line in case of HSIC modifications on Tablet2. Do naot apss it in case of traditional PHY usage. Change-Id: I0c50a1af18a26b06ca3957b21c7fa707d870428b Signed-off-by: Ruslan Bilovol <ruslan.bilovol@ti.com>
* ehci: omap: add HSIC disconnect-reconnect functionalityRuslan Bilovol2012-10-051-0/+7
| | | | | | | | | | | Added HSIC disconnect-reconnect functionality using AUX pin. Disconnect or reconnect may be initiated by Device (using AUX pin) as well as by Host (through sysfs entries). Reimplemented .hub_status_data and .hub_control functions, implemented .disconnect and .reconnect ones. Change-Id: If697c06a4ef39ccaabb7c96dbcc0c597e7780515 Signed-off-by: Ruslan Bilovol <ruslan.bilovol@ti.com>
* ARM: OMAP4: Tablet: Add new board revisionVolodymyr Riazantsev2012-09-211-1/+3
| | | | | | | Adding new (2158-004) board revision for Tablet2. Change-Id: I9e3c914f8c79d8b29cd1ebb76509210ecccb33e2 Signed-off-by: Volodymyr Riazantsev <v.riazantsev@ti.com>
* OMAP4: USB: remove unused function twl6030_set_phy_clkRuslan Bilovol2012-09-121-1/+0
| | | | | | | | This function is redundant and not used anywhere. Remove it and change associated code accordingly Change-Id: I06ba222429cfe89a401b426a211d1752e646450a Signed-off-by: Ruslan Bilovol <ruslan.bilovol@ti.com>
* OMAP: clock: Add dummy round_rate and set_rate functionsTaras Kondratiuk2012-09-041-1/+2
| | | | | | | | | Add functions which are going to be used by dummy virtual clocks: long clk_dummy_round_rate(struct clk *clk, unsigned long rate) int clk_dummy_set_rate(struct clk *clk, unsigned long rate) Change-Id: I9bb1e886888a117548d62ef2edd9598bce2723e6 Signed-off-by: Taras Kondratiuk <taras@ti.com>
* omap: rpres: add api to lookup max frequency for a remote deviceJuan Gutierrez2012-08-091-0/+2
| | | | | | | | | | | | | | | | A new public function, rpres_get_max_freq, is added to perform a lookup for the maximum supported frequency from the OPP table for a remote processor device. This API can be used by the remote resource layer in sharing this data to the remote processor application code for performing power related policy decisions. Change-Id: Idbea6884fa47b3bd1f000b6f696fbbcf7036a6ee Signed-off-by: Suman Anna <s-anna@ti.com> Signed-off-by: Juan Gutierrez <jgutierrez@ti.com> Signed-off-by: Paul Hunt <hunt@ti.com> Signed-off-by: Fernando Guzman Lugo <fernando.lugo@ti.com>
* OMAP4: Add platform data to support HDMI default displayMuralidhar Dixit2012-07-171-0/+2
| | | | | | | | | Adding new platform data to support HDMI default display feature. HDMI platform data is selected if HDMI is selected as default display in boot args. Change-Id: Ic5968c4b293e2a1edff61490b2deab2e4af6dbcb Signed-off-by: Muralidhar Dixit <murali.dixit@ti.com>
* OMAP4: DPLL cascading: Recalibrate Baud Rates for UARTs when the DPLL freq ↵Ruchika Kharwar2012-06-181-0/+5
| | | | | | | | | | | | | | | changes This patch attached the callbacks to DPLL framework to recalib. the baud rates of all the UART's base on the functional clock chnages in the DPLL cascading Low Power mode. [Andrii Tseglytskyi <andrii.tseglytskyi@ti.com>: Ported and adapted to p-android-omap-3.0] Change-Id: If60b3287934f8d780b72b3aa68cbeccd52f99658 Signed-off-by: Ruchika Kharwar <ruchika@ti.com> Signed-off-by: Andrii Tseglytskyi <andrii.tseglytskyi@ti.com>
* omap: common: add kernel API to query RAM sizeDevaraj Rangasamy2012-06-161-0/+4
| | | | | | | | | | | | Add kernel api omap_total_ram_size() to query the exact size of physical ram available in system. Its derived from mem arguments passed to kernel via bootargs and is expected to be used by board files and drivers. Note: omap_init_ram_size() has to be invoked at the earliest during board init to update memory size. Change-Id: I8511fd66ba51343bc64a58db04994af930cbe709 Signed-off-by: Devaraj Rangasamy <dev@ti.com>
* OMAP4470: gcx: Add device_scale, bandwith interface functions.Oleg Matcovschi2012-06-011-0/+4
| | | | | | | | Extend device platform data to support device scaling and querying L3 bandwidth. Change-Id: I7e926767ba727bacc0f13543425d43225f815ccd Signed-off-by: Oleg Matcovschi <oleg.matcovschi@ti.com>
* Merge branch wuxga/p-android-omap-3.0-dev into p-android-omap-3.0-devDima Svetlov2012-05-182-0/+36
|\ | | | | | | | | Change-Id: I695b59aeccd2e5cb5a50c6fc734c5d54795f5615 Signed-off-by: Dima Svetlov <svetlov@ti.com>
| * OMAPDSS: DSSCOMP: Added support for back bufer copy for ext displaysSunita Nadampalli2012-05-171-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | In order to decouple the LCD FB and the ext display buffers, sDMA copy based solution is implemented in dsscomp. This patch adds the support for parsing ION handles for buffer addresses and copying FB into user provide buffers (for ext display cloning). Change-Id: I84cfa249e86b863aef9fd9685e1854649f25afc8 Signed-off-by: Sunita Nadampalli <sunitan@ti.com> Signed-off-by: Lajos Molnar <lajos@ti.com> Signed-off-by: Dima Svetlov <svetlov@ti.com>
| * OMAP2: generic Android display configuration setupLajos Molnar2012-05-151-0/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added android_display methods to allow runtime configuration of Android display resources, such as: - FB0's vram is dynamically calculated from the number of buffers SGX requires in VRAM (swap chain and/or composition buffers), and the FB0 display size. - OMAP VRAM is calculated from FB0's vram need + any other specified FB's vram. (If command line is used to specify FB vrams, omap vram must also be specified.) - TILER1D area reserved for use as DSS MMU by DSSCOMP is calculated from default display size. It can be overriden by board file. - TILER2D carveout size is reduced by TILER1D area (if coallocated with TILER2D) and by the TILER2D SGX buffers (swapchain and/or composition buffers) - nonsecure TILER2D carveout size is set to the backpages needed by TILER2D SGX buffers. All of this is coordinated by omap_android_display_setup. It takes pointers to the DSS board info, FB platform data, and optionally to the ION, SGX and DSSCOMP platform data. It should be called in board_reserve before omap_ion_init. If SGX data is provided, it is set as the SGX platform data for FB0. Similarly, if DSSCOMP platform data is provided it is also set. This can be used to set a preferred tiler1d slot size. If ION platform data is provided, it is updated with the required tiler2d carveout sizes. NOTE: To maximize TILER2D space, the TILER1D area reserved for android display is not aligned to 1MB, but is aligned to 32 pages as the smallest 2D allocation needs a 32-page band. We further reduce TILER2D space by the container space lost by the SGX buffers, which may be larger than the actual backpages bneeded for the SGX buffers. Therefore the sum of secure + nonsecure + 1D tiler space may be smaller than the available container space. Ported to latest SGX DDK by Dima Svetlov. Change-Id: I5d8858c38efd842452994e3a3476463083d200d7 Signed-off-by: Lajos Molnar <lajos@ti.com> Signed-off-by: Dima Svetlov <svetlov@ti.com>
| * OMAPDSS: DSSCOMP: Export dsscomp_set_platform_dataLajos Molnar2012-05-151-0/+4
| | | | | | | | | | | | | | | | | | This is used by android-display to set up default tiler1d slot size. Change-Id: Ic6fe49b9338d8ce41c2ac2b444d8ef018ee5fc7a Signed-off-by: Lajos Molnar <lajos@ti.com> Signed-off-by: Dima Svetlov <svetlov@ti.com>
* | omap: rpmsg: bump to max freq while booting remote processorMiguel Vadillo2012-05-171-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reduce the remote processor booting time by bumping to the max frequency. This is achieved by putting in constraints before the loading of the remote processor. The latter is known through the RPROC_PRELOAD notification. Once the remote processor has reached a certain point, it would send a message, RP_MSG_BOOTINIT_DONE via mailbox to notify the host that the remote processor has completed the basic boot and initization. The constraints are released upon receipt of this message. They are also released in case of an error during loading. NOTE: The current implementation used tput api for ipu since freq scale api is not supported directly yet. Change-Id: I1fe936087f00872756c7b532ee58d923e695ff28 Signed-off-by: Miguel Vadillo <vadillo@ti.com> Signed-off-by: Fernando Guzman Lugo <fernando.lugo@ti.com> Signed-off-by: Subramaniam C.A <subramaniam.ca@ti.com> Signed-off-by: Chandra Sekhar.Anagani <chandu@ti.com> Signed-off-by: Suman Anna <s-anna@ti.com>
* | remoteproc: fix obsolete comment about memory_mapsDavid Schleef2012-05-171-1/+0
| | | | | | | | | | | | | | | | | | | | memory_maps in remoteproc platform data has been replaced with memory_pool, but the comment still remained. It has been cleaned up. Change-Id: Iae78c0b8e8d4caccce2fc0248b89a9d18f8d7cca Signed-off-by: David Schleef <ds@ti.com> Signed-off-by: Suman Anna <s-anna@ti.com>
* | OMAP4: IRQ: Fix OMAP44XX_IRQ_CPUIDLE_POKE0 definitionGrygorii Strashko2012-05-151-1/+1
|/ | | | | | | | | | | According to OMAP4470 TRM the MA_IRQ_60 is busy for L3_STAT_ALARM_IRQ L3 NoC statistics collector alarm interrupt. The MA_IRQ_106 is reserved in all OMAP4 chips, so it's selected for using as OMAP44XX_IRQ_CPUIDLE_POKE0. Change-Id: Iba7f727035c71db009defe684a66fb8c58ee3f93 Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
* gc320: determine whether context was lost and reset gpuTony Lofthouse2012-05-101-0/+1
| | | | | | | | | If the context is lost this means BB2D_RST is asserted and we will need to take appropriate action. This assumes that resetting the GPU is the limit of this. There could be more. Change-Id: I71ec274e6dd46d0b22c0b1f708eaa3303bef824d Signed-off-by: Tony Lofthouse <a0741364@ti.com>
* ARM: OMAP4: USB: Update workaround for USB errata i719Jon Hunter2012-05-071-0/+3
| | | | | | | | | | | | | | | | | Due to USB errata i719 the USB host save-and-restore context can be corrupted if the device enters off mode more than two times without enabling the USB host controller in between. The corruption is occuring during the software save of the USB context which occurs on entry to every off mode attempt. To avoid this problem only save the USB context if the USB host controller has been enabled since the previous off mode attempt. We do not need to save the USB context on every entry to off mode if the USB controller has not been enabled. Change-Id: I67e07963679af6494ef289eb10db09c0162d6f00 Signed-off-by: Jon Hunter <jon-hunter@ti.com> Signed-off-by: Volodymyr Riazantsev <v.riazantsev@ti.com> Signed-off-by: Ruslan Bilovol <ruslan.bilovol@ti.com>
* gcx: use pm_runtime calls to obtain omap power resources.Tony Lofthouse2012-05-031-1/+0
| | | | | | | | | | | These are the proper PM apis to use for GC320. Remove explicit usage of the bb2d fclk. Remove idle wait check. Any handling of prcm wait states should be done in the hwmod if needed in the future. Change-Id: I16a53e98fa4c1efca512b7506e2fe9934e9b185f Signed-off-by: Tony Lofthouse <a0741364@ti.com>
* gcx: driver cleanup.David Sin2012-05-031-0/+1
| | | | | | | | | Remove unused flush pages function. Replace hardcoded irq value with proper method. Remove hardcoded 2d base address & direct allocation. Change-Id: I79c1089db935bfddc17e85f761113e3f709738b6 Signed-off-by: David Sin <davidsin@ti.com>
* omap_gcx: enhance to provide omap operationsTony Lofthouse2012-04-201-0/+26
| | | | | | | | | | | In order to provide the gccore driver a function to check the state of the prcm, we will put a function pointer in the gcx platform device. The previous platform device entries were not used by the gccore driver. Change-Id: I7e3f1755261d99fe022964a2a26db6ba7f42092e Signed-off-by: Tony Lofthouse <a0741364@ti.com>
* omap: mailbox: add pm constraint field to mbox structureSubramaniam C.A2012-04-181-0/+1
| | | | | | | | | | By adding this field, the pm qos apis can be selectively applied only if the pm constraint is set to a +ve value. Change-Id: I3b6930e85f65f7354826813798dec76b25149370 Signed-off-by: Subramaniam C.A <subramaniam.ca@ti.com> Signed-off-by: Omar Ramirez Luna <omar.ramirez@ti.com> Signed-off-by: Suman Anna <s-anna@ti.com>
* omap: iommu: program constraints based on platform dataSubramaniam C.A2012-04-181-0/+2
| | | | | | | | | | | | | | | | | | | | IOMMU driver requests and releases constraints in iommu_get and iommu_put respectively. These constraints are actually needed only on OMAP4 and beyond for sub-systems that have an AMMU. The current driver code has these values hard-coded for all the chips. A new platform data field has been added now for the constraints values, and this allows the values to be programmed based on the OMAP chip and also allow a unique value if needed for each iommu instance. The logic in IOMMU driver code is adjusted to request the constraints only if the relevant platform data field is set. Change-Id: Iab18cbdde1d7fa7507dbff0b9512c8577b42fefd Signed-off-by: Subramaniam C.A <subramaniam.ca@ti.com> Signed-off-by: Suman Anna <s-anna@ti.com>
* sgx_omaplfb: Create omaplfb platform device file to permit device configurationTony Lofthouse2012-04-161-0/+71
| | | | | | Change-Id: Ic790a0440d19d862d981a230470523409b25b9a3 Signed-off-by: Tony Lofthouse <a0741364@ti.com> Signed-off-by: Gustavo Diaz Prado <a0273371@ti.com>
* omap: Adds access_process_vm to gpu platform dataRogelio Garcia2012-03-221-0/+2
| | | | | | | | This core API function is needed by modular PVR driver. Change-Id: I409bf934aa3c2566f468715e490c911b97b247bc Signed-off-by: Rogelio Garcia <rgarcia@ti.com> Signed-off-by: Atanas (Tony) Zlatinski <zlatinski@gmail.com>
* OMAP4: ID: Add high IVA OPPs identificationTaras Kondratiuk2012-03-151-0/+4
| | | | | | | | Some 4460 and 4470 devices support IVA OPPNT and OPPSB. Add flags to identify this feature. Change-Id: I6e78d95ca07435c60aae36562a2d9b66fcd1baa4 Signed-off-by: Taras Kondratiuk <taras@ti.com>
* omap: Adding opp functions to gpu platform data.Rogelio Garcia2012-03-141-0/+3
| | | | | | | This is required for providing opp framework access to SGX kernel module. Change-Id: Ie968a6c51ac636b70909257be4c51430c4cc3d48 Signed-off-by: Rogelio Garcia <rgarcia@ti.com>
* omap: remoteproc: use device-specific dump-register opsJuan Gutierrez2012-03-141-0/+77
| | | | | | | | | | | | | | | The current omap register dump function is catering only to ARM cores. Introduce device-specific dump register functions so that the omap remoteproc code can call into them based on the processor type. This patch also adds a minimal support for dumping dsp registers in addition to moving the existing functionality for ARM cores to the device-specific function. Change-Id: Ic446695a6a5a1a4b1f600c1900f74c3e5932c158 Signed-off-by: Juan Gutierrez <jgutierrez@ti.com> Signed-off-by: Suman Anna <s-anna@ti.com>
* omap: add dsp carveout for remoteproc functionalityJuan Gutierrez2012-03-142-1/+20
| | | | | | | | | | | | | | | | | | | | | | | remoteproc uses DDR carveout memories for the functionality of different rproc instances. New interfaces have been added to perform this carveout memory during board initialization for DSP. This patch reserves two types of carveout memory - one whose address is dynamic, and another that leverages a fixed static range. The dynamic pool will be used for allocating memory for firmware sections that have no physical memory allocated. The static pool will be used to validate the firmware sections with fixed physical addresses. This patch also assigns addresses for the Virtio vring buffers for DSP. This is previously not handled, and the buffers are currently assigned from the static pool associated with the dsp. The rpmsg bus initialization sequence is enhanced to process all the vprocs even if an earlier one in the list fails due to memory requirements. Change-Id: I0dec512b63904d3ffe0867ce00150b6c21a80805 Signed-off-by: Juan Gutierrez <jgutierrez@ti.com> Signed-off-by: Suman Anna <s-anna@ti.com>
* omap: add ipu and dsp as configurable remoteproc instancesJuan Gutierrez2012-03-141-1/+1
| | | | | | | | | | | | | | | | | OMAP4 and OMAP5 both support two remoteproc instances - ipu & dsp. The CONFIG_OMAP_REMOTE_PROC menuconfig option enabled support for all OMAP remoteproc instances, but there was no choice to enable/disable a specific remoteproc instance. This patch adds two additional dependent config options for finer control over these remoteproc instances. The option CONFIG_OMAP_REMOTE_PROC will continue to be the generic option for enabling remoteproc driver support for OMAP. Change-Id: I9688672e4c758b9e4f4c0fb4f83654ef7b3cf48f Signed-off-by: Juan Gutierrez <jgutierrez@ti.com> Signed-off-by: Suman Anna <s-anna@ti.com> Signed-off-by: Subramaniam C.A <subramaniam.ca@ti.com>
* omap: remoteproc: add support for a boot registerJuan Gutierrez2012-03-141-0/+2
| | | | | | | | | | | | | | | | | | | Some remote processors (like DSP) need to explicitly configure a boot address in a special register or memory location, and this is the address from which they start executing code when taken out of reset. Support for this infrastructure has been added to remoteproc code. The memory or register address where the boot address is to be stored is supplied through the boot_reg field of the platform data in the remoteproc. The omap_rproc_start function will fetch the boot address from the image, and write this address into the boot register, if provided, before taking the processor out of reset. Change-Id: I4efc5824791eda6e23e5d568f4568a3fe3d0014b Signed-off-by: Juan Gutierrez <jgutierrez@ti.com> Signed-off-by: Suman Anna <s-anna@ti.com>
* OMAPDSS: DSSCOMP: move device to omap plat to configure tiler1d slotTony Lofthouse2012-03-051-0/+4
| | | | | | | | | | | Different devices will have varying requirements on tiler resources. This change moves the platform device registration for dsscomp to the omap platform level so at device initialization time we can set the appropriate Tiler1D slot size. Change-Id: I5edf5b7cfb056a45ab038b244d2efc758a840b00 Signed-off-by: Tony Lofthouse <a0741364@ti.com> Signed-off-by: Lajos Molnar <lajos@ti.com>
* OMAP4: Add 4430 ES2.3 chip is checkDan Murphy2012-02-011-3/+4
| | | | | | | | | | 4430 ES2.3 chip is check was missed during the merge phase. Putting it back in Change-Id: I94fa2b8f803acb2a13c2f7db4558b2864106d213 Signed-off-by: Dan Murphy <dmurphy@ti.com>
* ARM:OMAP4:Thermal Framework:added TMP102 temperature sensorEugen Mandrenko2012-02-011-0/+29
| | | | | | | | This patch adds kernel driver for TMP102 temperature sensor TMP102 is controled through I2C bus. Change-Id: I4012a0ab53945ad8a240f395bb321cf09ebeb3ea Signed-off-by: Eugen Mandrenko <ievgen.mandrenko@ti.com>
* OMAP4: ID: Add runtime detection of 4470 1.5Ghz siliconLeonid Iziumtsev2012-02-011-1/+3
| | | | | | | | | STD_FUSE_PROD_ID_1[17:16] fuse determines silicon type: 0x1 - Standard performance (1.3 GHz) 0x2 - High performance (1.5 GHz) Change-Id: I7e37daf1d214d63b35f10fa45952485c59cbc009 Signed-off-by: Leonid Iziumtsev <x0153368@ti.com>
* ARM: OMAP4: clock: Define 4470 flag in cpu masksTaras Kondratiuk2012-02-012-4/+5
| | | | | | | | | | Define OMAP4470 flag in clock cpu masks. Reuse CK_44XX clocks for 4470. Increased 'flags' field size to fit additional CPU type. Change-Id: I546d69495152567b2248b457172c0ab7b2782ce3 Signed-off-by: Taras Kondratiuk <taras@ti.com>
* OMAP4: ID: Chip detection for OMAP4470Leonid Iziumtsev2012-02-011-5/+16
| | | | | | | Add support for detection of the next chip in the OMAP4 family: OMAP4470 ES1.0 Change-Id: I931d3df6e69fdc3ee4a307c204a68fc9b3ff519b Signed-off-by: Leonid Iziumtsev <x0153368@ti.com>
* OMAP4: HSI: Added API to allow HSI device registrationDjamil Elaidi2012-01-041-0/+2
| | | | | | | | | | | | If HSI support is not needed, omap_hsi device shall not be registered as it will force the muxing of usbb1_ulpitll_clk pad to hsi1_cawake, which is not good. omap_hsi device will now only be registered if explicitly requested using new API omap_hsi_allow_registration(). Change-Id: I405a614f0421056e4c5a5fee8b98b1482b40b8da Signed-off-by: Djamil Elaidi <d-elaidi@ti.com>
* OMAP4: HSI: Add HW errata platform dataDjamil Elaidi2012-01-041-0/+25
| | | | | | | | | | | | Created a platform data field to pass errata ids to HSI driver. Supported erratum are : HSI-C1BUG00088: i696: HSI: Issue with SW reset HSI-C1BUG00085: ixxx: HSI wakeup issue in 3 wires mode HSI-OMAP4430-2.2BUG00055: i702: DSP Swakeup generated is the same than MPU Swakeup. Change-Id: I0b4fca39b1133842aa1ca62ff4e60b4425cf4776 Signed-off-by: Djamil Elaidi <d-elaidi@ti.com>
* OMAP4: HSI: Fix for back to back CAWAKE interruptsDjamil Elaidi2011-12-221-1/+1
| | | | | | | | | | | | | | | | | | If a CAWAKE interrupt occurs while previous CAWAKE is still being processed, the end of first CAWAKE processing will clear interrupt status bit for 1st CAWAKE interrupt, but also for second interrupt. So 2nd CAWAKE interrupt is missed. Added a backup CAWAKE interrupt (HSI_Pp_M_IRQrU_STATUS.HSR_WAKE) to take over the regular CAWAKE interrupt ((HSI_Pp_M_IRQr_STATUS.HSR_WAKE) while it is being processed. This CAWAKE backup interrupt will catch the second interrupt if it occurs. It guaranty we don't miss a CAWAKE interrupt while clearing the previous regular one. Change-Id: Id37bbe095f72af7dd478f8e9b1256d136b7ccebc Signed-off-by: Djamil Elaidi <d-elaidi@ti.com> Reported-by: Cedric Poignet <a0919860@ti.com>
* OMAP4: HSI: Add dynamic OPP changeDjamil Elaidi2011-12-211-2/+6
| | | | | | | | | | | | | | Added an IOCTL to change HSI FClk to 96MHz or 192MHz. Decision of when to increase/decrease modem speed is up to Link Layer. Constraint : * RX/TX divisors and RX error counters need to be changed after Fclk is changed. * Read/Write operation must not be pending when OPP change request is issued, otherwise OPP change is aborted. * Any Read/Write operation started during HSI OPP change operation will be aborted. Change-Id: I06e15a205e614506994989ec6a40c0383e32776d Signed-off-by: Djamil Elaidi <d-elaidi@ti.com>
* omap4: add 4430 ES2.3 supportAnand Gadiyar2011-12-191-4/+7
| | | | | | | And default to 4430 ES2.3 for unidentified silicon. Change-Id: I06b0aa9c5f33af25345996cf9d0c994491093096 Signed-off-by: Anand Gadiyar <gadiyar@ti.com>
* OMAP4 Thermal Framework: added PCB temperature sensorSebastien Sabatier2011-12-191-0/+33
| | | | | | | | | | This patch adds kernel driver for PCB temperature sensor connected on TWL6030 GPADC (Thermistor). It calls dedicated function to start GPADC conversion and convert the result into milli-degrees celsius. Change-Id: I7b573182611bda187f6a38dc01ba65935c8a5c4b Signed-off-by: Sebastien Sabatier <s-sabatier1@ti.com>
* OMAP: hwmod: fix the i2c-reset timeout during bootupAvinash.H.M2011-12-152-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | The sequence of _ocp_softreset doesn't work for i2c. The i2c module has a special sequence to reset the module. The sequence is - Disable the I2C. - Write to SOFTRESET bit. - Enable the I2C. - Poll on the RESETDONE bit. The sequence is implemented as a function and the i2c_class is updated with the correct 'reset' pointer. omap_hwmod_softreset function is implemented which triggers the softreset by writing into sysconfig register. On following this sequence, i2c module resets properly and timeouts are not seen. Change-Id: I742f18d6db724235a38923312be64723316c9ef1 Cc: Rajendra Nayak <rnayak@ti.com> Cc: Paul Walmsley <paul@pwsan.com> Cc: Benoit Cousson <b-cousson@ti.com> Cc: Kevin Hilman <khilman@ti.com> Signed-off-by: Avinash.H.M <avinashhm@ti.com> [paul@pwsan.com: combined this patch with a patch to remove HWMOD_INIT_NO_RESET from the 44xx hwmod flags; change register offset conditional code to use the IP block revision; minor code cleanup] Signed-off-by: Paul Walmsley <paul@pwsan.com> Signed-off-by: Jon Hunter <jon-hunter@ti.com>
* I2C: OMAP2+: Introduce I2C IP versioning constantsAndy Green2011-12-151-0/+1
| | | | | | | | | | | | | | | | | | These represent the two kinds of (incompatible) OMAP I2C peripheral unit in use so far. The constants are in linux/i2c-omap.h so the omap i2c driver can have them too. Change-Id: I42d2c7822985a9bc4124986d7cd786565006466f Cc: patches@linaro.org Cc: Ben Dooks <ben-linux@fluff.org> Reported-by: Peter Maydell <peter.maydell@linaro.org> Signed-off-by: Andy Green <andy.green@linaro.org> Signed-off-by: Tony Lindgren <tony@atomide.com> Signed-off-by: Kevin Hilman <khilman@ti.com> Signed-off-by: Paul Walmsley <paul@pwsan.com> Signed-off-by: Jon Hunter <jon-hunter@ti.com>
* omap: uart: wer restorationruchika kharwar2011-12-141-0/+1
| | | | | | | | | | | | | | | | | | | The WER value for a uart port is restored properly in either case Case 1: The port is started, the device enters off mode and resumes. In this case wer is restored with the intended board defined value. Case 2: The port is started, shutdown, the device enters off mode and resumes. In this case wer is restored with zero. This prevents events from being registered in the uart hardware which will not be handled by a port that is not started in software. Change-Id: I5dd426b2cdb8925404f6ba7fc83569b49bda1695 Signed-off-by: Ruchika Kharwar <ruchika@ti.com>
* OMAP4: UART: Add UART init at boot for DEBUG_LL on TabletEduard Popkov2011-11-291-0/+1
| | | | | | | | Makes DEBUG_LL on OMAP4 recognize omap_tabletblaze machine. Change-Id: I9c815703f81df9f6d13feaa17af4b85dad771cc9 Signed-off-by: Eduard Popkov <eduard.popkov@globallogic.com> Signed-off-by: Taras Kondratiuk <taras@ti.com>
generated by cgit v1.1 at 2025-08-15 18:03:21 +0000