From: Bo Shen <voice.shen@atmel.com> To: Florian Fainelli <f.fainelli@gmail.com> Cc: netdev <netdev@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org> Subject: Re: [RFC PATCH] phy: micrel: make phy_has_fixups attribute read correctly Date: Fri, 27 Jun 2014 11:33:11 +0800 [thread overview] Message-ID: <53ACE5F7.3060102@atmel.com> (raw) In-Reply-To: <CAGVrzcaN9KKW6vN5Xy775RTBD3ODpK95-o0V+pKDcCCxetPycA@mail.gmail.com> Hi Florian, On 06/27/2014 02:00 AM, Florian Fainelli wrote: > Hello, > > 2014-06-25 0:24 GMT-07:00 Bo Shen <voice.shen@atmel.com>: >> If the fixups parameters get from dtb, it won't set has_fixups >> parameters, so when read phy_has_fixups attribute, it always >> present as 0. >> Add this patch to make phy_has_fixups attribute read correctly. > > I am not entirely sure whether loading values from Device Tree should > be considered a PHY fixup per-se. They do override the hardware reset > default values, but I am not sure if we should consider that as a > fixup. In old method, we will call phy_register_fixup_for_uid to update this configuration, which will set the phy_has_fixups as true, then it regards as fix up. So, can we also consider loading values from DTS also as fix up? > Assuming that you need to troubleshoot a given system, one of the > first things you will surely ask for is the DTS used by that platform, > and in that case you can quickly check whether the PHY default > settings are changed, right? I am not sure I am fully understand here. The value retrieve from DTS is used to overwrite the default value, so I think it is no need to check. >> >> Signed-off-by: Bo Shen <voice.shen@atmel.com> >> --- >> drivers/net/phy/micrel.c | 4 ++++ >> 1 file changed, 4 insertions(+) >> >> diff --git a/drivers/net/phy/micrel.c b/drivers/net/phy/micrel.c >> index bc7c7d2..c384922 100644 >> --- a/drivers/net/phy/micrel.c >> +++ b/drivers/net/phy/micrel.c >> @@ -237,6 +237,8 @@ static int ksz9021_load_values_from_of(struct phy_device *phydev, >> >> if (!matches) >> return 0; >> + else >> + phydev->has_fixups = true; > > There is no need for the else here > >> >> if (matches < 4) >> newval = kszphy_extended_read(phydev, reg); >> @@ -330,6 +332,8 @@ static int ksz9031_of_load_skew_values(struct phy_device *phydev, >> >> if (!matches) >> return 0; >> + else >> + phydev->has_fixups = true; > > Same here > >> >> if (matches < numfields) >> newval = ksz9031_extended_read(phydev, OP_DATA, 2, reg); >> -- >> 1.8.5.2 Best Regards, Bo Shen
WARNING: multiple messages have this Message-ID (diff)
From: voice.shen@atmel.com (Bo Shen) To: linux-arm-kernel@lists.infradead.org Subject: [RFC PATCH] phy: micrel: make phy_has_fixups attribute read correctly Date: Fri, 27 Jun 2014 11:33:11 +0800 [thread overview] Message-ID: <53ACE5F7.3060102@atmel.com> (raw) In-Reply-To: <CAGVrzcaN9KKW6vN5Xy775RTBD3ODpK95-o0V+pKDcCCxetPycA@mail.gmail.com> Hi Florian, On 06/27/2014 02:00 AM, Florian Fainelli wrote: > Hello, > > 2014-06-25 0:24 GMT-07:00 Bo Shen <voice.shen@atmel.com>: >> If the fixups parameters get from dtb, it won't set has_fixups >> parameters, so when read phy_has_fixups attribute, it always >> present as 0. >> Add this patch to make phy_has_fixups attribute read correctly. > > I am not entirely sure whether loading values from Device Tree should > be considered a PHY fixup per-se. They do override the hardware reset > default values, but I am not sure if we should consider that as a > fixup. In old method, we will call phy_register_fixup_for_uid to update this configuration, which will set the phy_has_fixups as true, then it regards as fix up. So, can we also consider loading values from DTS also as fix up? > Assuming that you need to troubleshoot a given system, one of the > first things you will surely ask for is the DTS used by that platform, > and in that case you can quickly check whether the PHY default > settings are changed, right? I am not sure I am fully understand here. The value retrieve from DTS is used to overwrite the default value, so I think it is no need to check. >> >> Signed-off-by: Bo Shen <voice.shen@atmel.com> >> --- >> drivers/net/phy/micrel.c | 4 ++++ >> 1 file changed, 4 insertions(+) >> >> diff --git a/drivers/net/phy/micrel.c b/drivers/net/phy/micrel.c >> index bc7c7d2..c384922 100644 >> --- a/drivers/net/phy/micrel.c >> +++ b/drivers/net/phy/micrel.c >> @@ -237,6 +237,8 @@ static int ksz9021_load_values_from_of(struct phy_device *phydev, >> >> if (!matches) >> return 0; >> + else >> + phydev->has_fixups = true; > > There is no need for the else here > >> >> if (matches < 4) >> newval = kszphy_extended_read(phydev, reg); >> @@ -330,6 +332,8 @@ static int ksz9031_of_load_skew_values(struct phy_device *phydev, >> >> if (!matches) >> return 0; >> + else >> + phydev->has_fixups = true; > > Same here > >> >> if (matches < numfields) >> newval = ksz9031_extended_read(phydev, OP_DATA, 2, reg); >> -- >> 1.8.5.2 Best Regards, Bo Shen
next prev parent reply other threads:[~2014-06-27 3:33 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-25 7:24 [RFC PATCH] phy: micrel: make phy_has_fixups attribute read correctly Bo Shen 2014-06-25 7:24 ` Bo Shen 2014-06-26 18:00 ` Florian Fainelli 2014-06-26 18:00 ` Florian Fainelli 2014-06-26 18:00 ` Florian Fainelli 2014-06-27 3:33 ` Bo Shen [this message] 2014-06-27 3:33 ` Bo Shen 2014-06-27 3:33 ` Bo Shen
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=53ACE5F7.3060102@atmel.com \ --to=voice.shen@atmel.com \ --cc=f.fainelli@gmail.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --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: linkBe 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.