From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/4] driver changes for ti-sysc for v4.16
Date: Fri, 22 Dec 2017 10:14:25 -0800 [thread overview]
Message-ID: <pull-1513966338-859035@atomide.com-2> (raw)
In-Reply-To: <pull-1513966338-859035@atomide.com>
From: "Tony Lindgren" <tony@atomide.com>
The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.16/ti-sysc-signed
for you to fetch changes up to c5a2de97fbd2979fab291fb048084d3fddd322dd:
bus: ti-sysc: Add parsing of module capabilities (2017-12-21 07:28:54 -0800)
----------------------------------------------------------------
TI sysc driver updates for v4.16 merge window
We now have gotten ti-sysc driver to the point where it can parse
interconnect target configuration from device tree instead of the
legacy platform data. This series updates the device tree binding
and adds parsing to the driver for quirks and capabilities.
----------------------------------------------------------------
Tony Lindgren (8):
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
Documentation/devicetree/bindings/bus/ti-sysc.txt | 37 ++
arch/arm/boot/dts/dra7.dtsi | 4 +-
arch/arm/boot/dts/omap4.dtsi | 20 +-
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, 666 insertions(+), 109 deletions(-)
create mode 100644 include/dt-bindings/bus/ti-sysc.h
create mode 100644 include/linux/platform_data/ti-sysc.h
next prev parent reply other threads:[~2017-12-22 18:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 18:14 [GIT PULL 1/4] soc changes for omaps for v4.16, part 2 Tony Lindgren
2017-12-22 18:14 ` Tony Lindgren [this message]
2018-01-05 7:06 ` [GIT PULL 2/4] driver changes for ti-sysc for v4.16 Olof Johansson
2017-12-22 18:14 ` [GIT PULL 3/4] dts changes for omaps for v4.16, part 2 Tony Lindgren
2017-12-22 18:55 ` Tony Lindgren
2017-12-23 16:29 ` Tony Lindgren
2018-01-05 7:06 ` Olof Johansson
2017-12-22 18:14 ` [GIT PULL 4/4] defconfig changes for omaps for v4.16 Tony Lindgren
2018-01-05 7:07 ` Olof Johansson
2018-01-05 6:59 ` [GIT PULL 1/4] soc changes for omaps for v4.16, part 2 Olof Johansson
2018-01-05 18:20 ` 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=pull-1513966338-859035@atomide.com-2 \
--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).