summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-omap2/omap_hwmod_33xx_43xx_interconnect_data.c
Commit message (Collapse)AuthorAgeFilesLines
* ARM: OMAP2+: Drop uart platform data for am33xx and am43xxTony Lindgren2019-04-081-40/+0Star
| | | | | | | | We can now drop legacy platform data one interconnect target module at a time in favor of the device tree based data that has been added earlier. Signed-off-by: Tony Lindgren <tony@atomide.com>
* ARM: OMAP2+: Drop gpio platform data for am33xx and am43xxTony Lindgren2019-04-081-24/+0Star
| | | | | | | | We can now drop legacy platform data one interconnect target module at a time in favor of the device tree based data that has been added earlier. Signed-off-by: Tony Lindgren <tony@atomide.com>
* ARM: OMAP2+: Drop i2c platform data for am33xx and am43xxTony Lindgren2019-04-081-15/+0Star
| | | | | | | | We can now drop legacy platform data one interconnect target module at a time in favor of the device tree based data that has been added earlier. Signed-off-by: Tony Lindgren <tony@atomide.com>
* ARM: OMAP2+: Drop mmc platform data for am330x and am43xxTony Lindgren2019-04-081-24/+0Star
| | | | | | | | We can now drop legacy platform data one interconnect target module at a time in favor of the device tree based data that has been added earlier. Signed-off-by: Tony Lindgren <tony@atomide.com>
* ARM: OMAP2+: Drop legacy struct omap_hwmod_addr_spaceTony Lindgren2017-10-101-100/+0Star
| | | | | | | | | | | With all of mach-omap2 booting now in device tree only mode, we can get the module IO range from device tree and just drop the legacy hwmod struct omap_hwmod_addr_space. Cc: Lokesh Vutla <lokeshvutla@ti.com> Cc: Paul Walmsley <paul@pwsan.com> Cc: Tero Kristo <t-kristo@ti.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
* ARM: OMAP2+: Fix MMC address space mismatch for am33xx and am43xxTony Lindgren2017-09-191-30/+0Star
| | | | | | | | | | | | | | The address space currently set up for the interconnect data is different compared to the dts data. We have hwmod data with offset 0x100 to account for the revision, sysc and syss register offsets. Let's fix the issue by correcting the MMC register offsets in hwmod data and removing the unnecessary duplicate IO range data that we get from device tree anyways. Cc: Lokesh Vutla <lokeshvutla@ti.com> Cc: Paul Walmsley <paul@pwsan.com> Cc: Tero Kristo <t-kristo@ti.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
* ARM: AMx3xx: hwmod: Add data for RNGLokesh Vutla2016-11-091-0/+8
| | | | | | | | | Hardware random number generator is present in both AM33xx and AM43xx SoC's. So moving the hwmod data to common data. Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com> Signed-off-by: Tero Kristo <t-kristo@ti.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
* ARM: AM335x/AM437x: hwmod: Remove eQEP, ePWM and eCAP hwmod entriesFranklin S Cooper Jr2016-06-101-64/+0Star
| | | | | | | | | | | | | | Devices that utilize the OCP registers and/or PRCM registers and register bit fields should be modeled using hwmod. Since eQEP, ePWM and eCAP don't fall under this category, remove their hwmod entries. Instead these clocks simply use the clock that is passed through by its parent PWMSS. Therefore, PWMSS handles the clock for itself and its subdevices. Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com> Acked-by: Paul Walmsley <paul@pwsan.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
* ARM: DRA7/AM335x/AM437x: hwmod: Remove gpmc address space from hwmod dataFranklin S Cooper Jr2015-10-231-10/+0Star
| | | | | | | | | | GPMC address information is provided by device tree. No longer need to include this information within hwmod. Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com> Acked-by: Roger Quadros <rogerq@ti.com> [paul@pwsan.com: fixed chip names in subject line] Signed-off-by: Paul Walmsley <paul@pwsan.com>
* ARM: DRA7/AM335x/AM437x: hwmod: Remove elm address space from hwmod dataFranklin S Cooper Jr2015-10-201-10/+0Star
| | | | | | | | | | | ELM address information is provided by device tree. No longer need to include this information within hwmod. Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com> Acked-by: Roger Quadros <rogerq@ti.com> [paul@pwsan.com: fixed chip names in subject line; dropped the OMAP4 section since the OMAP4 SoC DTS file doesn't have the ELM address space documented yet] Signed-off-by: Paul Walmsley <paul@pwsan.com>
* ARM: AM33xx: hwmod_data: Remove legacy mailbox addrsSuman Anna2014-07-151-10/+0Star
| | | | | | | | | | The legacy-style definition of the hwmod addr space is no longer required as AM33xx/AM43xx are DT-boot only, and the minimal mailbox DT nodes have been added, so clean up this data. Acked-by: Paul Walmsley <paul@pwsan.com> Signed-off-by: Suman Anna <s-anna@ti.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
* ARM: OMAP2+: hwmod: AM335x/AM43x: move common dataAfzal Mohammed2013-10-141-0/+643
AM335x and AM43x have most of the IP's and interconnect's similar. Instead of adding redundant hwmod data, move interconnects and hwmod similar between AM335x and AM43x to a common location. This helps in reuse on AM43x. AM335x interconnects that has difference and not present in AM43x are not moved. ocp clock of those in l4_wkup is fed from a different source for AM43x. Also pruss interconnect is different. AM335x hwmod's that has difference other than prcm register offsets (difference is in clocks of wkup_m3, control, gpio0, debugss and clock domain of l4_hs, adc_tsc as compared to AM43x) and those that are not present in AM43x are not moved. Signed-off-by: Afzal Mohammed <afzal@ti.com> Acked-by: Rajendra Nayak <rnayak@ti.com> Acked-by: Tony Lindgren <tony@atomide.com> Signed-off-by: Paul Walmsley <paul@pwsan.com>