All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Josua Mayer <josua@solid-run.com>,
	U-Boot-Denx <u-boot@lists.denx.de>,
	Yazan Shhady <yazan.shhady@solid-run.com>,
	Stefano Babic <sbabic@denx.de>,
	"NXP i.MX U-Boot Team" <uboot-imx@nxp.com>,
	Baruch Siach <baruch@tkos.co.il>,
	Marcel Ziswiler <marcel.ziswiler@toradex.com>
Subject: Re: [PATCH] mx6cuboxi: fix ethernet after synchronise device-tree
Date: Thu, 28 Jul 2022 08:01:44 -0400	[thread overview]
Message-ID: <20220728120144.GH1146598@bill-the-cat> (raw)
In-Reply-To: <CAOMZO5AbtM2DobDCrgaWksdxjsJ6H6u6WX6aRTMSKcXYrpUZtQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1492 bytes --]

On Thu, Jul 28, 2022 at 08:51:01AM -0300, Fabio Estevam wrote:
> Hi Tom,
> 
> On Thu, Jul 28, 2022 at 8:41 AM Tom Rini <trini@konsulko.com> wrote:
> >
> > On Thu, Jul 28, 2022 at 10:05:40AM +0300, Josua Mayer wrote:
> >
> > > The i.MX6 Cubox-i and HummingBoards can have different PHYs at varying
> > > addresses. U-Boot needs to auto-detect which phy is actually present,
> > > and at which address it is responding.
> > >
> > > Auto-detection from multiple phy nodes specified in device-tree does not
> > > currently work correct. As a work-around merge all three possible phys
> > > into one node with the special address 0xffffffff which indicates to the
> > > generic phy driver to probe all addresses.
> > > Also fixup this fake address before booting Linux, *if* booting with
> > > U-Boot's internal dtb.
> > >
> > > Signed-off-by: Josua Mayer <josua@solid-run.com>
> > > Fixes: d0399a46e7cd
> >
> > Tested-by: Tom Rini <trini@konsulko.com>
> 
> It's great that it worked, but if we take the patch as-is, then we
> will run into issues again in the future
> when a new re-sync is done.

Agreed.

> I see two alternatives:
> 
> 1. Make the arch/arm/dts/imx6qdl-sr-som.dtsi changes into
> arch/arm/dts/imx6qdl-sr-som-u-boot.dtsi, so that the main dtsi can
> still be used from Linux.
> 
> 2. Make the same dtsi work for both Linux and U-Boot.
> 
> What do you think?

If we can make #2 work that would be the best path forward I hope.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

      reply	other threads:[~2022-07-28 12:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220728070540.28554-1-josua@solid-run.com>
2022-07-28  7:08 ` [PATCH] mx6cuboxi: fix ethernet after synchronise device-tree Josua Mayer
2022-07-28 11:11   ` Fabio Estevam
2022-07-28 11:16   ` Tom Rini
2024-03-27 12:06   ` Josua Mayer
2024-03-27 12:17     ` Christian Gmeiner
2024-03-27 13:20       ` Josua Mayer
2024-03-27 15:55         ` Christian Gmeiner
2024-03-27 16:54           ` Josua Mayer
2024-03-27 19:29     ` Fabio Estevam
2024-03-27 21:04       ` Fabio Estevam
2024-03-27 23:17         ` Fabio Estevam
2024-03-28  7:08           ` Christian Gmeiner
2022-07-28 11:41 ` Tom Rini
2022-07-28 11:51   ` Fabio Estevam
2022-07-28 12:01     ` Tom Rini [this message]

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=20220728120144.GH1146598@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=baruch@tkos.co.il \
    --cc=festevam@gmail.com \
    --cc=josua@solid-run.com \
    --cc=marcel.ziswiler@toradex.com \
    --cc=sbabic@denx.de \
    --cc=u-boot@lists.denx.de \
    --cc=uboot-imx@nxp.com \
    --cc=yazan.shhady@solid-run.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.