From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/9] Update ti-sysc driver to use dts for capabilities
Date: Fri, 15 Dec 2017 10:08:51 -0800 [thread overview]
Message-ID: <20171215180900.3243-1-tony@atomide.com> (raw)
Hi all,
Here are patches for review to update ti-sysc binding and driver to
get interconnect target module capabilities from device tree.
After this series I'll be posting another series to dynamically
allocate struct omap_hwmod_class_sysconfig based on device tree
data instead of the current platform data.
These patches are against v4.15-rc series with the last patch
depending on the clkctrl nodes in Linux next.
Regards,
Tony
Tony Lindgren (9):
dt-bindings: ti-sysc: Update binding for timers and capabilities
ARM: dts: Add generic ti,sysc compatible in addition to the custom
ones
ARM: OMAP2+: Move all omap_hwmod_sysc_fields to
omap_hwmod_common_data.c
bus: ti-sysc: Make omap_hwmod_sysc_fields into sysc_regbits platform
data
bus: ti-sysc: Add register bits for interconnect target modules
bus: ti-sysc: Detect i2c interconnect target module based on register
layout
bus: ti-sysc: Handle module quirks based dts configuration
bus: ti-sysc: Add parsing of module capabilities
ARM: dts: Update ti-sysc data for existing users
Documentation/devicetree/bindings/bus/ti-sysc.txt | 37 ++
arch/arm/boot/dts/dra7.dtsi | 30 +-
arch/arm/boot/dts/omap4.dtsi | 94 ++++-
arch/arm/mach-omap2/omap_hwmod.c | 2 +
arch/arm/mach-omap2/omap_hwmod.h | 34 +-
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 21 -
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 17 +-
arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 7 +-
arch/arm/mach-omap2/omap_hwmod_common_data.c | 40 +-
drivers/bus/ti-sysc.c | 485 ++++++++++++++++++++--
include/dt-bindings/bus/ti-sysc.h | 22 +
include/linux/platform_data/ti-sysc.h | 86 ++++
12 files changed, 758 insertions(+), 117 deletions(-)
create mode 100644 include/dt-bindings/bus/ti-sysc.h
create mode 100644 include/linux/platform_data/ti-sysc.h
--
2.15.0
next reply other threads:[~2017-12-15 18:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 18:08 Tony Lindgren [this message]
2017-12-15 18:08 ` [PATCH 1/9] dt-bindings: ti-sysc: Update binding for timers and capabilities Tony Lindgren
2017-12-16 18:31 ` Rob Herring
2017-12-16 19:22 ` Tony Lindgren
2017-12-20 18:10 ` Rob Herring
2017-12-21 15:29 ` Tony Lindgren
2017-12-15 18:08 ` [PATCH 2/9] ARM: dts: Add generic ti, sysc compatible in addition to the custom ones Tony Lindgren
2017-12-16 18:34 ` Rob Herring
2017-12-16 19:54 ` Tony Lindgren
2017-12-15 18:08 ` [PATCH 3/9] ARM: OMAP2+: Move all omap_hwmod_sysc_fields to omap_hwmod_common_data.c Tony Lindgren
2017-12-15 18:08 ` [PATCH 4/9] bus: ti-sysc: Make omap_hwmod_sysc_fields into sysc_regbits platform data Tony Lindgren
2017-12-15 18:08 ` [PATCH 5/9] bus: ti-sysc: Add register bits for interconnect target modules Tony Lindgren
2017-12-15 18:08 ` [PATCH 6/9] bus: ti-sysc: Detect i2c interconnect target module based on register layout Tony Lindgren
2017-12-15 18:08 ` [PATCH 7/9] bus: ti-sysc: Handle module quirks based dts configuration Tony Lindgren
2017-12-15 18:08 ` [PATCH 8/9] bus: ti-sysc: Add parsing of module capabilities Tony Lindgren
2017-12-15 18:09 ` [PATCH 9/9] ARM: dts: Update ti-sysc data for existing users 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=20171215180900.3243-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).