From: Matthieu CASTET <matthieu.castet@parrot.com>
To: Pavan Kondeti <pkondeti@codeaurora.org>
Cc: "greg@kroah.com" <greg@kroah.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
Mike Lockwood <lockwood@android.com>,
Brian Swetland <swetland@google.com>
Subject: Re: [PATCH v2] USB: Add MSM USB Device Controller driver
Date: Tue, 9 Nov 2010 14:36:57 +0100 [thread overview]
Message-ID: <4CD94E79.1050104@parrot.com> (raw)
In-Reply-To: <20101109121607.GA30807@codeaurora.org>
Hi Pavan,
Pavan Kondeti a écrit :
> On Tue, Nov 09, 2010 at 12:40:17PM +0100, Matthieu CASTET wrote:
>
> Hi Matthieu,
>
>>>
>> This look like the arc/chipidea/mips ehci otg core.
>
> Yes. It is chipidea core for ARM.
>> Why can't you reuse the ci13xxx_udc.c driver ?
>> Or if ci13xxx_udc.c is too bad, rewrite a new generic version for this core.
>>
> ci13xxx_udc.c driver registers with PCI subsytem (ours is a platform subsystem),
> does not manage clocks. msm72k_udc.c also takes care of initializing the
> integrated PHY. We also need to program special registers (MSM-ARM specific)
> upon resetting the hardware.
Yes, but why not adding this to ci13xxx_udc.c instead of doing a new driver.
For example adding platform subsystem is less than 150 lines of code.
I am not sure doing n drivers for a same hardware is a good idea.
May be ci13xxx_udc.c isn't enough generic, but in this case don't do the
same mistake with the new driver.
Make a generic core, and make the ulpi stuff (or other specific stuff)
in a glue around this code.
Look at host ehci : you don't need to rewrite ehci core. You only add a
glue around it.
Matthieu
next prev parent reply other threads:[~2010-11-09 13:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 11:18 [PATCH v2] Add MSM USB Device Controller support Pavankumar Kondeti
2010-11-09 11:18 ` [PATCH v2] USB: Add MSM USB Device Controller driver Pavankumar Kondeti
2010-11-09 11:40 ` Matthieu CASTET
2010-11-09 12:16 ` Pavan Kondeti
2010-11-09 13:36 ` Matthieu CASTET [this message]
2010-11-10 2:12 ` Pavan Kondeti
2010-11-10 2:54 ` David Brownell
2010-11-10 6:22 ` Brian Swetland
2010-11-19 17:16 ` Matthieu CASTET
2010-11-27 14:00 ` Pavan Kondeti
2010-11-28 6:30 ` David Brownell
2010-11-28 12:09 ` Pavan Kondeti
2010-12-07 12:44 ` Pavan Kondeti
2010-11-09 13:25 ` Heikki Krogerus
2010-11-09 13:52 ` Matthieu CASTET
2010-11-09 15:36 ` Igor Grinberg
2010-11-10 2:19 ` Pavan Kondeti
2010-11-10 6:47 ` Igor Grinberg
2010-11-11 2:10 ` Pavan Kondeti
2010-11-19 5:50 ` Pavan Kondeti
2010-11-21 8:09 ` Igor Grinberg
2010-11-10 2:17 ` Pavan Kondeti
2010-11-09 11:18 ` [PATCH v2] USB: msm72k_udc: Add debugfs support Pavankumar Kondeti
2010-11-09 11:18 ` [PATCH v2] USB: msm72k_udc: Add Remote wakeup support Pavankumar Kondeti
2010-11-09 11:18 ` [PATCH v2] USB: msm72k_udc: Add Test Mode support Pavankumar Kondeti
2010-11-09 11:18 ` [PATCH] USB: msm72k_udc: Add charging notification support Pavankumar Kondeti
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=4CD94E79.1050104@parrot.com \
--to=matthieu.castet@parrot.com \
--cc=greg@kroah.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lockwood@android.com \
--cc=pkondeti@codeaurora.org \
--cc=swetland@google.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).