From: Vinod Koul <vkoul@infradead.org>
To: Dave Jiang <dave.jiang@intel.com>
Cc: vinod.koul@intel.com, djbw@fb.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ioat: Adding Ivy Bridge IOATDMA PCI device IDs
Date: Fri, 31 Aug 2012 06:07:22 +0530 [thread overview]
Message-ID: <1346373442.15463.3.camel@vkoul-mobl4> (raw)
In-Reply-To: <20120824233619.9218.25014.stgit@djiang5-linux.ch.intel.com>
On Fri, 2012-08-24 at 16:36 -0700, Dave Jiang wrote:
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
Sounds okay to me, I can carry it once Dan acks it
> ---
>
> drivers/dma/ioat/pci.c | 22 ++++++++++++++++++++++
> 1 files changed, 22 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/dma/ioat/pci.c b/drivers/dma/ioat/pci.c
> index 5e3a40f..c057306 100644
> --- a/drivers/dma/ioat/pci.c
> +++ b/drivers/dma/ioat/pci.c
> @@ -40,6 +40,17 @@ MODULE_VERSION(IOAT_DMA_VERSION);
> MODULE_LICENSE("Dual BSD/GPL");
> MODULE_AUTHOR("Intel Corporation");
>
> +#define PCI_DEVICE_ID_INTEL_IOAT_IVB0 0x0e20
> +#define PCI_DEVICE_ID_INTEL_IOAT_IVB1 0x0e21
> +#define PCI_DEVICE_ID_INTEL_IOAT_IVB2 0x0e22
> +#define PCI_DEVICE_ID_INTEL_IOAT_IVB3 0x0e23
> +#define PCI_DEVICE_ID_INTEL_IOAT_IVB4 0x0e24
> +#define PCI_DEVICE_ID_INTEL_IOAT_IVB5 0x0e25
> +#define PCI_DEVICE_ID_INTEL_IOAT_IVB6 0x0e26
> +#define PCI_DEVICE_ID_INTEL_IOAT_IVB7 0x0e27
> +#define PCI_DEVICE_ID_INTEL_IOAT_IVB8 0x0e2e
> +#define PCI_DEVICE_ID_INTEL_IOAT_IVB9 0x0e2f
> +
> static struct pci_device_id ioat_pci_tbl[] = {
> /* I/OAT v1 platforms */
> { PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_IOAT) },
> @@ -83,6 +94,17 @@ static struct pci_device_id ioat_pci_tbl[] = {
> { PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_IOAT_SNB8) },
> { PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_IOAT_SNB9) },
>
> + { PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_IOAT_IVB0) },
> + { PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_IOAT_IVB1) },
> + { PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_IOAT_IVB2) },
> + { PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_IOAT_IVB3) },
> + { PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_IOAT_IVB4) },
> + { PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_IOAT_IVB5) },
> + { PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_IOAT_IVB6) },
> + { PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_IOAT_IVB7) },
> + { PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_IOAT_IVB8) },
> + { PCI_VDEVICE(INTEL, PCI_DEVICE_ID_INTEL_IOAT_IVB9) },
> +
> { 0, }
> };
> MODULE_DEVICE_TABLE(pci, ioat_pci_tbl);
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
~Vinod Koul
Intel Corp.
next prev parent reply other threads:[~2012-08-31 0:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 23:36 [PATCH] ioat: Adding Ivy Bridge IOATDMA PCI device IDs Dave Jiang
2012-08-31 0:37 ` Vinod Koul [this message]
2012-08-31 15:28 ` Dan Williams
2012-08-31 15:50 ` Vinod Koul
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=1346373442.15463.3.camel@vkoul-mobl4 \
--to=vkoul@infradead.org \
--cc=dave.jiang@intel.com \
--cc=djbw@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vinod.koul@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).