From: Tony Lindgren <tony@atomide.com>
To: linux-omap@vger.kernel.org
Cc: "Benoît Cousson" <bcousson@baylibre.com>, devicetree@vger.kernel.org
Subject: [PATCH 00/12] Update omap4 devicetree files to probe with genpd
Date: Mon, 8 Mar 2021 15:38:58 +0200 [thread overview]
Message-ID: <20210308133910.12454-1-tony@atomide.com> (raw)
Hi all,
Here are the devicetree changes to update omap4 to probe with genpd and
simple-pm-bus.
These patches are against v5.12-rc2, and depend on the following preparatory
patches posted earlier:
"ARM: OMAP2+: Init both prm and prcm nodes early for clocks"
"bus: ti-sysc: Probe for l4_wkup and l4_cfg interconnect devices first"
"ARM: dts: Drop duplicate sha2md5_fck to fix clk_disable race"
"ARM: dts: Fix moving mmc devices with aliases for omap4 & 5"
"bus: ti-sysc: Fix initializing module_pa for modules without sysc register"
"soc: ti: omap-prm: Allow hardware supported retention when idle"
I will post another series to drop the legacy data.
Regards,
Tony
Tony Lindgren (12):
ARM: dts: Configure power-domain for omap4 gfx
ARM: dts: Configure power-domain for omap4 dts iss
ARM: dts: Configure interconnect target module for omap4 dmm
ARM: dts: Configure interconnect target module for omap4 emif
ARM: dts: Configure interconnect target module for omap4 debugss
ARM: dts: Configure interconnect target module for omap4 mpu
ARM: dts: Move omap4 mmio-sram out of l3 interconnect
ARM: dts: Move omap4 l3-noc to a separate node
ARM: dts: Configure simple-pm-bus for omap4 l4_wkup
ARM: dts: Configure simple-pm-bus for omap4 l4_per
ARM: dts: Configure simple-pm-bus for omap4 l4_cfg
ARM: dts: Prepare for simple-pm-bus for omap4 l3
arch/arm/boot/dts/omap4-l4.dtsi | 39 +++++---
arch/arm/boot/dts/omap4.dtsi | 165 ++++++++++++++++++++++----------
arch/arm/boot/dts/omap4460.dtsi | 13 ++-
3 files changed, 143 insertions(+), 74 deletions(-)
--
2.30.1
next reply other threads:[~2021-03-08 13:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 13:38 Tony Lindgren [this message]
2021-03-08 13:38 ` [PATCH 01/12] ARM: dts: Configure power-domain for omap4 gfx Tony Lindgren
2021-03-08 13:39 ` [PATCH 02/12] ARM: dts: Configure power-domain for omap4 dts iss Tony Lindgren
2021-03-08 13:39 ` [PATCH 03/12] ARM: dts: Configure interconnect target module for omap4 dmm Tony Lindgren
2021-03-08 13:39 ` [PATCH 04/12] ARM: dts: Configure interconnect target module for omap4 emif Tony Lindgren
2021-03-08 13:39 ` [PATCH 05/12] ARM: dts: Configure interconnect target module for omap4 debugss Tony Lindgren
2021-03-08 13:39 ` [PATCH 06/12] ARM: dts: Configure interconnect target module for omap4 mpu Tony Lindgren
2021-03-08 13:39 ` [PATCH 07/12] ARM: dts: Move omap4 mmio-sram out of l3 interconnect Tony Lindgren
2021-03-08 13:39 ` [PATCH 08/12] ARM: dts: Move omap4 l3-noc to a separate node Tony Lindgren
2021-03-08 13:39 ` [PATCH 09/12] ARM: dts: Configure simple-pm-bus for omap4 l4_wkup Tony Lindgren
2021-03-08 13:39 ` [PATCH 10/12] ARM: dts: Configure simple-pm-bus for omap4 l4_per Tony Lindgren
2021-03-08 13:39 ` [PATCH 11/12] ARM: dts: Configure simple-pm-bus for omap4 l4_cfg Tony Lindgren
2021-03-08 13:39 ` [PATCH 12/12] ARM: dts: Prepare for simple-pm-bus for omap4 l3 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=20210308133910.12454-1-tony@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.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 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).