From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: Want to Get Suggestion for MX28 USB Submisson
Date: Mon, 9 Apr 2012 20:56:04 +0200 [thread overview]
Message-ID: <201204092056.04269.marek.vasut@gmail.com> (raw)
In-Reply-To: <4F830A4F.4040909@grid-net.com>
Dear Subodh Nijsure,
> On 04/06/2012 06:34 PM, Marek Vasut wrote:
> > Dear Marek Vasut,
> >
> >> Dear Chen Peter-B29397,
> >>
> >>>> On Wed, Mar 14, 2012 at 12:30 AM, Chen Peter-B29397
> >>>>
> >>>> <B29397@freescale.com> wrote:
> >>>>> According to sascha's suggestion, it is better to re-submit after we
> >>>>
> >>>> have
> >>>>
> >>>>> a generic USB PHY Layer in mainline.
> >>>>>
> >>>>> Currently, Heikki's split PHY from OTG structure patches have
> >>>>> mainlined, next step is to submit a generic USB PHY driver.
> >>>>
> >>>> Just for my understanding: is there someone working on this generic
> >>>> USB PHY driver?
> >>>
> >>> Add related people.
> >>>
> >>> I have much internal stuff on hands now, and have not bandwidth to do
> >>> it right now.
> >>
> >> It's in my queue to look into this too, but it's still low prio biz.
> >
> > Ok, it just became high-prio biz ...
> >
> > I have the code in prototype phase, will submit it once customer signs
> > the contract (likely next week).
>
> We have ported USB driver from Freescale's 2.6.35 implementation to
> 3.1-rc5 kernel. We are migrating from 3.1-rc5 to 3.4-rc1 so I am
> starting to look at this. Let me know if I can be of any help. I would
> be more than happy to test stuff you have.
Well, I already have this implemented via the generic phy framework, I don't
think FSL has this too. I'll be more than happy if you helped testing though ;-)
> -Subodh
Best regards,
Marek Vasut
prev parent reply other threads:[~2012-04-09 18:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 3:06 Want to Get Suggestion for MX28 USB Submisson Chen Peter-B29397
2011-11-28 4:57 ` Greg KH
2011-11-28 5:24 ` Chen Peter-B29397
2011-11-28 5:32 ` Greg KH
2011-11-30 3:04 ` Shawn Guo
2011-11-30 3:08 ` Chen Peter-B29397
2011-11-28 7:08 ` Robert Schwebel
2011-11-28 8:10 ` Chen Peter-B29397
2011-11-28 8:17 ` Robert Schwebel
2011-11-28 9:02 ` Chen Peter-B29397
2011-11-28 9:44 ` Marc Kleine-Budde
2011-11-28 12:11 ` Chen Peter-B29397
2012-02-03 21:21 ` Marek Vasut
2012-02-04 1:24 ` Chen Peter-B29397
2012-02-04 10:17 ` Marek Vasut
2012-02-10 3:31 ` Chen Peter-B29397
2012-02-10 3:47 ` Marek Vasut
2012-03-14 3:24 ` Fabio Estevam
2012-03-14 3:30 ` Chen Peter-B29397
2012-03-14 19:24 ` Sascha Hauer
2012-03-16 23:13 ` Fabio Estevam
2012-03-18 12:06 ` Chen Peter-B29397
2012-04-03 7:23 ` Marek Vasut
2012-04-07 1:34 ` Marek Vasut
2012-04-09 16:11 ` Subodh Nijsure
2012-04-09 18:56 ` Marek Vasut [this message]
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=201204092056.04269.marek.vasut@gmail.com \
--to=marek.vasut@gmail.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).