mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Renaud Barbier <Renaud.Barbier@ametek.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: RE: [PATCH v2 4/4] ARM: ls1021a: initial Ethernet and mdio configuration
Date: Mon, 9 Feb 2026 17:46:09 +0000	[thread overview]
Message-ID: <SJ0PR07MB97664D4DEF1BA1F1FD1DB1EDEC65A@SJ0PR07MB9766.namprd07.prod.outlook.com> (raw)
In-Reply-To: <aYnyr03HdE8B-b5o@pengutronix.de>



> > +&enet0 {
> > +     status = "disabled";
> > +};
> > +
> > +&enet1 {
> > +     tbi-handle = <&tbi1>;
> > +     phy-handle = <&phy3>;
> > +     phy-mode = "sgmii";
> > +     /* Disable property as transmit fails without a DMA sync */
> > +     /delete-property/ dma-coherent;
> > +};
> > +
> > +&enet2 {
> > +     status = "disabled";
> > +};
> > +
> > +&mdio0 {
> > +     /* Rename the compatible name property as the mdio register offset
> > +      * in the gianfar driver depends on this name. Once the driver
> > +      * is in sync with Linux, it may be gone.
> > +      */
> > +     compatible = "fsl,etsec2-mdio";
> 
> What am I missing here? The "fsl,etsec2-mdio" compatible is introduced in
> your patch series and the original "gianfar" compatible is unused in barebox,
> so why not use the original "gianfar" compatible?

This looks like a brain meltdown. Working on it.

> 
> Sascha
> 
> --
> Pengutronix e.K.                           |                             |
> Steuerwalder Str. 21                       |
> https://urldefense.com/v3/__http://www.pengutronix.de/__;!!HKOSU0g!EYn
> wk0KOC4uaZ6o2g405vX9jY5cYxTXggB3OWKRK4fkhKYQkD1ipDYAvpoXwCD1xI
> ouD69egxnltsNg0UUl0r8QgLw$   |
> 31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



      reply	other threads:[~2026-02-09 17:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-04 11:46 [PATCH v2 0/4] net: expand gianfar support to ls1021a Renaud Barbier
2026-02-04 11:46 ` [PATCH v2 1/4] net: gianfar: disable link information Renaud Barbier
2026-02-04 11:46 ` [PATCH v2 2/4] gianfar: apply checkpatch recommendations Renaud Barbier
2026-02-04 11:46 ` [PATCH v2 3/4] net:gianfar: add device tree support Renaud Barbier
2026-02-04 11:46 ` [PATCH v2 4/4] ARM: ls1021a: initial Ethernet and mdio configuration Renaud Barbier
2026-02-09 14:43   ` Sascha Hauer
2026-02-09 17:46     ` Renaud Barbier [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=SJ0PR07MB97664D4DEF1BA1F1FD1DB1EDEC65A@SJ0PR07MB9766.namprd07.prod.outlook.com \
    --to=renaud.barbier@ametek.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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