From: Simon Horman <horms@kernel.org>
To: Grzegorz Nitka <grzegorz.nitka@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
Aleksandr Loktionov <aleksandr.loktionov@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next] ice: unify PHY FW loading status handler for E800 devices
Date: Wed, 15 Oct 2025 09:44:38 +0100 [thread overview]
Message-ID: <aO9e9ix2jHA30pY0@horms.kernel.org> (raw)
In-Reply-To: <20251014084618.2746755-1-grzegorz.nitka@intel.com>
On Tue, Oct 14, 2025 at 10:46:18AM +0200, Grzegorz Nitka wrote:
> Unify handling of PHY firmware load delays across all E800 family
> devices. There is an existing mechanism to poll GL_MNG_FWSM_FW_LOADING_M
> bit of GL_MNG_FWSM register in order to verify whether PHY FW loading
> completed or not. Previously, this logic was limited to E827 variants
> only.
>
> Also, inform a user of possible delay in initialization process, by
> dumping informational message in dmesg log.
>
> Signed-off-by: Grzegorz Nitka <grzegorz.nitka@intel.com>
> Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
Reviewed-by: Simon Horman <horms@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@kernel.org>
To: Grzegorz Nitka <grzegorz.nitka@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
Aleksandr Loktionov <aleksandr.loktionov@intel.com>
Subject: Re: [PATCH iwl-next] ice: unify PHY FW loading status handler for E800 devices
Date: Wed, 15 Oct 2025 09:44:38 +0100 [thread overview]
Message-ID: <aO9e9ix2jHA30pY0@horms.kernel.org> (raw)
In-Reply-To: <20251014084618.2746755-1-grzegorz.nitka@intel.com>
On Tue, Oct 14, 2025 at 10:46:18AM +0200, Grzegorz Nitka wrote:
> Unify handling of PHY firmware load delays across all E800 family
> devices. There is an existing mechanism to poll GL_MNG_FWSM_FW_LOADING_M
> bit of GL_MNG_FWSM register in order to verify whether PHY FW loading
> completed or not. Previously, this logic was limited to E827 variants
> only.
>
> Also, inform a user of possible delay in initialization process, by
> dumping informational message in dmesg log.
>
> Signed-off-by: Grzegorz Nitka <grzegorz.nitka@intel.com>
> Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2025-10-15 8:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 8:46 [Intel-wired-lan] [PATCH iwl-next] ice: unify PHY FW loading status handler for E800 devices Grzegorz Nitka
2025-10-14 8:46 ` Grzegorz Nitka
2025-10-15 8:44 ` Simon Horman [this message]
2025-10-15 8:44 ` Simon Horman
2025-10-16 15:53 ` [Intel-wired-lan] " Paul Menzel
2025-10-17 8:45 ` Nitka, Grzegorz
2025-10-17 8:45 ` Nitka, Grzegorz
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=aO9e9ix2jHA30pY0@horms.kernel.org \
--to=horms@kernel.org \
--cc=aleksandr.loktionov@intel.com \
--cc=grzegorz.nitka@intel.com \
--cc=intel-wired-lan@lists.osuosl.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: link
Be 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.