All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: linux-omap@vger.kernel.org
Cc: devicetree@vger.kernel.org, "Dave Gerlach" <d-gerlach@ti.com>,
	Keerthy <j-keerthy@ti.com>, "Tero Kristo" <t-kristo@ti.com>,
	"Benoît Cousson" <bcousson@baylibre.com>,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Update am437x and am335x dts to probe with ti-sysc
Date: Mon, 24 Sep 2018 17:05:41 -0700	[thread overview]
Message-ID: <20180925000545.22931-1-tony@atomide.com> (raw)

Hi all,

Here are four patches to make am437x and am335x l4 devices to probe with
ti-sysc driver similar to what we've already done for omap4. The related
legacy hwmod platform data will be removed few merge cycles later.

There are still dependencies to Tero's clkctrl changes and for ti-sysc
drivers changes. So these patches are based on on v4.19-rc3 merged with
my omap-for-v4.20/dt branch plus the following additional series of
patches:

[PATCH 00/11] clk: ti: clkctrl data split based on clkdm boundaries
[PATCH 0/3] ARM: dts: am3/am4/dra7 clkctrl data conversion
[PATCH 0/4] TI sysc driver updates for am335x and am437x

v4.19-rc3 is needed for commit 18eb8aea7fb2 ("net: ethernet:
cpsw-phy-sel: prefer phandle for phy sel") and omap-for-v4.20/dt
is needed to avoid conflicts with clean-up.

I've also pushed out a temporary testing branch for people to test
as omap-for-v4.20/dt-ti-sysc-tmp-testing [0][1].

Regards,

Tony

[0] git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git omap-for-v4.20/dt-ti-sysc-tmp-testing
[1] https://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git/log/?h=omap-for-v4.20/dt-ti-sysc-tmp-testing


Tony Lindgren (4):
  ARM: dts: am437x: Add l4 interconnect hierarchy and ti-sysc data
  ARM: dts: am437x: Move l4 child devices to probe them with ti-sysc
  ARM: dts: am335x: Add l4 interconnect hierarchy and ti-sysc data
  ARM: dts: am335x: Move l4 child devices to probe them with ti-sysc

 arch/arm/boot/dts/am335x-shc.dts |    2 +-
 arch/arm/boot/dts/am33xx-l4.dtsi | 2132 +++++++++++++++++++++++++
 arch/arm/boot/dts/am33xx.dtsi    |  623 +-------
 arch/arm/boot/dts/am4372.dtsi    |  876 +----------
 arch/arm/boot/dts/am437x-l4.dtsi | 2499 ++++++++++++++++++++++++++++++
 5 files changed, 4651 insertions(+), 1481 deletions(-)
 create mode 100644 arch/arm/boot/dts/am33xx-l4.dtsi
 create mode 100644 arch/arm/boot/dts/am437x-l4.dtsi

-- 
2.19.0

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Update am437x and am335x dts to probe with ti-sysc
Date: Mon, 24 Sep 2018 17:05:41 -0700	[thread overview]
Message-ID: <20180925000545.22931-1-tony@atomide.com> (raw)

Hi all,

Here are four patches to make am437x and am335x l4 devices to probe with
ti-sysc driver similar to what we've already done for omap4. The related
legacy hwmod platform data will be removed few merge cycles later.

There are still dependencies to Tero's clkctrl changes and for ti-sysc
drivers changes. So these patches are based on on v4.19-rc3 merged with
my omap-for-v4.20/dt branch plus the following additional series of
patches:

[PATCH 00/11] clk: ti: clkctrl data split based on clkdm boundaries
[PATCH 0/3] ARM: dts: am3/am4/dra7 clkctrl data conversion
[PATCH 0/4] TI sysc driver updates for am335x and am437x

v4.19-rc3 is needed for commit 18eb8aea7fb2 ("net: ethernet:
cpsw-phy-sel: prefer phandle for phy sel") and omap-for-v4.20/dt
is needed to avoid conflicts with clean-up.

I've also pushed out a temporary testing branch for people to test
as omap-for-v4.20/dt-ti-sysc-tmp-testing [0][1].

Regards,

Tony

[0] git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git omap-for-v4.20/dt-ti-sysc-tmp-testing
[1] https://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git/log/?h=omap-for-v4.20/dt-ti-sysc-tmp-testing


Tony Lindgren (4):
  ARM: dts: am437x: Add l4 interconnect hierarchy and ti-sysc data
  ARM: dts: am437x: Move l4 child devices to probe them with ti-sysc
  ARM: dts: am335x: Add l4 interconnect hierarchy and ti-sysc data
  ARM: dts: am335x: Move l4 child devices to probe them with ti-sysc

 arch/arm/boot/dts/am335x-shc.dts |    2 +-
 arch/arm/boot/dts/am33xx-l4.dtsi | 2132 +++++++++++++++++++++++++
 arch/arm/boot/dts/am33xx.dtsi    |  623 +-------
 arch/arm/boot/dts/am4372.dtsi    |  876 +----------
 arch/arm/boot/dts/am437x-l4.dtsi | 2499 ++++++++++++++++++++++++++++++
 5 files changed, 4651 insertions(+), 1481 deletions(-)
 create mode 100644 arch/arm/boot/dts/am33xx-l4.dtsi
 create mode 100644 arch/arm/boot/dts/am437x-l4.dtsi

-- 
2.19.0

             reply	other threads:[~2018-09-25  0:05 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25  0:05 Tony Lindgren [this message]
2018-09-25  0:05 ` [PATCH 0/4] Update am437x and am335x dts to probe with ti-sysc Tony Lindgren
2018-09-25  0:05 ` [PATCH 1/4] ARM: dts: am437x: Add l4 interconnect hierarchy and ti-sysc data Tony Lindgren
2018-09-25  0:05   ` Tony Lindgren
2018-09-25  0:05 ` [PATCH 2/4] ARM: dts: am437x: Move l4 child devices to probe them with ti-sysc Tony Lindgren
2018-09-25  0:05   ` Tony Lindgren
2018-12-04 12:23   ` Peter Ujfalusi
2018-12-04 12:23     ` Peter Ujfalusi
2018-12-04 18:11     ` Tony Lindgren
2018-12-04 18:11       ` Tony Lindgren
2018-12-04 23:18       ` Tony Lindgren
2018-12-04 23:18         ` Tony Lindgren
2018-12-05  6:14         ` Peter Ujfalusi
2018-12-05 19:00           ` Tony Lindgren
2018-12-05 19:00             ` Tony Lindgren
2018-12-05 23:02             ` Tony Lindgren
2018-12-05 23:02               ` Tony Lindgren
2018-12-07 12:46               ` Peter Ujfalusi
2018-09-25  0:05 ` [PATCH 3/4] ARM: dts: am335x: Add l4 interconnect hierarchy and ti-sysc data Tony Lindgren
2018-09-25  0:05   ` Tony Lindgren
2018-09-27 14:56   ` Tony Lindgren
2018-09-27 14:56     ` Tony Lindgren
2018-09-25  0:05 ` [PATCH 4/4] ARM: dts: am335x: Move l4 child devices to probe them with ti-sysc Tony Lindgren
2018-09-25  0:05   ` Tony Lindgren
2018-11-27 13:03   ` Peter Ujfalusi
2018-11-27 13:03     ` Peter Ujfalusi
2018-11-27 16:16     ` Tony Lindgren
2018-11-27 16:16       ` Tony Lindgren
2018-11-28 12:52       ` Peter Ujfalusi
2018-11-28 12:52         ` Peter Ujfalusi
2018-11-29 19:07         ` Tony Lindgren
2018-11-29 19:07           ` Tony Lindgren
2018-09-25  5:14 ` [PATCH 0/4] Update am437x and am335x dts to probe " Keerthy
2018-09-25  5:14   ` Keerthy
2018-09-25 14:40   ` Tony Lindgren
2018-09-25 14:40     ` Tony Lindgren
2018-09-25 17:55     ` Tony Lindgren
2018-09-25 17:55       ` Tony Lindgren
2018-09-25 21:16       ` Grygorii Strashko
2018-09-25 21:16         ` Grygorii Strashko
2018-09-26  4:08       ` Keerthy
2018-09-26  4:08         ` Keerthy
2018-09-26 15:59         ` Tony Lindgren
2018-09-26 15:59           ` Tony Lindgren
2018-09-26 16:23           ` Tony Lindgren
2018-09-26 16:23             ` Tony Lindgren
2018-09-26 21:36             ` Grygorii Strashko
2018-09-26 21:36               ` Grygorii Strashko
2018-09-26 23:31               ` Tony Lindgren
2018-09-26 23:31                 ` Tony Lindgren
2018-09-27  4:55                 ` Keerthy
2018-09-27  4:55                   ` Keerthy
2018-09-27 14:53                   ` Tony Lindgren
2018-09-27 14:53                     ` Tony Lindgren
2018-09-27 21:43                     ` Tony Lindgren
2018-09-27 21:43                       ` Tony Lindgren
2018-10-01 16:32                   ` Tony Lindgren
2018-10-01 16:32                     ` Tony Lindgren
2018-10-04  4:29                     ` Keerthy
2018-10-04  4:29                       ` Keerthy
2018-10-04 14:23                       ` Tony Lindgren
2018-10-04 14:23                         ` Tony Lindgren
2018-09-27 19:11                 ` Grygorii Strashko
2018-09-27 19:11                   ` Grygorii Strashko
2018-09-27 19:38                   ` Tony Lindgren
2018-09-27 19:38                     ` 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=20180925000545.22931-1-tony@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=d-gerlach@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=j-keerthy@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=t-kristo@ti.com \
    /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.