linux-kernel - Re: [PATCH] omap: twl-common: Fix musb-hdrc device name.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 5 Dec 2013 10:43:23 -0800
From:	Tony Lindgren <tony@...mide.com>
To:	Belisko Marek <marek.belisko@...il.com>
Cc:	Kishon Vijay Abraham I <kishon@...com>,
	Russell King - ARM Linux <linux@....linux.org.uk>,
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
	"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	"Dr. H. Nikolaus Schaller" <hns@...delico.com>
Subject: Re: [PATCH] omap: twl-common: Fix musb-hdrc device name.

* Belisko Marek <marek.belisko@...il.com> [131203 01:21]:
> On Tue, Dec 3, 2013 at 10:08 AM, Belisko Marek <marek.belisko@...il.com> wrote:
> > Hi,
> >
> > On Tue, Dec 3, 2013 at 9:58 AM, Kishon Vijay Abraham I <kishon@...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.

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.

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/