Use dts data for ti-sysc to configure sysconfig
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest12 patches 5 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/12 | bus: ti-sysc: Add fck clock alias for children with notifier_blockdrivers/ | +87 | 0 replies | |
| 2/12 | bus: ti-sysc: Add suspend and resume handlingdrivers/ | +34 | 0 replies | |
| 3/12 | bus: ti-sysc: Handle stdout-path for debug consoledrivers/ | +46 | 0 replies | |
| 4/12 | bus: ti-sysc: Improve handling for no-reset-on-init and no-idle-on-initdrivers/ | +22 | 0 replies | |
| 5/12 | bus: ti-sysc: Remove unnecessary debugging statementsdrivers/ | +1 | 0 replies | |
| 6/12 | bus: ti-sysc: Add support for platform data callbacksarch/ arch/ drivers/ +1 more | +172 | 0 replies | |
| 7/12 | bus: ti-sysc: Handle some devices in omap_device compatible waydrivers/ include/ | +225 | 1 reply | |
| 8/12 | ARM: OMAP2+: Add functions to allocate module data from device treearch/ arch/ | +315 | 0 replies | |
| 9/12 | ARM: OMAP2+: Add checks for device tree based sysconfig dataarch/ | +106 | 0 replies | |
| 10/12 | ARM: OMAP2+: Try to parse earlycon from parent tooarch/ | +6 | 0 replies | |
| 11/12 | PM / AVS: SmartReflex: Prepare to use device tree based probingdrivers/ | +34 | 4 replies | |
| 12/12 | ARM: OMAP2+: Enable ti-sysc to use device tree data for smartreflexarch/ arch/ arch/ | +20 | 0 replies |
Reviews trailers per patch
1 of 12 patches has a Reviewed-by or Acked-by.
| Patch | Kevin Hilman |
|---|---|
| 1/12 | |
| 2/12 | |
| 3/12 | |
| 4/12 | |
| 5/12 | |
| 6/12 | |
| 7/12 | |
| 8/12 | |
| 9/12 | |
| 10/12 | |
| 11/12 | A-b |
| 12/12 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 00/12] Use dts data for ti-sysc to configure sysconfig
Hi all,
This series of changes makes ti-sysc driver to use device tree data for configuring the interconnect target module registers. We already have smartreflex dts data configured according to the binding for ti-sysc, so that will be the first user.
I've added code to check the dts data against the existing platform data to make sure we're not causing regressions. And I've verified that PM still works.
Regards,
Tony
Tony Lindgren (12):
bus: ti-sysc: Add fck clock alias for children with notifier_block
bus: ti-sysc: Add suspend and resume handling
bus: ti-sysc: Handle stdout-path for debug console
bus: ti-sysc: Improve handling for no-reset-on-init and
no-idle-on-init
bus: ti-sysc: Remove unnecessary debugging statements
bus: ti-sysc: Add support for platform data callbacks
bus: ti-sysc: Handle some devices in omap_device compatible way
ARM: OMAP2+: Add functions to allocate module data from device tree
ARM: OMAP2+: Add checks for device tree based sysconfig data
ARM: OMAP2+: Try to parse earlycon from parent too
PM / AVS: SmartReflex: Prepare to use device tree based probing
ARM: OMAP2+: Enable ti-sysc to use device tree data for smartreflex
arch/arm/mach-omap2/board-n8x0.c | 4 +- arch/arm/mach-omap2/omap_device.c | 5 + arch/arm/mach-omap2/omap_hwmod.c | 418 ++++++++++++++++++++++++++- arch/arm/mach-omap2/omap_hwmod.h | 7 + arch/arm/mach-omap2/pdata-quirks.c | 41 ++- arch/arm/mach-omap2/sr_device.c | 25 +- drivers/bus/ti-sysc.c | 527 +++++++++++++++++++++++++++++++--- drivers/power/avs/smartreflex.c | 41 ++- include/linux/platform_data/ti-sysc.h | 50 ++++ 9 files changed, 1063 insertions(+), 55 deletions(-)
Signature · 1 line
2.16.2