From: <Arun.Ramadoss@microchip.com>
To: <andrew@lunn.ch>
Cc: <linux@armlinux.org.uk>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <davem@davemloft.net>,
<hkallweit1@gmail.com>, <kuba@kernel.org>
Subject: Re: [RFC PATCH net-next 1/4] net: phy: used the genphy_soft_reset for phy reset in Lan87xx
Date: Wed, 2 Mar 2022 10:04:07 +0000 [thread overview]
Message-ID: <a7c3b0d4a8001146b774a4b831be860afded533c.camel@microchip.com> (raw)
In-Reply-To: <Yh7iJpT0H1+3RncS@lunn.ch>
On Wed, 2022-03-02 at 04:19 +0100, Andrew Lunn wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> On Mon, Feb 28, 2022 at 07:35:07PM +0530, Arun Ramadoss wrote:
> > Replaced current code for soft resetting phy to genphy_soft_reset
> > function. And added the macro for LAN87xx Phy ID.
>
> Hi Arun
>
> Please don't mix multiple things in one patch.
>
> Looking at the actual path, you have:
>
> > +#define LAN87XX_PHY_ID 0x0007c150
> > +#define MICROCHIP_PHY_ID_MASK 0xfffffff0
>
> Part of macros for PHY ID.
>
> > +
> > /* External Register Control Register */
> > #define LAN87XX_EXT_REG_CTL (0x14)
> > #define LAN87XX_EXT_REG_CTL_RD_CTL (0x1000)
> > @@ -197,20 +200,10 @@ static int lan87xx_phy_init(struct phy_device
> > *phydev)
> > if (rc < 0)
> > return rc;
> >
> > - /* Soft Reset the SMI block */
> > - rc = access_ereg_modify_changed(phydev, PHYACC_ATTR_BANK_SMI,
> > - 0x00, 0x8000, 0x8000);
> > - if (rc < 0)
> > - return rc;
> > -
> > - /* Check to see if the self-clearing bit is cleared */
> > - usleep_range(1000, 2000);
> > - rc = access_ereg(phydev, PHYACC_ATTR_MODE_READ,
> > - PHYACC_ATTR_BANK_SMI, 0x00, 0);
> > + /* phy Soft reset */
> > + rc = genphy_soft_reset(phydev);
> > if (rc < 0)
> > return rc;
> > - if ((rc & 0x8000) != 0)
> > - return -ETIMEDOUT;
>
> Soft reset.
>
> >
> > /* PHY Initialization */
> > for (i = 0; i < ARRAY_SIZE(init); i++) {
> > @@ -273,6 +266,9 @@ static int lan87xx_config_init(struct
> > phy_device *phydev)
> > {
> > int rc = lan87xx_phy_init(phydev);
> >
> > + if (rc < 0)
> > + phydev_err(phydev, "failed to initialize phy\n");
> > +
>
> A new error message.
>
> > return rc < 0 ? rc : 0;
> > }
> >
> > @@ -506,18 +502,14 @@ static int
> > lan87xx_cable_test_get_status(struct phy_device *phydev,
> >
> > static struct phy_driver microchip_t1_phy_driver[] = {
> > {
> > - .phy_id = 0x0007c150,
> > - .phy_id_mask = 0xfffffff0,
> > - .name = "Microchip LAN87xx T1",
> > + .phy_id = LAN87XX_PHY_ID,
> > + .phy_id_mask = MICROCHIP_PHY_ID_MASK,
>
> 2nd part of the PHY ID macros.
>
> > + .name = "LAN87xx T1",
>
> A change in name.
>
> > .flags = PHY_POLL_CABLE_TEST,
> > -
> > .features = PHY_BASIC_T1_FEATURES,
> > -
> > .config_init = lan87xx_config_init,
> > -
> > .config_intr = lan87xx_phy_config_intr,
> > .handle_interrupt = lan87xx_handle_interrupt,
> > -
>
> White space changes.
>
> You can also use PHY_ID_MATCH_MODEL().
>
> Andrew
Thanks for the comment. I will keep one change per patch and split this
patch & resend.
next prev parent reply other threads:[~2022-03-02 10:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 14:05 [RFC PATCH net-next 0/4] Add support for LAN937x T1 Phy Arun Ramadoss
2022-02-28 14:05 ` [RFC PATCH net-next 1/4] net: phy: used the genphy_soft_reset for phy reset in Lan87xx Arun Ramadoss
2022-03-02 3:19 ` Andrew Lunn
2022-03-02 10:04 ` Arun.Ramadoss [this message]
2022-02-28 14:05 ` [RFC PATCH net-next 2/4] net: phy: updated the initialization routine for LAN87xx Arun Ramadoss
2022-02-28 14:05 ` [RFC PATCH net-next 3/4] net: phy: added the LAN937x phy support Arun Ramadoss
2022-03-02 3:22 ` Andrew Lunn
2022-03-02 9:57 ` Arun.Ramadoss
2022-02-28 14:05 ` [RFC PATCH net-next 4/4] net: phy: added master-slave config and cable diagnostics for Lan937x Arun Ramadoss
2022-02-28 14:12 ` Russell King (Oracle)
2022-03-01 16:59 ` Arun.Ramadoss
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=a7c3b0d4a8001146b774a4b831be860afded533c.camel@microchip.com \
--to=arun.ramadoss@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.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 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®