From: Logan Gunthorpe <logang@deltatee.com>
To: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
dmaengine@vger.kernel.org, Vinod Koul <vkoul@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: Frank Li <Frank.li@nxp.com>,
Kelvin Cao <kelvin.cao@microchip.com>,
Logan Gunthorpe <logang@deltatee.com>
Subject: [PATCH v1 0/3] switchtec: add new device IDs
Date: Tue, 14 Jul 2026 15:20:07 -0600 [thread overview]
Message-ID: <20260714212010.230606-1-logang@deltatee.com> (raw)
This little patch set adds some new device IDs for switchtec hardware
to the PCI driver, the DMA driver and the PCI quirk needed for NTB.
I originally included this in a patchset I'm working on for
switchtec-dma but the Sashiko bot reminded me I need to add it to the
PCI management device and the quirk used for NTB. So I've respun three
patches here.
I'm open to options, but I might suggest if everyone is okay with it
these three patches could just go through the PCI tree together.
These three patches are based on v7.2-rc3.
Thanks,
Logan
Logan Gunthorpe (3):
dmaengine: switchtec-dma: Add PCI1008 device ID
PCI/switch: switchtec: Add PCI1008 device ID
PCI: Add PCI1008 to switchtec NTB DMA alias quirk
drivers/dma/switchtec_dma.c | 1 +
drivers/pci/quirks.c | 1 +
drivers/pci/switch/switchtec.c | 1 +
3 files changed, 3 insertions(+)
base-commit: a13c140cc289c0b7b3770bce5b3ad42ab35074aa
--
2.47.3
next reply other threads:[~2026-07-14 21:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 21:20 Logan Gunthorpe [this message]
2026-07-14 21:20 ` [PATCH v1 1/3] dmaengine: switchtec-dma: Add PCI1008 device ID Logan Gunthorpe
2026-07-14 21:28 ` sashiko-bot
2026-07-14 21:42 ` Logan Gunthorpe
2026-07-14 21:20 ` [PATCH v1 2/3] PCI/switch: switchtec: " Logan Gunthorpe
2026-07-14 21:23 ` sashiko-bot
2026-07-14 21:20 ` [PATCH v1 3/3] PCI: Add PCI1008 to switchtec NTB DMA alias quirk Logan Gunthorpe
2026-07-14 21:38 ` sashiko-bot
2026-07-14 21:44 ` Logan Gunthorpe
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=20260714212010.230606-1-logang@deltatee.com \
--to=logang@deltatee.com \
--cc=Frank.li@nxp.com \
--cc=bhelgaas@google.com \
--cc=dmaengine@vger.kernel.org \
--cc=kelvin.cao@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=vkoul@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.