linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: snijsure@grid-net.com (Subodh Nijsure)
To: linux-arm-kernel@lists.infradead.org
Subject: i.MX USB Re-Structure
Date: Thu, 10 May 2012 09:08:33 -0700	[thread overview]
Message-ID: <4FABE801.7070701@grid-net.com> (raw)
In-Reply-To: <201205101512.27073.marex@denx.de>

On 05/10/2012 06:12 AM, Marek Vasut wrote:
> Dear Sascha Hauer,
>
>> On Thu, May 10, 2012 at 02:05:24PM +0800, Peter Chen wrote:
>>> Hi Sascha,
>>>
>>> Recently, Alexander Shishkin has posted new chipidea patchset
>>> (http://www.spinics.net/lists/linux-usb/msg62975.html)
>>> to support USB driver who use chipidea core. In his structure,
>>> all controller related files (like ehci-mxc.c, fsl-udc-core.c, etc)
>>> will be drivers/usb/chipidea, and no related file will be host, gadget
>>> and otg again.
>>>
>>> So, it will be different with marek has posted i.mx28 USB driver,
>>> and also different with your proposal in the past. But I think
>>> you and marek may prefer Alexander's structure, and would like
>>> use it for i.mx in future, correct?
>> I was not aware of this patchset. I only had a short look at it, but
>> yes, it seems to be the way to go, for all SoCs supporting this
>> hardware, be it i.MX, MXS or something else.
> Correct, I can't but agree here.
http://www.spinics.net/lists/linux-usb/msg63064.html

In followup message referenced above Felipe Balbi said he can't put 
above patch in v3.5 pull and has to be deferred till 3.6.

So are we left with roll your own i.MX USB support for 3.5? Is Marek's 
work going to be part of 3.5 pull?

-Subodh

  reply	other threads:[~2012-05-10 16:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10  6:05 i.MX USB Re-Structure Peter Chen
2012-05-10 10:28 ` Marek Vasut
2012-05-11  1:20   ` Chen Peter-B29397
2012-05-11  2:13     ` Marek Vasut
2012-05-10 12:58 ` Sascha Hauer
2012-05-10 13:12   ` Marek Vasut
2012-05-10 16:08     ` Subodh Nijsure [this message]
2012-05-10 17:32       ` Marek Vasut

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=4FABE801.7070701@grid-net.com \
    --to=snijsure@grid-net.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).