From: Joe Perches <joe@perches.com>
To: Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
Vinod Koul <vinod.koul@intel.com>,
linux-kernel@vger.kernel.org, qi.wang@intel.com,
yong.y.wang@intel.com, joel.clark@intel.com,
kok.howg.ewe@intel.com, toshiharu-linux@dsn.okisemi.com
Subject: Re: [PATCH V2 5/5] pch_dma: Support new device ML7223 IOH
Date: Sun, 08 May 2011 21:05:41 -0700 [thread overview]
Message-ID: <1304913941.19586.8.camel@Joe-Laptop> (raw)
In-Reply-To: <1304912885-6747-1-git-send-email-tomoya-linux@dsn.okisemi.com>
On Mon, 2011-05-09 at 12:48 +0900, Tomoya MORINAGA wrote:
> Support new device OKI SEMICONDUCTOR ML7223 IOH(Input/Output Hub).
> The ML7223 IOH is for MP(Media Phone) use.
> The ML7223 is companion chip for Intel Atom E6xx series.
> The ML7223 is completely compatible for Intel EG20T PCH.
> Signed-off-by: Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>
> ---
> config PCH_DMA
> - tristate "Intel EG20T PCH / OKI SEMICONDUCTOR ML7213 IOH DMA support"
> + tristate "Intel EG20T PCH / OKI SEMICONDUCTOR IOH(ML7213/ML7223)"
DMA support?
> diff --git a/drivers/dma/pch_dma.c b/drivers/dma/pch_dma.c
> index 2c052bb..466954d 100644
> --- a/drivers/dma/pch_dma.c
> +++ b/drivers/dma/pch_dma.c
> @@ -956,6 +956,10 @@ static void __devexit pch_dma_remove(struct pci_dev *pdev)
> #define PCI_DEVICE_ID_ML7213_DMA2_8CH 0x802B
> #define PCI_DEVICE_ID_ML7213_DMA3_4CH 0x8034
> #define PCI_DEVICE_ID_ML7213_DMA4_12CH 0x8032
> +#define PCI_DEVICE_ID_ML7223_DMA1_4CH 0x800B
> +#define PCI_DEVICE_ID_ML7223_DMA2_4CH 0x800E
> +#define PCI_DEVICE_ID_ML7223_DMA3_4CH 0x8017
> +#define PCI_DEVICE_ID_ML7223_DMA4_4CH 0x803B
>
> static const struct pci_device_id pch_dma_id_table[] = {
DEFINE_PCI_DEVICE_TABLE(pch_dma_id_table) = {
next prev parent reply other threads:[~2011-05-09 4:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 3:48 [PATCH V2 5/5] pch_dma: Support new device ML7223 IOH Tomoya MORINAGA
2011-05-09 4:05 ` Joe Perches [this message]
2011-05-09 5:33 ` Tomoya MORINAGA
2011-05-09 6:01 ` Joe Perches
2011-05-09 6:41 ` Tomoya MORINAGA
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=1304913941.19586.8.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=dan.j.williams@intel.com \
--cc=joel.clark@intel.com \
--cc=kok.howg.ewe@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qi.wang@intel.com \
--cc=tomoya-linux@dsn.okisemi.com \
--cc=toshiharu-linux@dsn.okisemi.com \
--cc=vinod.koul@intel.com \
--cc=yong.y.wang@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