From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/12] Use dts data for ti-sysc to configure sysconfig
Date: Fri, 23 Feb 2018 13:00:48 -0800 [thread overview]
Message-ID: <20180223210100.86732-1-tony@atomide.com> (raw)
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
next reply other threads:[~2018-02-23 21:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 21:00 Tony Lindgren [this message]
2018-02-23 21:00 ` [PATCH 01/12] bus: ti-sysc: Add fck clock alias for children with notifier_block Tony Lindgren
2018-02-23 21:00 ` [PATCH 02/12] bus: ti-sysc: Add suspend and resume handling Tony Lindgren
2018-02-23 21:00 ` [PATCH 03/12] bus: ti-sysc: Handle stdout-path for debug console Tony Lindgren
2018-02-23 21:00 ` [PATCH 04/12] bus: ti-sysc: Improve handling for no-reset-on-init and no-idle-on-init Tony Lindgren
2018-02-23 21:00 ` [PATCH 05/12] bus: ti-sysc: Remove unnecessary debugging statements Tony Lindgren
2018-02-23 21:00 ` [PATCH 06/12] bus: ti-sysc: Add support for platform data callbacks Tony Lindgren
2018-02-23 21:00 ` [PATCH 07/12] bus: ti-sysc: Handle some devices in omap_device compatible way Tony Lindgren
2018-03-01 0:37 ` Tony Lindgren
2018-02-23 21:00 ` [PATCH 08/12] ARM: OMAP2+: Add functions to allocate module data from device tree Tony Lindgren
2018-02-23 21:00 ` [PATCH 09/12] ARM: OMAP2+: Add checks for device tree based sysconfig data Tony Lindgren
2018-02-23 21:00 ` [PATCH 10/12] ARM: OMAP2+: Try to parse earlycon from parent too Tony Lindgren
2018-02-23 21:00 ` [PATCH 11/12] PM / AVS: SmartReflex: Prepare to use device tree based probing Tony Lindgren
2018-02-26 10:37 ` Rafael J. Wysocki
2018-02-26 21:34 ` Tony Lindgren
2018-03-01 3:07 ` Kevin Hilman
2018-03-01 3:49 ` Tony Lindgren
2018-02-23 21:01 ` [PATCH 12/12] ARM: OMAP2+: Enable ti-sysc to use device tree data for smartreflex Tony Lindgren
2018-02-23 21:41 ` [PATCH 0.5/12] ARM: OMAP2+: Prepare to pass auxdata " Tony Lindgren
2018-02-26 8:37 ` kbuild test robot
2018-02-26 22:23 ` Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180223210100.86732-1-tony@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).