From: Logan Gunthorpe <logang@deltatee.com>
To: Rakesh Babu Saladi <Saladi.Rakeshbabu@microchip.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
bhelgaas@google.com, kurt.schwemmer@microsemi.com
Cc: unglinuxdriver@microchip.com
Subject: Re: [PATCH] PCI: switchtec: Include PCI100X devices support
Date: Mon, 20 Jan 2025 10:31:15 -0700 [thread overview]
Message-ID: <f0b8792e-06c0-43f1-863d-021d9feac2ca@deltatee.com> (raw)
In-Reply-To: <20250120095524.243103-1-Saladi.Rakeshbabu@microchip.com>
On 2025-01-20 02:55, Rakesh Babu Saladi wrote:
> Add the Microchip Parts to the existing device ID
> table so that the driver supports PCI100x devices too.
>
> Add a new macro to quirk the Microchip switchtec PCI100x parts
> to allow DMA access via NTB to work when the IOMMU is turned on.
>
> PCI100x family has 6 variants, each variant is designed for different
> application usages, different port counts and lane counts.
>
> PCI1001 has 1 x4 upstream port and 3 x4 downstream ports.
> PCI1002 has 1 x4 upstream port and 4 x2 downstream ports.
> PCI1003 has 2 x4 upstream ports, 2 x2 upstream ports and 2 x2
> downstream ports.
> PCI1004 has 4 x4 upstream ports.
> PCI1005 has 1 x4 upstream port and 6 x2 downstream ports.
> PCI1006 has 6 x2 upstream ports and 2 x2 downstream ports.
>
> Signed-off-by: Rakesh Babu Saladi <Saladi.Rakeshbabu@microchip.com>
Looks good to me, thanks!
Acked-By: Logan Gunthorpe <logang@deltatee.com>
Logan
next prev parent reply other threads:[~2025-01-20 18:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 9:55 [PATCH] PCI: switchtec: Include PCI100X devices support Rakesh Babu Saladi
2025-01-20 17:31 ` Logan Gunthorpe [this message]
2025-01-20 22:56 ` Bjorn Helgaas
2025-01-21 13:16 ` Saladi.Rakeshbabu
2025-01-21 14:48 ` Woojung.Huh
2025-01-21 16:47 ` Bjorn Helgaas
2025-01-21 17:22 ` Bjorn Helgaas
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=f0b8792e-06c0-43f1-863d-021d9feac2ca@deltatee.com \
--to=logang@deltatee.com \
--cc=Saladi.Rakeshbabu@microchip.com \
--cc=bhelgaas@google.com \
--cc=kurt.schwemmer@microsemi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=unglinuxdriver@microchip.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