From: "Théo Lebrun" <theo.lebrun@bootlin.com>
To: "James Clark" <jjc@jclark.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@kernel.org>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Richard Cochran" <richardcochran@gmail.com>,
"Florian Fainelli" <florian.fainelli@broadcom.com>,
"Doug Berger" <opendmb@gmail.com>,
"Nicolai Buchwitz" <nb@tipi-net.de>
Cc: "Russell King" <linux@armlinux.org.uk>,
"Conor Dooley" <conor.dooley@microchip.com>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"Thomas Gleixner" <tglx@kernel.org>,
"Miroslav Lichvar" <mlichvar@redhat.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Maxime Chevallier" <maxime.chevallier@bootlin.com>
Subject: Re: [PATCH net-next 4/5] net: macb: implement timestamped MDIO writes
Date: Sun, 11 Oct 2026 12:02:59 +0200 [thread overview]
Message-ID: <DM1X8RPY7556.2VHDX3Z5VKKM1@bootlin.com> (raw)
In-Reply-To: <DM1WEUIF8V8V.2OZWRB5G232T4@bootlin.com>
On Sun Oct 11, 2026 at 11:23 AM CEST, Théo Lebrun wrote:
>> -static int macb_mdio_write_c22(struct mii_bus *bus, int mii_id, int regnum,
>> - u16 value)
>> +static u64 macb_mdio_sts_delay(struct macb *bp)
>> +{
>> + static const u16 gem_divisors[] = {
>> + [GEM_CLK_DIV8] = 8,
>> + [GEM_CLK_DIV16] = 16,
>> + [GEM_CLK_DIV32] = 32,
>> + [GEM_CLK_DIV48] = 48,
>> + [GEM_CLK_DIV64] = 64,
>> + [GEM_CLK_DIV96] = 96,
>> + [GEM_CLK_DIV128] = 128,
>> + [GEM_CLK_DIV224] = 224,
>> + };
>> + static const u16 macb_divisors[] = {
>> + [MACB_CLK_DIV8] = 8,
>> + [MACB_CLK_DIV16] = 16,
>> + [MACB_CLK_DIV32] = 32,
>> + [MACB_CLK_DIV64] = 64,
>> + };
>
> Do I sound crazy if I say we could use a single array for both?
> Both GEM_CLK_DIV* and MACB_CLK_DIV* are enums and are ordered in the
> same way. First four GEM_* are the same ones as MACB_* and it will
> never change.
Ignore this comment because gem_divisors[3] != macb_divisors[3].
Thanks,
--
Théo Lebrun, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-10-11 10:03 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 14:35 [PATCH net-next 0/5] net: mdio: add timestamped MDIO writes for PHY gettimex64 James Clark
2026-10-09 14:35 ` [PATCH net-next 1/5] net: mdio: add timestamped write operation James Clark
2026-10-10 15:10 ` netdev-bot+sashiko
2026-10-11 14:03 ` Andrew Lunn
2026-10-11 14:33 ` James Clark
2026-10-09 14:35 ` [PATCH net-next 2/5] net: phy: broadcom: use timestamped MDIO writes in gettimex64 James Clark
2026-10-10 15:10 ` netdev-bot+sashiko
2026-10-09 14:35 ` [PATCH net-next 3/5] ptp: add functions to adjust system timestamps James Clark
2026-10-10 15:10 ` netdev-bot+sashiko
2026-10-09 14:35 ` [PATCH net-next 4/5] net: macb: implement timestamped MDIO writes James Clark
2026-10-10 15:10 ` netdev-bot+sashiko
2026-10-11 9:23 ` Théo Lebrun
2026-10-11 10:02 ` Théo Lebrun [this message]
2026-10-11 13:01 ` James Clark
2026-10-11 21:10 ` Andrew Lunn
2026-10-09 14:35 ` [PATCH net-next 5/5] net: mdio: bcm-unimac: " James Clark
2026-10-09 16:04 ` Florian Fainelli
2026-10-10 1:25 ` James Clark
2026-10-10 15:18 ` Nicolai Buchwitz
2026-10-11 7:20 ` James Clark
2026-10-11 13:22 ` Nicolai Buchwitz
2026-10-12 0:54 ` James Clark
2026-10-12 13:18 ` Nicolai Buchwitz
2026-10-12 11:51 ` Andrew Lunn
2026-10-12 13:21 ` Nicolai Buchwitz
2026-10-10 15:11 ` netdev-bot+sashiko
2026-10-12 12:03 ` Andrew Lunn
2026-10-10 4:55 ` [PATCH net-next 0/5] net: mdio: add timestamped MDIO writes for PHY gettimex64 James Clark
2026-10-11 13:50 ` Andrew Lunn
2026-10-11 14:00 ` James Clark
2026-10-11 18:07 ` Nicolai Buchwitz
2026-10-12 13:18 ` Andrew Lunn
2026-10-12 13:20 ` Nicolai Buchwitz
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=DM1X8RPY7556.2VHDX3Z5VKKM1@bootlin.com \
--to=theo.lebrun@bootlin.com \
--cc=andrew+netdev@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor.dooley@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=hkallweit1@gmail.com \
--cc=jjc@jclark.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=mlichvar@redhat.com \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=opendmb@gmail.com \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=tglx@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 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.