linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: daniel@caiaq.de (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MX27: Add USB platform devices and resources
Date: Mon, 23 Nov 2009 18:58:47 +0100	[thread overview]
Message-ID: <20091123175847.GO14091@buzzloop.caiaq.de> (raw)
In-Reply-To: <37367b3a0911230825y55c443d3ga4e70c583a179ff6@mail.gmail.com>

On Mon, Nov 23, 2009 at 02:25:22PM -0200, Alan Carvalho de Assis wrote:
> On 11/23/09, Daniel Mack <daniel@caiaq.de> wrote:
> > On Mon, Nov 23, 2009 at 01:18:03PM -0200, Alan Carvalho de Assis wrote:
> >> > What do we need now to get USB working on i.MX27?
> >> >
> >>
> >> (replying myself)
> >> I think this Daniel Mack's patch will be necessary:
> >>
> >> http://lists.infradead.org/pipermail/linux-arm-kernel/2009-June/002972.html
> >
> > The patch you refer to only contains the relevant bits for MX31, you
> > would need to tweak it a little to make MX27 work as well. I think this
> > has been done already by someone, but I can't remember exactly.
> >
> 
> Thank you Daniel.
> 
> I will try to modify it myself. Case you remember someone who already
> do that, please let me know.

Should be easy to add. All you need to do is modify the parts which are
SoC specific, ie, not part of the EHCI spec. See mxc_set_usbcontrol()
and check if PORTSC needs some modifications (which I don't believe).

Please also note that there is an amendment patch queued that adds
support for MX35; if you file a patch for your platform, it should
cleanly apply on top of that one.

For the board specific code, have a look at
arch/arm/mach-mx3/mx31lilly.c in Sascha's mxc-master tree and take that
as an example.

> > The patch above and some others are already queued for 2.6.33. The ARM
> > specific things are in Sascha's mxc-master, the rest in the USB tree.
> >
> 
> Great! I think i.MX support on mainline kernel is getting better!

Help improve it :)

Daniel

  reply	other threads:[~2009-11-23 17:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <eedb5540907150626m3dbf815bif92ff179b6ebfe58@mail.gmail.com>
     [not found] ` <20090716081235.GQ2714@pengutronix.de>
     [not found]   ` <37367b3a0911230436i5d44cd80y182316ef056d6b31@mail.gmail.com>
2009-11-23 15:18     ` [PATCH] MX27: Add USB platform devices and resources Alan Carvalho de Assis
2009-11-23 15:31       ` Daniel Mack
2009-11-23 16:25         ` Alan Carvalho de Assis
2009-11-23 17:58           ` Daniel Mack [this message]
2009-11-23 18:28             ` Alan Carvalho de Assis
2009-11-23 20:28               ` Daniel Mack
2009-11-23 17:37         ` Alan Carvalho de Assis
2009-11-23 17:40           ` Alan Carvalho de Assis

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=20091123175847.GO14091@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --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).