From: <Parthiban.Veerasooran@microchip.com>
To: <andrew@lunn.ch>
Cc: <hkallweit1@gmail.com>, <linux@armlinux.org.uk>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<ramon.nordin.rodriguez@ferroamp.se>,
<Horatiu.Vultur@microchip.com>, <Woojung.Huh@microchip.com>,
<Nicolas.Ferre@microchip.com>,
<Thorsten.Kummermehr@microchip.com>
Subject: Re: [PATCH net-next v2 2/6] net: phy: microchip_t1s: replace read-modify-write code with phy_modify_mmd
Date: Tue, 23 May 2023 06:15:38 +0000 [thread overview]
Message-ID: <8f5ef5b1-ce52-1426-fe68-55c769885f9a@microchip.com> (raw)
In-Reply-To: <2c78f2cc-ff5e-4dcd-a309-de21a5725053@lunn.ch>
Hi Andrew,
On 22/05/23 6:01 pm, Andrew Lunn wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
>>
>> /* Read-Modified Write Pseudocode (from AN1699)
>> * current_val = read_register(mmd, addr) // Read current register value
>
> Hi Parthiban
>
> Maybe extend the comment to indicate that although AN1699 says Read,
> Modify, Write, the write is not required if the register already has
> the required value. That is what phy_modify_mmd() actually does.
Sure, I will add it in the next version.
Best Regards,
Parthiban V
>
>> @@ -74,12 +72,11 @@ static int lan867x_config_init(struct phy_device *phydev)
>> * write_register(mmd, addr, new_val) // Write back updated register value
>> */
>> for (int i = 0; i < ARRAY_SIZE(lan867x_fixup_registers); i++) {
>> - reg = lan867x_fixup_registers[i];
>> - reg_value = phy_read_mmd(phydev, MDIO_MMD_VEND2, reg);
>> - reg_value &= ~lan867x_fixup_masks[i];
>> - reg_value |= lan867x_fixup_values[i];
>> - err = phy_write_mmd(phydev, MDIO_MMD_VEND2, reg, reg_value);
>> - if (err != 0)
>> + err = phy_modify_mmd(phydev, MDIO_MMD_VEND2,
>> + lan867x_fixup_registers[i],
>> + lan867x_fixup_masks[i],
>> + lan867x_fixup_values[i]);
>> + if (err)
>> return err;
>> }
>
>
> Andrew
>
> ---
> pw-bot: cr
next prev parent reply other threads:[~2023-05-23 6:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 11:33 [PATCH net-next v2 0/6] microchip_t1s: Update on Microchip 10BASE-T1S PHY driver Parthiban Veerasooran
2023-05-22 11:33 ` [PATCH net-next v2 1/6] net: phy: microchip_t1s: modify driver description to be more generic Parthiban Veerasooran
2023-05-22 12:27 ` Andrew Lunn
2023-05-22 11:33 ` [PATCH net-next v2 2/6] net: phy: microchip_t1s: replace read-modify-write code with phy_modify_mmd Parthiban Veerasooran
2023-05-22 12:31 ` Andrew Lunn
2023-05-23 6:15 ` Parthiban.Veerasooran [this message]
2023-05-22 11:33 ` [PATCH net-next v2 3/6] net: phy: microchip_t1s: update LAN867x PHY supported revision number Parthiban Veerasooran
2023-05-22 12:38 ` Andrew Lunn
2023-05-23 6:25 ` Parthiban.Veerasooran
2023-05-22 11:33 ` [PATCH net-next v2 4/6] net: phy: microchip_t1s: fix reset complete status handling Parthiban Veerasooran
2023-05-22 12:43 ` Andrew Lunn
2023-05-23 5:30 ` Parthiban.Veerasooran
2023-05-23 12:23 ` Andrew Lunn
2023-05-24 7:24 ` Parthiban.Veerasooran
2023-05-24 7:31 ` Parthiban.Veerasooran
2023-05-24 12:03 ` Andrew Lunn
2023-05-24 13:21 ` Parthiban.Veerasooran
2023-05-22 11:33 ` [PATCH net-next v2 5/6] net: phy: microchip_t1s: remove unnecessary interrupts disabling code Parthiban Veerasooran
2023-05-22 12:45 ` Andrew Lunn
2023-05-22 11:33 ` [PATCH net-next v2 6/6] net: phy: microchip_t1s: add support for Microchip LAN865x Rev.B0 PHYs Parthiban Veerasooran
2023-05-22 12:56 ` Andrew Lunn
2023-05-23 6:13 ` Parthiban.Veerasooran
2023-05-23 12:29 ` Andrew Lunn
2023-05-24 7:25 ` Parthiban.Veerasooran
2023-05-22 15:02 ` Simon Horman
2023-05-23 5:33 ` Parthiban.Veerasooran
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=8f5ef5b1-ce52-1426-fe68-55c769885f9a@microchip.com \
--to=parthiban.veerasooran@microchip.com \
--cc=Horatiu.Vultur@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=Thorsten.Kummermehr@microchip.com \
--cc=Woojung.Huh@microchip.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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ramon.nordin.rodriguez@ferroamp.se \
/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®