Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
To: Grzegorz Nitka <grzegorz.nitka@intel.com>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v1 0/3] ice: add E825C device family support
Date: Thu, 7 Dec 2023 10:11:06 +0100	[thread overview]
Message-ID: <cff236f7-a484-418f-b6cb-7be14581033d@intel.com> (raw)
In-Reply-To: <20231206192919.3826128-1-grzegorz.nitka@intel.com>



On 12/6/2023 8:29 PM, Grzegorz Nitka wrote:
> This patch series is supposed to add very basic support in ice driver
> for new Intel Ethernet device family E825C.
> E825C device consists of 2 NAC (Network Acceleration Complex) instances
> in the IO die and supports max of 8 ports with combined bandwidth up to
> 200G.
> There are 2 configurations (known as NAC Topology):
> - single NAC (only one NAC is enabled) or
> - dual NAC (both NACs are enabled, with one designated as primary and
>    other as secondary).
> 
> This series covers:
> - definition of new PCI device IDs assigned to E825C devices
> - support for new 3k signed DDP segments
> 
> In the follow-up series support for new PHY and NAC topology parser
> will be added.
> 
> Grzegorz Nitka (3):
>    ice: introduce new E825C devices family
>    ice:  Add helper function ice_is_generic_mac
>    ice: add support for 3k signing DDP sections for E825C
> 
>   drivers/net/ethernet/intel/ice/ice_common.c   | 37 +++++++++++++++++++
>   drivers/net/ethernet/intel/ice/ice_common.h   |  2 +
>   drivers/net/ethernet/intel/ice/ice_controlq.c |  2 +-
>   drivers/net/ethernet/intel/ice/ice_ddp.c      |  4 ++
>   drivers/net/ethernet/intel/ice/ice_devids.h   |  8 ++++
>   drivers/net/ethernet/intel/ice/ice_main.c     | 10 ++++-
>   drivers/net/ethernet/intel/ice/ice_type.h     |  1 +
>   7 files changed, 61 insertions(+), 3 deletions(-)
> 
> 
> base-commit: 545c31d16cc00bba281ee1927d6338e27d4b7b5e

Thanks Grzegorz.

For series:
Reviewed-by: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

      parent reply	other threads:[~2023-12-07  9:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 19:29 [Intel-wired-lan] [PATCH iwl-next v1 0/3] ice: add E825C device family support Grzegorz Nitka
2023-12-06 19:29 ` [Intel-wired-lan] [PATCH iwl-next v1 1/3] ice: introduce new E825C devices family Grzegorz Nitka
2023-12-12 10:01   ` Simon Horman
2024-01-08  4:50   ` Pucha, HimasekharX Reddy
2023-12-06 19:29 ` [Intel-wired-lan] [PATCH iwl-next v1 2/3] ice: Add helper function ice_is_generic_mac Grzegorz Nitka
2023-12-12 10:01   ` Simon Horman
2024-01-08  4:53   ` Pucha, HimasekharX Reddy
2023-12-06 19:29 ` [Intel-wired-lan] [PATCH iwl-next v1 3/3] ice: add support for 3k signing DDP sections for E825C Grzegorz Nitka
2023-12-12 10:02   ` Simon Horman
2024-01-08  4:55   ` Pucha, HimasekharX Reddy
2023-12-07  9:11 ` Mateusz Polchlopek [this message]

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=cff236f7-a484-418f-b6cb-7be14581033d@intel.com \
    --to=mateusz.polchlopek@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox