From: Kyle Switch <kyle.switch@motor-comm.com>
To: David Yang <mmyangfl@gmail.com>
Cc: andrew@lunn.ch, olteanv@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, linux@armlinux.org.uk, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, ming.xu@motor-comm.com,
xiaolin.xu@motor-comm.com, jianmin.wang@motor-comm.com,
wei.zhang@gl-inet.com, sijia.huang@gl-inet.com
Subject: Re: [PATCH net-next v14 3/5] net: dsa: motorcomm: use fixed-width GENMASK_U*() helpers
Date: Sun, 18 Oct 2026 11:26:20 +0800 [thread overview]
Message-ID: <7701a2c8-e945-489d-993b-d872d7852fce@motor-comm.com> (raw)
In-Reply-To: <CAAXyoMMw5ygXT7vO-GWWodY1HRuf+SgyfcaLenqnUGUvjTxjOg@mail.gmail.com>
On 10/17/26 03:38, David Yang wrote:
> On Tue, Oct 13, 2026 at 9:11 AM Kyle Switch <kyle.switch@motor-comm.com> wrote:
>> @@ -36,19 +36,19 @@
>> static const struct yt921x_info yt921x_infos[] = {
>> {
>> "YT9215SC", YT9215_MAJOR, 1, 0,
>> - GENMASK(4, 0),
>> + GENMASK_U16(4, 0),
>> BIT(9),
>> BIT(8) | BIT(9),
>> },
>> {
>> "YT9215S", YT9215_MAJOR, 2, 0,
>> - GENMASK(4, 0),
>> + GENMASK_U16(4, 0),
>> BIT(9),
>> BIT(8),
>> },
>> {
>> "YT9215RB", YT9215_MAJOR, 3, 0,
>> - GENMASK(4, 0),
>> + GENMASK_U16(4, 0),
>> BIT(8) | BIT(9),
>> 0,
>> },
>> @@ -66,13 +66,13 @@ static const struct yt921x_info yt921x_infos[] = {
>> },
>> {
>> "YT9218N", YT9218_MAJOR, 0, 0,
>> - GENMASK(7, 0),
>> + GENMASK_U16(7, 0),
>> 0,
>> 0,
>> },
>> {
>> "YT9218MB", YT9218_MAJOR, 1, 0,
>> - GENMASK(7, 0),
>> + GENMASK_U16(7, 0),
>> BIT(8) | BIT(9),
>> BIT(8) | BIT(9),
>> },
>> @@ -3741,7 +3741,7 @@ static int yt921x_chip_setup_dsa(struct yt921x_priv *priv)
>> if (res)
>> return res;
>>
>> - ctrl = GENMASK(10, 0);
>> + ctrl = GENMASK_U32(10, 0);
>> res = yt921x_reg_write(priv, YT921X_FILTER_UNK_UCAST, ctrl);
>> if (res)
>> return res;
> The change below is fine, but the ones above aren't, the width is
> already pinned by the variable being assigned to. Also DSA expects u32
> port masks to some extent, those add unnecessary changes if you want
> to change port masks in yt921x_info to u32 some day.
you're right, It may work for the current definition, but it's not
conducive to future expansion. In future series, there will be
multi-port scenarios.
will be fixed in next patch version.
>
>> diff --git a/drivers/net/dsa/motorcomm/mdio_bus.c b/drivers/net/dsa/motorcomm/mdio_bus.c
>> index 83f0212551ff..3aa1111efaa4 100644
>> --- a/drivers/net/dsa/motorcomm/mdio_bus.c
>> +++ b/drivers/net/dsa/motorcomm/mdio_bus.c
>> @@ -159,7 +159,7 @@ int yt921x_mbus_int_init(struct yt921x_priv *priv, struct device_node *mnp)
>> mbus->write = yt921x_mbus_int_write;
>> mbus->parent = dev;
>> max_ports = priv->series->max_ports;
>> - mbus->phy_mask = (u32)~GENMASK(max_ports - 1, 0);
>> + mbus->phy_mask = ~GENMASK_U32(max_ports - 1, 0);
>>
>> res = devm_of_mdiobus_register(dev, mbus, mnp);
>> if (res)
>> --
>> 2.25.1
>>
next prev parent reply other threads:[~2026-10-18 3:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 1:11 [PATCH net-next v14 0/5] net: dsa: motorcomm: add support yt922x driver Kyle Switch
2026-10-13 1:11 ` [PATCH net-next v14 1/5] net: dsa: motorcomm: initialize dsa_switch based on chipid Kyle Switch
2026-10-14 1:59 ` netdev-bot+sashiko
2026-10-13 1:11 ` [PATCH net-next v14 2/5] net: dsa: motorcomm: use max_ports in series for port bounds checking Kyle Switch
2026-10-13 1:11 ` [PATCH net-next v14 3/5] net: dsa: motorcomm: use fixed-width GENMASK_U*() helpers Kyle Switch
2026-10-14 1:59 ` netdev-bot+sashiko
2026-10-16 19:38 ` David Yang
2026-10-18 3:26 ` Kyle Switch [this message]
2026-10-13 1:11 ` [PATCH net-next v14 4/5] net: dsa: tag_yt922x: add support for Motorcomm YT922x tags Kyle Switch
2026-10-14 1:59 ` netdev-bot+sashiko
2026-10-13 1:11 ` [PATCH net-next v14 5/5] net: dsa: motorcomm: Add support for Motorcomm YT922x Kyle Switch
2026-10-13 1:51 ` Andrew Lunn
2026-10-18 3:10 ` Kyle Switch
2026-10-14 1:59 ` netdev-bot+sashiko
2026-10-16 20:15 ` David Yang
2026-10-18 3:02 ` Kyle Switch
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=7701a2c8-e945-489d-993b-d872d7852fce@motor-comm.com \
--to=kyle.switch@motor-comm.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jianmin.wang@motor-comm.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=ming.xu@motor-comm.com \
--cc=mmyangfl@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=sijia.huang@gl-inet.com \
--cc=wei.zhang@gl-inet.com \
--cc=xiaolin.xu@motor-comm.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