From: Jon Hunter <jonathanh@nvidia.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>, Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Brad Griffis <bgriffis@nvidia.com>
Subject: Re: [RESEND PATCH net-next v3 2/4] net: phy: aquantia: wait for FW reset before checking the vendor ID
Date: Tue, 30 Jul 2024 10:59:59 +0100 [thread overview]
Message-ID: <8ac00a45-ac61-41b4-9f74-d18157b8b6bf@nvidia.com> (raw)
In-Reply-To: <20240708075023.14893-3-brgl@bgdev.pl>
Hi Bartosz,
On 08/07/2024 08:50, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> Checking the firmware register before it complete the boot process makes
> no sense, it will report 0 even if FW is available from internal memory.
> Always wait for FW to boot before continuing or we'll unnecessarily try
> to load it from nvmem/filesystem and fail.
>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> ---
> drivers/net/phy/aquantia/aquantia_firmware.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/net/phy/aquantia/aquantia_firmware.c b/drivers/net/phy/aquantia/aquantia_firmware.c
> index 0c9640ef153b..524627a36c6f 100644
> --- a/drivers/net/phy/aquantia/aquantia_firmware.c
> +++ b/drivers/net/phy/aquantia/aquantia_firmware.c
> @@ -353,6 +353,10 @@ int aqr_firmware_load(struct phy_device *phydev)
> {
> int ret;
>
> + ret = aqr_wait_reset_complete(phydev);
> + if (ret)
> + return ret;
> +
> /* Check if the firmware is not already loaded by pooling
> * the current version returned by the PHY. If 0 is returned,
> * no firmware is loaded.
Although this fixed another issue we were seeing with this driver, we
have been reviewing this change and have a question about it.
According to the description for the function aqr_wait_reset_complete()
this function is intended to give the device time to load firmware and
check there is a valid firmware ID.
If a valid firmware ID (non-zero) is detected, then
aqr_wait_reset_complete() will return 0 (because
phy_read_mmd_poll_timeout() returns 0 on success and -ETIMEDOUT upon a
timeout).
If it times out, then it would appear that with the above code we don't
attempt to load the firmware by any other means?
Hence, I was wondering if we want this ...
diff --git a/drivers/net/phy/aquantia/aquantia_firmware.c
b/drivers/net/phy/aquantia/aquantia_firmware.c
index 524627a36c6f..a167f42ae36b 100644
--- a/drivers/net/phy/aquantia/aquantia_firmware.c
+++ b/drivers/net/phy/aquantia/aquantia_firmware.c
@@ -353,16 +353,12 @@ int aqr_firmware_load(struct phy_device *phydev)
{
int ret;
- ret = aqr_wait_reset_complete(phydev);
- if (ret)
- return ret;
-
- /* Check if the firmware is not already loaded by pooling
+ /* Check if the firmware is not already loaded by polling
* the current version returned by the PHY. If 0 is returned,
- * no firmware is loaded.
+ * firmware is loaded.
*/
- ret = phy_read_mmd(phydev, MDIO_MMD_VEND1, VEND1_GLOBAL_FW_ID);
- if (ret > 0)
+ ret = aqr_wait_reset_complete(phydev);
+ if (!ret)
goto exit;
ret = aqr_firmware_load_nvmem(phydev);
Our Aquantia PHY has a SPI-NOR and so we don't to test the other
firmware loading cases.
Jon
--
nvpublic
next prev parent reply other threads:[~2024-07-30 10:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 7:50 [RESEND PATCH net-next v3 0/4] net: phy: aquantia: enable support for aqr115c Bartosz Golaszewski
2024-07-08 7:50 ` [RESEND PATCH net-next v3 1/4] net: phy: aquantia: rename and export aqr107_wait_reset_complete() Bartosz Golaszewski
2024-07-08 7:50 ` [RESEND PATCH net-next v3 2/4] net: phy: aquantia: wait for FW reset before checking the vendor ID Bartosz Golaszewski
2024-07-30 9:59 ` Jon Hunter [this message]
2024-07-30 11:23 ` Russell King (Oracle)
2024-08-06 11:36 ` Vladimir Oltean
2024-08-06 11:27 ` Vladimir Oltean
2024-07-08 7:50 ` [RESEND PATCH net-next v3 3/4] net: phy: aquantia: wait for the GLOBAL_CFG to start returning real values Bartosz Golaszewski
2024-07-18 12:23 ` Jon Hunter
2024-07-18 13:04 ` Bartosz Golaszewski
2024-07-18 13:29 ` Bartosz Golaszewski
2024-07-18 14:08 ` Jon Hunter
2024-07-18 14:13 ` Bartosz Golaszewski
2024-07-18 14:49 ` Jon Hunter
2024-07-18 14:59 ` Bartosz Golaszewski
2024-07-18 17:42 ` Jon Hunter
2024-07-18 19:05 ` Bartosz Golaszewski
2024-07-19 8:39 ` Jon Hunter
2024-07-19 3:41 ` Andrew Lunn
2024-07-08 7:50 ` [RESEND PATCH net-next v3 4/4] net: phy: aquantia: add support for aqr115c Bartosz Golaszewski
2024-07-10 10:20 ` [RESEND PATCH net-next v3 0/4] net: phy: aquantia: enable " patchwork-bot+netdevbpf
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=8ac00a45-ac61-41b4-9f74-d18157b8b6bf@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=andrew@lunn.ch \
--cc=bartosz.golaszewski@linaro.org \
--cc=bgriffis@nvidia.com \
--cc=brgl@bgdev.pl \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).