From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Dirk Brandewie <dirk.brandewie@gmail.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
David Brownell <dbrownell@users.sourceforge.net>
Subject: Re: [PATCH 6/6] ce4100: Add support for CE4100 EHCI IP block to EHCI driver
Date: Wed, 10 Nov 2010 13:51:17 +0300 [thread overview]
Message-ID: <4CDA7925.10707@ru.mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1011092134180.14099-100000@netrider.rowland.org>
Hello.
On 10-11-2010 5:36, Alan Stern wrote:
>> In a previous patch in this series GregKH asked that the PCI ID not be added
>> to pci_ids.h for ID's that are only used by a single file.
>> Here is an updated version of the EHCI controller patch.
>> Subject: [PATCH] ce4100: Add support for CE4100 EHCI IP block to EHCI driver
>> This patch adds support for the EHCI IP block present on the Intel
>> CE4100.
>> Signed-off-by: Dirk Brandewie<dirk.brandewie@gmail.com>
>> CC: linux-usb@vger.kernel.org
>> CC: David Brownell<dbrownell@users.sourceforge.net>
>> ---
>> drivers/usb/host/ehci-pci.c | 4 ++++
>> 1 files changed, 4 insertions(+), 0 deletions(-)
>> diff --git a/drivers/usb/host/ehci-pci.c b/drivers/usb/host/ehci-pci.c
>> index a1e8d27..da2b196 100644
>> --- a/drivers/usb/host/ehci-pci.c
>> +++ b/drivers/usb/host/ehci-pci.c
>> @@ -124,6 +124,10 @@ static int ehci_pci_setup(struct usb_hcd *hcd)
>> ehci_info(ehci, "disable lpm for langwell/penwell\n");
>> ehci->has_lpm = 0;
>> }
>> + if (pdev->device == 0x2e70) {
>> + hcd->has_tt = 1;
>> + tdi_reset(ehci);
>> + }
> I think Greg meant that it's okay to use a symbolic constant for the
> PCI ID (it helps tell people what hardware is being handled). Just
> don't add that constant to the pci_ids.h file.
Or at least you need a comment naming the hardware that this ID belongs to.
> Alan Stern
WBR, Sergei
next prev parent reply other threads:[~2010-11-10 10:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 20:08 [PATCH 0/6] Add support for the Intel CE4100 dirk.brandewie
2010-11-09 20:08 ` [PATCH 1/6] x86: Add CE4100 platform support dirk.brandewie
2010-11-09 20:08 ` [PATCH 2/6] ce4100: add PCI register emulation for CE4100 dirk.brandewie
2010-11-11 11:51 ` Thomas Gleixner
2010-11-09 20:08 ` [PATCH 3/6] serial/ce4100: Add PCI UART support for the ce4100 dirk.brandewie
2010-11-09 21:14 ` Greg KH
2010-11-09 21:54 ` Dirk Brandewie
2010-11-17 15:35 ` [PATCH] " dirk.brandewie
2010-11-09 20:08 ` [PATCH 4/6] ce4100: Add errata fixes for UART on CE4100 dirk.brandewie
2010-11-11 11:34 ` Thomas Gleixner
2010-11-11 11:52 ` Dirk Brandewie
2010-11-11 11:47 ` Thomas Gleixner
2010-11-11 12:10 ` Dirk Brandewie
2010-11-11 12:06 ` Thomas Gleixner
2010-11-22 14:28 ` [PATCH] " dirk.brandewie
2010-12-06 15:00 ` [tip:x86/platform] " tip-bot for Dirk Brandewie
2010-11-09 20:08 ` [PATCH 5/6] x86: ce4100: Add reboot_fixup() for CE4100 dirk.brandewie
2010-11-09 20:08 ` [PATCH 6/6] ce4100: Add support for CE4100 EHCI IP block to EHCI driver dirk.brandewie
2010-11-09 22:01 ` Dirk Brandewie
2010-11-10 2:36 ` Alan Stern
2010-11-10 10:51 ` Sergei Shtylyov [this message]
2010-11-16 21:46 ` Greg KH
2010-11-16 23:24 ` Dirk Brandewie
2010-11-17 15:43 ` [PATCH] " dirk.brandewie
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=4CDA7925.10707@ru.mvista.com \
--to=sshtylyov@mvista.com \
--cc=dbrownell@users.sourceforge.net \
--cc=dirk.brandewie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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