From: Heiner Kallweit <hkallweit1@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>, Andrew Lunn <andrew+netdev@lunn.ch>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: [PATCH net-next v2 0/2] net: phy: fixed_phy: replace list of fixed PHYs with static array
Date: Sun, 11 Jan 2026 13:40:30 +0100 [thread overview]
Message-ID: <110f676d-727c-4575-abe4-e383f98fc38f@gmail.com> (raw)
Due to max 32 PHY addresses being available per mii bus, using a list
can't support more fixed PHY's. And there's no known use case for as
much as 32 fixed PHY's on a system. 8 should be plenty of fixed PHY's,
so use an array of that size instead of a list. This allows to
significantly reduce the code size and complexity.
In addition replace heavy-weight IDA with a simple bitmap.
Heiner Kallweit (2):
net: phy: fixed_phy: replace list of fixed PHYs with static array
net: phy: fixed_phy: replace IDA with a bitmap
drivers/net/phy/fixed_phy.c | 83 +++++++++++++------------------------
1 file changed, 29 insertions(+), 54 deletions(-)
--
2.52.0
next reply other threads:[~2026-01-11 12:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-11 12:40 Heiner Kallweit [this message]
2026-01-11 12:41 ` [PATCH net-next v2 1/2] net: phy: fixed_phy: replace list of fixed PHYs with static array Heiner Kallweit
2026-01-11 12:43 ` [PATCH net-next v2 2/2] net: phy: fixed_phy: replace IDA with a bitmap Heiner Kallweit
2026-01-12 10:36 ` [PATCH net-next v2 0/2] net: phy: fixed_phy: replace list of fixed PHYs with static array Maxime Chevallier
2026-01-14 3:00 ` patchwork-bot+netdevbpf
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=110f676d-727c-4575-abe4-e383f98fc38f@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--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 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.