linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnaud.patard@rtp-net.org (Arnaud Patard (Rtp))
To: linux-arm-kernel@lists.infradead.org
Subject: [patch 1/1] imx53-qsb: enable usb power
Date: Tue, 25 Jun 2013 19:08:53 +0200	[thread overview]
Message-ID: <878v1y9kyi.fsf@lebrac.rtp-net.org> (raw)
In-Reply-To: <CAOMZO5DR6ChNwX8Kqb9mO66-M4xi1G3R8nQ=ENUwrp9k9S8vDg@mail.gmail.com> (Fabio Estevam's message of "Mon, 24 Jun 2013 22:40:04 -0300")

Fabio Estevam <festevam@gmail.com> writes:

> On Mon, Jun 24, 2013 at 8:52 PM, Fabio Estevam <festevam@gmail.com> wrote:
>> On Thu, Jun 20, 2013 at 6:29 PM, Arnaud Patard
>> <arnaud.patard@rtp-net.org> wrote:
>>> Enable usb power pin by using a fixed regulator. With this and the usb clock
>>> patch is making usb working on my loco.
>>>
>>> Signed-off-by: Arnaud Patard <arnaud.patard@rtp-net.org>
>>
>> Could you please test this against linux-next?
>>
>> It does not work for me:
>>
>> usbcore: registered new interface driver usb-storage
>> platform 53f80000.usb: Driver imx_usb requests probe deferral
>> platform 53f80200.usb: Driver imx_usb requests probe deferral
>
> Ok, got it working now, but had to do two changes:
>
> - Add a vbus-supply node for usbh1 as suggested by Sascha

How do you want to proceed ? send a patch on top of mine or send a new
patch containing my patch and this change ? ( I guess that the later
would be easier)

btw, now that it seems that some more stuff has been merged in chipidea
are in next, what about enabling the second port ?

Arnaud

  reply	other threads:[~2013-06-25 17:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20 21:29 [patch 1/1] imx53-qsb: enable usb power Arnaud Patard (Rtp)
2013-06-23 18:59 ` Sascha Hauer
2013-06-24  7:29   ` Arnaud Patard (Rtp)
2013-06-24 23:52 ` Fabio Estevam
2013-06-25  1:40   ` Fabio Estevam
2013-06-25 17:08     ` Arnaud Patard (Rtp) [this message]
2013-06-25 17:12       ` Fabio Estevam
2013-07-25 12:42 ` Fabio Estevam

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=878v1y9kyi.fsf@lebrac.rtp-net.org \
    --to=arnaud.patard@rtp-net.org \
    --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).