From: Simon Horman <horms@kernel.org>
To: Grzegorz Nitka <grzegorz.nitka@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
Karol Kolacinski <karol.kolacinski@intel.com>,
Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>
Subject: Re: [PATCH iwl-next v3 1/3] ice: remove SW side band access workaround for E825
Date: Sun, 23 Mar 2025 17:12:20 +0000 [thread overview]
Message-ID: <20250323171220.GT892515@horms.kernel.org> (raw)
In-Reply-To: <20250320131538.712326-2-grzegorz.nitka@intel.com>
On Thu, Mar 20, 2025 at 02:15:36PM +0100, Grzegorz Nitka wrote:
> From: Karol Kolacinski <karol.kolacinski@intel.com>
>
> Due to the bug in FW/NVM autoload mechanism (wrong default
> SB_REM_DEV_CTL register settings), the access to peer PHY and CGU
> clients was disabled by default.
>
> As the workaround solution, the register value was overwritten by the
> driver at the probe or reset handling.
> Remove workaround as it's not needed anymore. The fix in autoload
> procedure has been provided with NVM 3.80 version.
>
> NOTE: at the time the fix was provided in NVM, the E825C product was
> not officially available on the market, so it's not expected this change
> will cause regression when running with older driver/kernel versions.
>
> Reviewed-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> Signed-off-by: Karol Kolacinski <karol.kolacinski@intel.com>
> Signed-off-by: Grzegorz Nitka <grzegorz.nitka@intel.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2025-03-23 17:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 13:15 [PATCH iwl-next v3 0/3] E825C timesync dual NAC support Grzegorz Nitka
2025-03-20 13:15 ` [PATCH iwl-next v3 1/3] ice: remove SW side band access workaround for E825 Grzegorz Nitka
2025-03-23 17:12 ` Simon Horman [this message]
2025-04-04 10:52 ` [Intel-wired-lan] " Rinitha, SX
2025-03-20 13:15 ` [PATCH iwl-next v3 2/3] ice: refactor ice_sbq_msg_dev enum Grzegorz Nitka
2025-04-04 10:52 ` [Intel-wired-lan] " Rinitha, SX
2025-03-20 13:15 ` [PATCH iwl-next v3 3/3] ice: enable timesync operation on 2xNAC E825 devices Grzegorz Nitka
2025-04-04 10:52 ` [Intel-wired-lan] " Rinitha, SX
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=20250323171220.GT892515@horms.kernel.org \
--to=horms@kernel.org \
--cc=grzegorz.nitka@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=karol.kolacinski@intel.com \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.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).