From: Simon Horman <horms@kernel.org>
To: Grzegorz Nitka <grzegorz.nitka@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
Karol Kolacinski <karol.kolacinski@intel.com>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH v3 iwl-net 2/4] ice: Fix quad registers read on E825
Date: Sat, 2 Nov 2024 15:10:33 +0000 [thread overview]
Message-ID: <20241102151033.GP1838431@kernel.org> (raw)
In-Reply-To: <20241028204543.606371-3-grzegorz.nitka@intel.com>
On Mon, Oct 28, 2024 at 09:45:41PM +0100, Grzegorz Nitka wrote:
> From: Karol Kolacinski <karol.kolacinski@intel.com>
>
> Quad registers are read/written incorrectly. E825 devices always use
> quad 0 address and differentiate between the PHYs by changing SBQ
> destination device (phy_0 or phy_0_peer).
>
> Add helpers for reading/writing PTP registers shared per quad and use
> correct quad address and SBQ destination device based on port.
>
> Rename rmn_0 to phy_0 and remove rmn_1 and rmn_2 as E82X HW does not
> support it. Rename eth56g_phy_1 to phy_0_peer.
>
> Fixes: 7cab44f1c35f ("ice: Introduce ETH56G PHY model for E825C products")
> Reviewed-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
> Signed-off-by: Karol Kolacinski <karol.kolacinski@intel.com>
> ---
> V2 -> V3: Replaced lower/upper_32_bits calls with lower/upper_16_bits
> V1 -> V2: Fixed kdoc issues
>
> drivers/net/ethernet/intel/ice/ice_common.c | 2 +-
> .../net/ethernet/intel/ice/ice_ptp_consts.h | 75 ++----
> drivers/net/ethernet/intel/ice/ice_ptp_hw.c | 237 +++++++++++-------
> drivers/net/ethernet/intel/ice/ice_ptp_hw.h | 37 ++-
> drivers/net/ethernet/intel/ice/ice_sbq_cmd.h | 7 +-
> drivers/net/ethernet/intel/ice/ice_type.h | 1 -
> 6 files changed, 177 insertions(+), 182 deletions(-)
This patch seems to mix bug fixes and cleanup.
Which leads to a rather large patch - larger than is desirable for stable IMHO.
Could we consider a more minimal fix for iwl-net.
And then follow-up with clean-ups for iwl?
...
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,
anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
Karol Kolacinski <karol.kolacinski@intel.com>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Subject: Re: [PATCH v3 iwl-net 2/4] ice: Fix quad registers read on E825
Date: Sat, 2 Nov 2024 15:10:33 +0000 [thread overview]
Message-ID: <20241102151033.GP1838431@kernel.org> (raw)
In-Reply-To: <20241028204543.606371-3-grzegorz.nitka@intel.com>
On Mon, Oct 28, 2024 at 09:45:41PM +0100, Grzegorz Nitka wrote:
> From: Karol Kolacinski <karol.kolacinski@intel.com>
>
> Quad registers are read/written incorrectly. E825 devices always use
> quad 0 address and differentiate between the PHYs by changing SBQ
> destination device (phy_0 or phy_0_peer).
>
> Add helpers for reading/writing PTP registers shared per quad and use
> correct quad address and SBQ destination device based on port.
>
> Rename rmn_0 to phy_0 and remove rmn_1 and rmn_2 as E82X HW does not
> support it. Rename eth56g_phy_1 to phy_0_peer.
>
> Fixes: 7cab44f1c35f ("ice: Introduce ETH56G PHY model for E825C products")
> Reviewed-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
> Signed-off-by: Karol Kolacinski <karol.kolacinski@intel.com>
> ---
> V2 -> V3: Replaced lower/upper_32_bits calls with lower/upper_16_bits
> V1 -> V2: Fixed kdoc issues
>
> drivers/net/ethernet/intel/ice/ice_common.c | 2 +-
> .../net/ethernet/intel/ice/ice_ptp_consts.h | 75 ++----
> drivers/net/ethernet/intel/ice/ice_ptp_hw.c | 237 +++++++++++-------
> drivers/net/ethernet/intel/ice/ice_ptp_hw.h | 37 ++-
> drivers/net/ethernet/intel/ice/ice_sbq_cmd.h | 7 +-
> drivers/net/ethernet/intel/ice/ice_type.h | 1 -
> 6 files changed, 177 insertions(+), 182 deletions(-)
This patch seems to mix bug fixes and cleanup.
Which leads to a rather large patch - larger than is desirable for stable IMHO.
Could we consider a more minimal fix for iwl-net.
And then follow-up with clean-ups for iwl?
...
next prev parent reply other threads:[~2024-11-02 15:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 20:45 [Intel-wired-lan] [PATCH v3 iwl-net 0/4] Fix E825 initialization Grzegorz Nitka
2024-10-28 20:45 ` Grzegorz Nitka
2024-10-28 20:45 ` [Intel-wired-lan] [PATCH v3 iwl-net 1/4] ice: " Grzegorz Nitka
2024-10-28 20:45 ` Grzegorz Nitka
2024-10-28 20:45 ` [Intel-wired-lan] [PATCH v3 iwl-net 2/4] ice: Fix quad registers read on E825 Grzegorz Nitka
2024-10-28 20:45 ` Grzegorz Nitka
2024-11-02 15:10 ` Simon Horman [this message]
2024-11-02 15:10 ` Simon Horman
2024-11-04 14:56 ` [Intel-wired-lan] " Nitka, Grzegorz
2024-11-04 14:56 ` Nitka, Grzegorz
2024-10-28 20:45 ` [Intel-wired-lan] [PATCH v3 iwl-net 3/4] ice: Fix ETH56G FC-FEC Rx offset value Grzegorz Nitka
2024-10-28 20:45 ` Grzegorz Nitka
2024-10-28 20:45 ` [Intel-wired-lan] [PATCH v3 iwl-net 4/4] ice: Add correct PHY lane assignment Grzegorz Nitka
2024-10-28 20:45 ` Grzegorz Nitka
2024-10-29 8:33 ` [Intel-wired-lan] [PATCH v3 iwl-net 0/4] Fix E825 initialization Przemek Kitszel
2024-10-29 8:33 ` Przemek Kitszel
2024-11-02 15:12 ` [Intel-wired-lan] " Simon Horman
2024-11-02 15:12 ` Simon Horman
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=20241102151033.GP1838431@kernel.org \
--to=horms@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=grzegorz.nitka@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=karol.kolacinski@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 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.