linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] omap: twl-common: Fix musb-hdrc device name.
Date: Mon, 9 Dec 2013 09:50:06 -0800	[thread overview]
Message-ID: <20131209175006.GD12527@atomide.com> (raw)
In-Reply-To: <CAAfyv37e9+OLH-KegPCEhc0sbBS7UVnaSGU0mBw2AxAN9D7Akw@mail.gmail.com>

* Belisko Marek <marek.belisko@gmail.com> [131208 23:36]:
> Hi Tony,
> 
> On Thu, Dec 5, 2013 at 7:43 PM, Tony Lindgren <tony@atomide.com> wrote:
> > * Belisko Marek <marek.belisko@gmail.com> [131203 01:21]:
> >> On Tue, Dec 3, 2013 at 10:08 AM, Belisko Marek <marek.belisko@gmail.com> wrote:
> >> > Hi,
> >> >
> >> > On Tue, Dec 3, 2013 at 9:58 AM, Kishon Vijay Abraham I <kishon@ti.com> wrote:
> >> >> Hi,
> >> >>
> >> >> On Tuesday 03 December 2013 02:03 PM, Marek Belisko wrote:
> >> >>> Without this change when booting omap3 device (gta04) with board file
> >> >>> leads to follwing errors:
> >> >>>
> >> >>> [    1.203308] musb-hdrc musb-hdrc.0.auto: unable to find phy
> >> >>> [    1.209075] HS USB OTG: no transceiver configured
> >> >>> [    1.214019] musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517
> >> >>>
> >> >>> and usb isn't working.
> >> >>>
> >> >>> This is probably regression caused by commit: 6c27f939
> >> >>
> >> >> I think a better fix would be to have this merged..
> >> >> https://lkml.org/lkml/2013/7/26/91
> >> > Yes I see but how this could help with current situation? Ho you then
> >> > specify device number?
> >> I was too fast with reply sorry. I can see whole series and it is of
> >> course correct solution. But as I said
> >> can we except to be merged to 3.13. If not Tony can you pick my patch.
> >
> > If it's a regression, then let's get it merged for the -rc cycle.
> Yes it is regression and without that usb on most omap3 based boards
> without DT will not work.
> >
> > So please try to follow up on getting the proper fix merged, meanwhile
> > I'll mark this thread as read. If you need this one merged for some
> > reason, then please report to get it back to my radar.

I'm still clueless which USB regression fix to apply for the -rc cycle
though.. Hoping to see a single patch which clearly states the issue
and has acks.

Regards,

Tony

  reply	other threads:[~2013-12-09 17:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03  8:33 [PATCH] omap: twl-common: Fix musb-hdrc device name Marek Belisko
2013-12-03  8:58 ` Kishon Vijay Abraham I
2013-12-03  9:08   ` Belisko Marek
2013-12-03  9:19     ` Kishon Vijay Abraham I
2013-12-03  9:20     ` Belisko Marek
2013-12-05 18:43       ` Tony Lindgren
2013-12-09  7:35         ` Belisko Marek
2013-12-09 17:50           ` Tony Lindgren [this message]
2013-12-13 11:27             ` Belisko Marek
2013-12-13 11:56               ` Kishon Vijay Abraham I
2013-12-13 17:36                 ` Tony Lindgren
2013-12-16  8:52                   ` Kishon Vijay Abraham I
2013-12-16 15:26                     ` Kishon Vijay Abraham I

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=20131209175006.GD12527@atomide.com \
    --to=tony@atomide.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).