From: festevam@gmail.com (Fabio Estevam)
To: linux-arm-kernel@lists.infradead.org
Subject: Enabling USBH1 on mx53qsb
Date: Thu, 25 Jul 2013 18:06:51 -0300 [thread overview]
Message-ID: <CAOMZO5CYnj1nNYMe4aONFCQ+a3pgtiAxSWWP+h5XvOjLO308Bg@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5CYNAKPFL1LgNGzwyZe9aCP9NHEXJFx+ymiqQf=QVx9YQ@mail.gmail.com>
On Thu, Jul 25, 2013 at 5:26 PM, Fabio Estevam <festevam@gmail.com> wrote:
> So we have a bug in the chipidea driver not writing to USBH1 PORTSC
> register even if I pass the "phy_type" via dt.
I fixed the issue and will submit the patches shortly.
prev parent reply other threads:[~2013-07-25 21:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 2:59 Enabling USBH1 on mx53qsb Fabio Estevam
2013-07-25 3:13 ` Peter Chen
2013-07-25 3:28 ` Fabio Estevam
2013-07-25 3:37 ` Peter Chen
2013-07-25 3:44 ` Fabio Estevam
2013-07-25 3:57 ` Marek Vasut
2013-07-25 14:03 ` Arnaud Patard (Rtp)
2013-07-25 20:26 ` Fabio Estevam
2013-07-25 21:06 ` Fabio Estevam [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=CAOMZO5CYnj1nNYMe4aONFCQ+a3pgtiAxSWWP+h5XvOjLO308Bg@mail.gmail.com \
--to=festevam@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).