mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: micrel ksz8081 RMII phy and clause-22 broadcast
Date: Wed, 16 Oct 2024 23:43:31 +0200	[thread overview]
Message-ID: <8bbe2e1a-3ff0-4cf2-8d46-5f806f112925@lunn.ch> (raw)
In-Reply-To: <20241016-kissing-baffle-da66ca25d14a@thorsis.com>

> Would be happy if anyone could suggest a path forward here?

The hardware is different, so have a different dts file. You can then
list the PHY at is real address, which will stop the phantom broadcast
address PHY being created, and use a phy-handle to point to the real
PHYs, so when the phantom broadcast PHY is disabled, it does not
matter.

I would say that listing multiple PHYS is just an opportunistic hack,
which might work for simple cases, but soon leads to difficulties as
the situation gets complex.

	Andrew

  reply	other threads:[~2024-10-16 21:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-16 15:43 Alexander Dahl
2024-10-16 21:43 ` Andrew Lunn [this message]
2024-10-17  6:29   ` Alexander Dahl

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=8bbe2e1a-3ff0-4cf2-8d46-5f806f112925@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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

all inboxes | Powered by JetHome®