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(-)
--
2.16.2
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
