From: Nishanth Menon <nm@ti.com>
To: Maxime Ripard <mripard@kernel.org>
Cc: <u-boot@lists.denx.de>, Tom Rini <trini@konsulko.com>,
Wadim Egorov <w.egorov@phytec.de>,
Francesco Dolcini <francesco@dolcini.it>,
Sjoerd Simons <sjoerd@collabora.com>,
Neha Malcom Francis <n-francis@ti.com>,
Bryan Brattlof <bb@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Mattijs Korpershoek <mkorpershoek@baylibre.com>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Roger Quadros <rogerq@kernel.org>
Subject: Re: [PATCH 3/3] arm: dts: k3-am62: Bump dtsi from linux v6.5-rc1
Date: Tue, 25 Jul 2023 09:09:34 -0500 [thread overview]
Message-ID: <20230725140934.wxo7ndfkfvem5xhs@excitable> (raw)
In-Reply-To: <j3lyjxcnh2p5oh56jwpsuh2xg4277pz365k33vvydxspyel6iu@7njcuj3q4lil>
On 15:56-20230725, Maxime Ripard wrote:
> Hi,
>
> On Tue, Jul 25, 2023 at 07:58:56AM -0500, Nishanth Menon wrote:
> > Update the am62 and am625 device-trees from linux v6.3-rc5 This needed the followin
> > tweaks to the u-boot specific dtsi as well:
> > - Switch tick-timer to the main_timer as it's now defined in the main dtsi
> > - Secure proxies are defined in Soc dtsis
> > - Drop duplicate nodes - u-boot.dtsi is includes in r5-sk, no need for
> > either the definitions from main.dtsi OR duplication from u-boot.dtsi
> > - Add mdio pins to the cpsw3g pinctrl in u-boot dtsi. It moved to a subnode in the
> > linux dtsi that u-boot doesn't use/support
> >
> > Cc: Francesco Dolcini <francesco@dolcini.it>
> > Cc: Sjoerd Simons <sjoerd@collabora.com>
> > Cc: Wadim Egorov <w.egorov@phytec.de>
> > Signed-off-by: Nishanth Menon <nm@ti.com>
> > ---
> >
> > I decided not to pick up changes from Roger and Maxime as they are'nt
> > regression fixes, instead the fixups can be done on top of the basic
> > sync.
>
> This breaks Linux network interfaces so I very much considers this a regression.
The current u-boot.dtsi I am confused - pinctrl mdio is still a
problem, is'nt it?
https://github.com/u-boot/u-boot/blob/master/arch/arm/dts/k3-am625-sk-u-boot.dtsi#L132
The follow on fixups from both your and Roger's series should fix things
up, correct?
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2023-07-25 14:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 12:58 [PATCH 0/3] arm: dts: Sync k3-am62 with upstream Nishanth Menon
2023-07-25 12:58 ` [PATCH 1/3] omap: timer: add ti,am654-timer compatibility Nishanth Menon
2023-07-25 12:58 ` [PATCH 2/3] arm: mach-k3: am62: Add timer0 id to the dev list Nishanth Menon
2023-07-25 12:58 ` [PATCH 3/3] arm: dts: k3-am62: Bump dtsi from linux v6.5-rc1 Nishanth Menon
2023-07-25 13:56 ` Maxime Ripard
2023-07-25 14:09 ` Nishanth Menon [this message]
2023-07-25 18:17 ` Tom Rini
2023-07-26 5:56 ` Ravi Gunasekaran
2023-07-26 8:15 ` Maxime Ripard
2023-07-26 12:51 ` Nishanth Menon
2023-07-26 13:36 ` Tom Rini
2023-07-26 14:19 ` Nishanth Menon
2023-07-26 8:05 ` Roger Quadros
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=20230725140934.wxo7ndfkfvem5xhs@excitable \
--to=nm@ti.com \
--cc=bb@ti.com \
--cc=francesco@dolcini.it \
--cc=marcel.ziswiler@toradex.com \
--cc=mkorpershoek@baylibre.com \
--cc=mripard@kernel.org \
--cc=n-francis@ti.com \
--cc=rogerq@kernel.org \
--cc=sjoerd@collabora.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
--cc=w.egorov@phytec.de \
/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