From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] i.MX6Q USB host support for mainline Linux (was: Re: [PATCH v2 1/2] usb/ehci: Add USB support for the MX6Q)
Date: Sun, 12 Feb 2012 12:09:46 +0100 [thread overview]
Message-ID: <201202121209.47022.marek.vasut@gmail.com> (raw)
In-Reply-To: <4F378C48.4070205@googlemail.com>
> While discussing at the U-Boot mailing list about i.MX6Q USB host
> support for U-Boot, there was the question what's about the same for
> mainline Linux. See below.
>
> I'd like to continue this discussion with a new subject and adding the
> Linaro mailing list.
I'm not subscribed, this is gonna make it all a mess.
>
> On 12.02.2012 09:46, Marek Vasut wrote:
> >> On 11.02.2012 19:46, Fabio Estevam wrote:
> >>> On Sat, Feb 11, 2012 at 5:12 AM, Marek Vasut<marek.vasut@gmail.com>
wrote:
> >>>> btw Fabio, do we support mx6q USB host in mainline Linux ?
> >>>
> >>> Not yet, Marek.
> >>
> >> Linaro has it working with
> >>
> >> http://git.linaro.org/gitweb?p=bsp/freescale/linux-linaro.git;a=commit;h
> >> =de 941f9ac0b59c34053618e90e3c1f1d8b5a2d22
> >>
> >> http://git.linaro.org/gitweb?p=bsp/freescale/linux-linaro.git;a=commit;h
> >> =40 26cfa27332f2e53cfbf72cc98cf4db8c2f2127
> >>
> >> It shouldn't be that hard to apply these to plain mainline Linux (?).
> >
> > Do you believe this will be accepted into mainline Linux if basically the
> > same stuff, except for mx28 did NOT get accepted?
>
> Do you have any pointers to the discussion about this? Hopefully we
> could learn from that.
This is the name of the thread in LAKML:
"RE: Want to Get Suggestion for MX28 USB Submisson"
>
> > The shape of the code was almost
> > identical, maybe better. Actually, even the file names are the same here
> > and in the old FSL BSP for mx28.
>
> I think the good news is at least that Linaro is working on a more or
> less recent kernel (atm 3.2). So, as mentioned above, porting it from
> the Linaro kernel to the mainline kernel shouldn't be that hard.
It actually will be, since ... well see the discussion about MX28 USB, it's all
explained there. Sorry, I'm currently at the verge of falling asleep, very
tired.
> The
> next step would be to clean them up, hopefully learning from the mx28
> experience mentioned above.
There was something going on about handling the PHY separately from the USB EHCI
core, that's the part where it got stuck if I recall well.
>
> What do you think?
I think I'll have a good sleep now, I need it, I'm starting to babble nonsense.
>
> Best regards
>
> Dirk
M
next prev parent reply other threads:[~2012-02-12 11:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 8:33 [U-Boot] [PATCH v2 0/2] usb/mx6q: USB EHCI support for MX6Q boards Wolfgang Grandegger
2012-02-09 8:33 ` [U-Boot] [PATCH v2 1/2] usb/ehci: Add USB support for the MX6Q Wolfgang Grandegger
2012-02-11 7:12 ` Marek Vasut
2012-02-11 7:19 ` Marek Vasut
2012-02-11 18:46 ` Fabio Estevam
2012-02-12 8:01 ` Dirk Behme
2012-02-12 8:46 ` Marek Vasut
2012-02-12 8:52 ` Shilpa Budhihal
2012-02-12 8:57 ` Marek Vasut
[not found] ` <FA04B2A1CD90BB43B811F51230EC7FCC02C25AF4@INFHYDEX10MB3.corp.infotech-enterprises.com>
2012-02-12 9:18 ` Marek Vasut
2012-02-12 9:54 ` [U-Boot] i.MX6Q USB host support for mainline Linux (was: Re: [PATCH v2 1/2] usb/ehci: Add USB support for the MX6Q) Dirk Behme
2012-02-12 11:09 ` Marek Vasut [this message]
2012-02-12 10:16 ` [U-Boot] [PATCH v2 1/2] usb/ehci: Add USB support for the MX6Q Wolfgang Grandegger
2012-02-12 11:06 ` Marek Vasut
2012-02-20 16:05 ` Stefano Babic
2012-02-09 8:33 ` [U-Boot] [PATCH v2 2/2] mx6qsabrelite: add and enable USB Host 1 support Wolfgang Grandegger
2012-02-20 16:05 ` Stefano Babic
2012-02-10 7:57 ` [U-Boot] [PATCH v2 0/2] usb/mx6q: USB EHCI support for MX6Q boards Dirk Behme
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=201202121209.47022.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=u-boot@lists.denx.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