Configure sgx interconnect data for some omap variants
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest6 patches 20 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | ARM: OMAP2+: Drop legacy platform data for omap4 gpuarch/ arch/ | +0 | 0 replies | |
| 2/6 | bus: ti-sysc: Add module enable quirk for SGX on omap36xxdrivers/ include/ | +22 | 0 replies | |
| 3/6 | clk: ti: add clkctrl data omap5 sgxdrivers/ include/ | +37 | 0 replies | |
| 4/6 | ARM: dts: Configure sgx for omap5arch/ arch/ | +37 | 5 replies | |
| 5/6 | ARM: dts: Configure interconnect target module for omap3 sgxarch/ arch/ | +53 | 3 replies | |
| 6/6 | ARM: dts: Configure rstctrl reset for SGXarch/ | +25 | 7 replies |
Reviews trailers per patch
None of the 6 patches has a Reviewed-by or Acked-by.
| Patch | Adam Ford |
|---|---|
| Series | T-b T-b |
| 1/6 | |
| 2/6 | |
| 3/6 | |
| 4/6 | |
| 5/6 | T-b |
| 6/6 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/6] Configure sgx interconnect data for some omap variants
Hi all,
For a while we've been idling sgx module on omap4 by probing it with ti-sysc interconnect target module driver. This allows leaving out any platform data in favor of device tree data, and idles the module for PM even if we don't have any sgx driver.
I've added similar configuration for omap34xx, omap36xx, omap5 and am335x. Adding dra7 should work too, but my beagle x15 is suffering from a power supply problem right now and I'll need to work more on that later on.
For am335x, the recently posted prm rstctrl driver is needed. The other SoCs here don't have a dependency to the prm rstctrl driver. And probably am335x child driver(s) also need to map the rstctrl register to increase the deassert use count.
Please review and test, this should allow sgx child driver(s) to just use PM runtime to enable the module with no platform data.
I've only tested these SoCs via sysfs to ensure the sgx module gets enabled and disabled properly. If you know something about sgx, please describe more why the sgx registers seem to be at different place for each SoC like between omap34xx and omap36xx.
These patches may have some dependencies to what I've queued into my for-next branch for fixes so it's best to test with that merged in. Linux next should be usable for testing with these the next time it gets integrated.
Regards,
Tony
Tony Lindgren (6):
ARM: OMAP2+: Drop legacy platform data for omap4 gpu
bus: ti-sysc: Add module enable quirk for SGX on omap36xx
clk: ti: add clkctrl data omap5 sgx
ARM: dts: Configure sgx for omap5
ARM: dts: Configure interconnect target module for omap3 sgx
ARM: dts: Configure rstctrl reset for SGX
arch/arm/boot/dts/am33xx.dtsi | 25 ++++++++++ arch/arm/boot/dts/omap34xx.dtsi | 26 +++++++++++ arch/arm/boot/dts/omap36xx.dtsi | 27 +++++++++++ arch/arm/boot/dts/omap4.dtsi | 1 - arch/arm/boot/dts/omap5.dtsi | 23 ++++++++++ arch/arm/boot/dts/omap54xx-clocks.dtsi | 14 ++++++ arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 53 ---------------------- drivers/bus/ti-sysc.c | 21 +++++++++ drivers/clk/ti/clk-54xx.c | 34 ++++++++++++++ include/dt-bindings/clock/omap5.h | 3 ++ include/linux/platform_data/ti-sysc.h | 1 + 11 files changed, 174 insertions(+), 54 deletions(-)
Signature · 1 line
2.21.0