mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefano Radaelli <stefano.radaelli21@gmail.com>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andrew Lunn <andrew@lunn.ch>
Cc: Xu Liang <lxu@maxlinear.com>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: [RFC] net: phy: mxl-86110: Manage broadcast configuration
Date: Fri, 12 Dec 2025 15:37:15 +0100	[thread overview]
Message-ID: <aTwom4FdQDcTyIdL@Lord-Beerus.station> (raw)

Hi all,

I am working with the MaxLinear MxL86110 PHY and I noticed that the
current driver only disables broadcast access inside mxl86110_broadcast_cfg().

However, according to the datasheet (Register A005h –
RGMII In-Band Status and MDIO Configuration Register), the PHY actually
supports multiple broadcast configuration modes:

- EPA0 (bit 6): enable/disable responding to broadcasts sent to PHY
  address 0.
- EBA (bit 5): enable/disable responding to broadcasts sent to an
  alternate broadcast address defined in BA.
- BA (bits 4:0): configurable broadcast address (0–31).

Given this, I would like to expose these capabilities to users.

Before implementing anything, I would like to ask for guidance on the
preferred way to expose these PHY settings to users. Specifically, I’m
uncertain whether such configuration should be handled through device
tree properties, PHY tunables, or any other mechanism considered more
appropriate within phylib.

Is there a recommended or established approach for enabling
user-configurable broadcast behaviour in PHY drivers?

Any feedback would be greatly appreciated. Once the preferred direction
is clear, I will prepare and submit a proper patch.

Thanks,
Stefano Radaelli

             reply	other threads:[~2025-12-12 14:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-12 14:37 Stefano Radaelli [this message]
2025-12-12 14:43 ` Andrew Lunn

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=aTwom4FdQDcTyIdL@Lord-Beerus.station \
    --to=stefano.radaelli21@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lxu@maxlinear.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 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®