From: Manoj Iyer <manoj.iyer@canonical.com>
To: Chris Ball <cjb@laptop.org>
Cc: linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
philipl@overt.org, w.sang@pengutronix.de
Subject: Re: [PATCH] mmc: Enable MMC card reader for RICOH [1180:e823]
Date: Tue, 31 May 2011 10:01:00 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1105310958460.4067@sleepy> (raw)
In-Reply-To: <m3fwo0u9sf.fsf@pullcord.laptop.org>
On Thu, 26 May 2011, Chris Ball wrote:
> Hi Manoj,
>
> On Thu, May 26 2011, Manoj Iyer wrote:
>> Signed-off-by: Manoj Iyer <manoj.iyer@canonical.com>
>> ---
>> drivers/pci/quirks.c | 2 ++
>> include/linux/pci_ids.h | 1 +
>> 2 files changed, 3 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
>> index e8a1406..02145e9 100644
>> --- a/drivers/pci/quirks.c
>> +++ b/drivers/pci/quirks.c
>> @@ -2761,6 +2761,8 @@ static void ricoh_mmc_fixup_r5c832(struct pci_dev *dev)
>> }
>> DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_RICOH, PCI_DEVICE_ID_RICOH_R5C832, ricoh_mmc_fixup_r5c832);
>> DECLARE_PCI_FIXUP_RESUME_EARLY(PCI_VENDOR_ID_RICOH, PCI_DEVICE_ID_RICOH_R5C832, ricoh_mmc_fixup_r5c832);
>> +DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_RICOH, PCI_DEVICE_ID_RICOH_R5CE823, ricoh_mmc_fixup_r5c832);
>> +DECLARE_PCI_FIXUP_RESUME_EARLY(PCI_VENDOR_ID_RICOH, PCI_DEVICE_ID_RICOH_R5CE823, ricoh_mmc_fixup_r5c832);
>> #endif /*CONFIG_MMC_RICOH_MMC*/
>>
>> #if defined(CONFIG_DMAR) || defined(CONFIG_INTR_REMAP)
>> diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
>> index 24787b7..2269dac 100644
>> --- a/include/linux/pci_ids.h
>> +++ b/include/linux/pci_ids.h
>> @@ -1537,6 +1537,7 @@
>> #define PCI_DEVICE_ID_RICOH_RL5C476 0x0476
>> #define PCI_DEVICE_ID_RICOH_RL5C478 0x0478
>> #define PCI_DEVICE_ID_RICOH_R5C822 0x0822
>> +#define PCI_DEVICE_ID_RICOH_R5CE823 0xe823
>> #define PCI_DEVICE_ID_RICOH_R5C832 0x0832
>> #define PCI_DEVICE_ID_RICOH_R5C843 0x0843
>
> Do you not need a corresponding entry in drivers/mmc/host/sdhci-pci.c's
> pci_device_id struct?
>
I believe there is an entry there already, introduced by this patch:
https://lkml.org/lkml/2011/2/11/309
> Thanks,
>
> - Chris.
> --
> Chris Ball <cjb@laptop.org> <http://printf.net/>
> One Laptop Per Child
>
>
--
====================
Manoj Iyer
Ubuntu/Canonical
Hardware Enablement
====================
next prev parent reply other threads:[~2011-05-31 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 16:19 [PATCH 1/1 V2] " Manoj Iyer
2011-05-26 16:19 ` [PATCH] " Manoj Iyer
2011-05-27 3:01 ` Chris Ball
2011-05-31 15:01 ` Manoj Iyer [this message]
2011-05-31 15:05 ` Chris Ball
-- strict thread matches above, loose matches on Subject: below --
2011-05-26 14:11 Manoj Iyer
2011-05-26 14:11 ` Manoj Iyer
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=alpine.DEB.2.02.1105310958460.4067@sleepy \
--to=manoj.iyer@canonical.com \
--cc=cjb@laptop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=philipl@overt.org \
--cc=w.sang@pengutronix.de \
/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
all inboxes | Powered by JetHome®