From: Simon Horman <horms@kernel.org>
To: Madhu Chittim <madhu.chittim@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org
Subject: Re: [Intel-wired-lan] [PATCH net-next v3] idpf: add support for IDPF PCI programming interface
Date: Mon, 1 Sep 2025 14:56:35 +0100 [thread overview]
Message-ID: <20250901135635.GD15473@horms.kernel.org> (raw)
In-Reply-To: <20250829172453.2059973-1-madhu.chittim@intel.com>
On Fri, Aug 29, 2025 at 10:24:53AM -0700, Madhu Chittim wrote:
> From: Pavan Kumar Linga <pavan.kumar.linga@intel.com>
>
> At present IDPF supports only 0x1452 and 0x145C as PF and VF device IDs
> on our current generation hardware. Future hardware exposes a new set of
> device IDs for each generation. To avoid adding a new device ID for each
> generation and to make the driver forward and backward compatible,
> make use of the IDPF PCI programming interface to load the driver.
>
> Write and read the VF_ARQBAL mailbox register to find if the current
> device is a PF or a VF.
>
> PCI SIG allocated a new programming interface for the IDPF compliant
> ethernet network controller devices. It can be found at:
> https://members.pcisig.com/wg/PCI-SIG/document/20113
> with the document titled as 'PCI Code and ID Assignment Revision 1.16'
> or any latest revisions.
>
> Reviewed-by: Sridhar Samudrala <sridhar.samudrala@intel.com>
> Signed-off-by: Pavan Kumar Linga <pavan.kumar.linga@intel.com>
> Signed-off-by: Madhu Chittim <madhu.chittim@intel.com>
>
> ---
> v3:
> - reworked logic to avoid gotos
Thanks,
I see that Paul has provided some review, which I don't disagree with.
But overall this looks good to me. Feel free to add.
Reviewed-by: Simon Horman <horms@kernel.org>
...
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@kernel.org>
To: Madhu Chittim <madhu.chittim@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3] idpf: add support for IDPF PCI programming interface
Date: Mon, 1 Sep 2025 14:56:35 +0100 [thread overview]
Message-ID: <20250901135635.GD15473@horms.kernel.org> (raw)
In-Reply-To: <20250829172453.2059973-1-madhu.chittim@intel.com>
On Fri, Aug 29, 2025 at 10:24:53AM -0700, Madhu Chittim wrote:
> From: Pavan Kumar Linga <pavan.kumar.linga@intel.com>
>
> At present IDPF supports only 0x1452 and 0x145C as PF and VF device IDs
> on our current generation hardware. Future hardware exposes a new set of
> device IDs for each generation. To avoid adding a new device ID for each
> generation and to make the driver forward and backward compatible,
> make use of the IDPF PCI programming interface to load the driver.
>
> Write and read the VF_ARQBAL mailbox register to find if the current
> device is a PF or a VF.
>
> PCI SIG allocated a new programming interface for the IDPF compliant
> ethernet network controller devices. It can be found at:
> https://members.pcisig.com/wg/PCI-SIG/document/20113
> with the document titled as 'PCI Code and ID Assignment Revision 1.16'
> or any latest revisions.
>
> Reviewed-by: Sridhar Samudrala <sridhar.samudrala@intel.com>
> Signed-off-by: Pavan Kumar Linga <pavan.kumar.linga@intel.com>
> Signed-off-by: Madhu Chittim <madhu.chittim@intel.com>
>
> ---
> v3:
> - reworked logic to avoid gotos
Thanks,
I see that Paul has provided some review, which I don't disagree with.
But overall this looks good to me. Feel free to add.
Reviewed-by: Simon Horman <horms@kernel.org>
...
next prev parent reply other threads:[~2025-09-01 13:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 17:24 [Intel-wired-lan] [PATCH net-next v3] idpf: add support for IDPF PCI programming interface Madhu Chittim
2025-08-29 17:24 ` Madhu Chittim
2025-08-29 22:07 ` [Intel-wired-lan] " Paul Menzel
2025-09-02 18:10 ` Linga, Pavan Kumar
2025-09-01 13:56 ` Simon Horman [this message]
2025-09-01 13:56 ` 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=20250901135635.GD15473@horms.kernel.org \
--to=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=madhu.chittim@intel.com \
--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.