From: <Parthiban.Veerasooran@microchip.com>
To: <simon.horman@corigine.com>
Cc: <andrew@lunn.ch>, <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 6/6] net: phy: microchip_t1s: add support for Microchip LAN865x Rev.B0 PHYs
Date: Tue, 23 May 2023 05:33:27 +0000 [thread overview]
Message-ID: <9c45a417-80c4-5c1f-243f-916292c741bd@microchip.com> (raw)
In-Reply-To: <ZGuD/dqpQl/2wpRY@corigine.com>
Hi Simon,
Thanks for your interest in reviewing my patches.
On 22/05/23 8:32 pm, Simon Horman wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Mon, May 22, 2023 at 05:03:31PM +0530, Parthiban Veerasooran wrote:
>> Add support for the Microchip LAN865x Rev.B0 10BASE-T1S Internal PHYs
>> (LAN8650/1). The LAN865x combines a Media Access Controller (MAC) and an
>> internal 10BASE-T1S Ethernet PHY to access 10BASE‑T1S networks. As
>> LAN867X and LAN865X are using the same function for the read_status,
>> rename the function as lan86xx_read_status.
>>
>> Signed-off-by: Parthiban Veerasooran <Parthiban.Veerasooran@microchip.com>
>
> Hi Parthiban,
>
> thanks for your patch.
> Some minor nits from my side.
>
> ...
>
>> +/* This is pulled straigt from AN1760 from 'calulation of offset 1' &
>> + * 'calculation of offset 2'
>> + */
>
> nit: s/straigt/straight/
Ah yes, surely will correct it in the next version.
>
>> +static int lan865x_generate_cfg_offsets(struct phy_device *phydev, s8 offsets[2])
>> +{
>> + const u16 fixup_regs[2] = {0x0004, 0x0008};
>> + int ret;
>> +
>> + for (int i = 0; i < ARRAY_SIZE(fixup_regs); i++) {
>> + ret = lan865x_revb0_indirect_read(phydev, fixup_regs[i]);
>> + if (ret < 0)
>> + return ret;
>> + if (ret & BIT(4))
>> + offsets[i] = ret | 0xE0;
>> + else
>> + offsets[i] = ret;
>> + }
>> +
>> + return 0;
>> +}
>
> ...
>
>> +static int lan865x_setup_cfgparam(struct phy_device *phydev)
>> +{
>> + u16 cfg_results[5];
>> + u16 cfg_params[ARRAY_SIZE(lan865x_revb0_fixup_cfg_regs)];
>> + s8 offsets[2];
>> + int ret;
>
> nit: Please use reverse xmas tree order - longest line to shortest -
> for local variable declarations in networking code.
Yes understood, surely will correct it in the next version.
Best Regards,
Parthiban V
>
> ...
prev parent reply other threads:[~2023-05-23 5:33 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
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 [this message]
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=9c45a417-80c4-5c1f-243f-916292c741bd@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 \
--cc=simon.horman@corigine.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®