From: daniel@caiaq.de (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: USB support on i.MX27
Date: Tue, 1 Dec 2009 15:26:10 +0100 [thread overview]
Message-ID: <20091201142609.GP14091@buzzloop.caiaq.de> (raw)
In-Reply-To: <37367b3a0912010616r26ff385bqe6b85db1c510822f@mail.gmail.com>
On Tue, Dec 01, 2009 at 12:16:03PM -0200, Alan Carvalho de Assis wrote:
> On 11/30/09, Alan Carvalho de Assis <acassis@gmail.com> wrote:
> > I forgot to comment, I am configuring usbh2's portsc as on mx31lite:
> >
> > .portsc = MXC_EHCI_MODE_ULPI | MXC_EHCI_UTMI_8BIT,
> >
> > I defined and configured usbh2 pins:
> > /* USBH2 */
> > PA0_PF_USBH2_CLK,
> > PA1_PF_USBH2_DIR,
> > PA3_PF_USBH2_NXT,
> > PA4_PF_USBH2_STP,
> > PD22_AF_USBH2_DATA0,
> > PD24_AF_USBH2_DATA1,
> > PD23_AF_USBH2_DATA2,
> > PD20_AF_USBH2_DATA3,
> > PD19_AF_USBH2_DATA4,
> > PD26_AF_USBH2_DATA5,
> > PD21_AF_USBH2_DATA6,
> > PA2_PF_USBH2_DATA7,
> > PA24_AIN_SLDCD1_D0, /* EN_B */
> > PA26_PF_PS, /* RES_B */
> >
> > What you think could be this issue?
> >
>
> More some debug and everything worked fine:
Hmm, I don't follow. You added some debug output and it started working,
is that what you say? Do we possibly need memory barriers somewhere?
Can you post a patch with your changes, please?
Daniel
next prev parent reply other threads:[~2009-12-01 14:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 11:43 USB support on i.MX27 Alan Carvalho de Assis
2009-11-24 11:57 ` Daniel Mack
2009-11-24 12:31 ` Alan Carvalho de Assis
2009-11-24 13:07 ` Daniel Mack
2009-11-25 6:52 ` javier Martin
2009-11-27 10:16 ` Daniel Mack
2009-11-30 15:07 ` Alan Carvalho de Assis
2009-11-30 19:57 ` Alan Carvalho de Assis
2009-12-01 14:16 ` Alan Carvalho de Assis
2009-12-01 14:26 ` Daniel Mack [this message]
2009-12-01 14:51 ` Alan Carvalho de Assis
2009-12-02 8:43 ` Valentin Longchamp
2009-12-02 9:03 ` Eric Bénard
2009-12-02 16:09 ` Valentin Longchamp
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=20091201142609.GP14091@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).