From: Tony Lindgren <tony@atomide.com>
To: arm@kernel.org
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] dts changes to use ti-sysc driver for omap4 l4
Date: Mon, 23 Jul 2018 20:40:03 -0700 [thread overview]
Message-ID: <pull-1532403550-185479@atomide.com> (raw)
From: "Tony Lindgren" <tony@atomide.com>
The following changes since commit 91f6278bfa3966529c61808bd3cb8f05d7ed5dc6:
ARM: dts: am335x: add am335x-sancloud-bbe board support (2018-07-17 01:05:37 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.19/dt-pt3-signed
for you to fetch changes up to ab8b1fdd012f41b27f85a6bb271389fd7ff349ea:
Merge branch 'omap-for-v4.19/dt-sysc-v2' into omap-for-v4.19/dt (2018-07-20 22:22:08 -0700)
----------------------------------------------------------------
Start using ti-sysc with device tree data for omap4 l4 devices
With ti-sysc driver working for most use cases, we can start converting
the omap variant SoCs to use device tree data for the interconnect target
modules instead of the legacy hwmod platform data.
We start with omap4 l4 devices excluding the ones that still depend on
a reset controller driver like DSP MMU. And we don't yet convert the l4
ABE instance as that needs a bit more work.
We also add a proper interconnect hierarchy for the devices while at it
to make further work on genpd easier and to avoid most deferred probe
issues.
At this point we are not dropping any platform data, and we initially
still use it to validate the dts data. Then in later merge cycles we
can start dropping the related platform data.
----------------------------------------------------------------
Tony Lindgren (6):
dt-bindings: Update omap l4 binding for optional registers
ARM: dts: omap4: Add l4 interconnect hierarchy and ti-sysc data
ARM: dts: omap4: Probe watchdog 3 with ti-sysc
ARM: dts: omap4: Move l4 child devices to probe them with ti-sysc
ARM: dts: omap4: Add l4 ranges for 4460
Merge branch 'omap-for-v4.19/dt-sysc-v2' into omap-for-v4.19/dt
Documentation/devicetree/bindings/arm/omap/l4.txt | 15 +-
arch/arm/boot/dts/omap4-l4.dtsi | 2444 +++++++++++++++++++++
arch/arm/boot/dts/omap4-panda-es.dts | 2 +-
arch/arm/boot/dts/omap4.dtsi | 812 +------
arch/arm/boot/dts/omap4460.dtsi | 36 +
5 files changed, 2526 insertions(+), 783 deletions(-)
create mode 100644 arch/arm/boot/dts/omap4-l4.dtsi
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] dts changes to use ti-sysc driver for omap4 l4
Date: Mon, 23 Jul 2018 20:40:03 -0700 [thread overview]
Message-ID: <pull-1532403550-185479@atomide.com> (raw)
From: "Tony Lindgren" <tony@atomide.com>
The following changes since commit 91f6278bfa3966529c61808bd3cb8f05d7ed5dc6:
ARM: dts: am335x: add am335x-sancloud-bbe board support (2018-07-17 01:05:37 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.19/dt-pt3-signed
for you to fetch changes up to ab8b1fdd012f41b27f85a6bb271389fd7ff349ea:
Merge branch 'omap-for-v4.19/dt-sysc-v2' into omap-for-v4.19/dt (2018-07-20 22:22:08 -0700)
----------------------------------------------------------------
Start using ti-sysc with device tree data for omap4 l4 devices
With ti-sysc driver working for most use cases, we can start converting
the omap variant SoCs to use device tree data for the interconnect target
modules instead of the legacy hwmod platform data.
We start with omap4 l4 devices excluding the ones that still depend on
a reset controller driver like DSP MMU. And we don't yet convert the l4
ABE instance as that needs a bit more work.
We also add a proper interconnect hierarchy for the devices while at it
to make further work on genpd easier and to avoid most deferred probe
issues.
At this point we are not dropping any platform data, and we initially
still use it to validate the dts data. Then in later merge cycles we
can start dropping the related platform data.
----------------------------------------------------------------
Tony Lindgren (6):
dt-bindings: Update omap l4 binding for optional registers
ARM: dts: omap4: Add l4 interconnect hierarchy and ti-sysc data
ARM: dts: omap4: Probe watchdog 3 with ti-sysc
ARM: dts: omap4: Move l4 child devices to probe them with ti-sysc
ARM: dts: omap4: Add l4 ranges for 4460
Merge branch 'omap-for-v4.19/dt-sysc-v2' into omap-for-v4.19/dt
Documentation/devicetree/bindings/arm/omap/l4.txt | 15 +-
arch/arm/boot/dts/omap4-l4.dtsi | 2444 +++++++++++++++++++++
arch/arm/boot/dts/omap4-panda-es.dts | 2 +-
arch/arm/boot/dts/omap4.dtsi | 812 +------
arch/arm/boot/dts/omap4460.dtsi | 36 +
5 files changed, 2526 insertions(+), 783 deletions(-)
create mode 100644 arch/arm/boot/dts/omap4-l4.dtsi
next reply other threads:[~2018-07-24 3:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 3:40 Tony Lindgren [this message]
2018-07-24 3:40 ` [GIT PULL] dts changes to use ti-sysc driver for omap4 l4 Tony Lindgren
2018-07-26 6:54 ` Olof Johansson
2018-07-26 6:54 ` Olof Johansson
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-1532403550-185479@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.