linux-kernel - Re: [PATCH] usb: misc: usb3503: Force late initialization

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]

Message-ID: <20130814190410.GO2401@sirena.org.uk>
Date:	Wed, 14 Aug 2013 20:04:10 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	Tushar Behera <tushar.behera@...aro.org>,
	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
	tobetter@...il.com, patches@...aro.org
Subject: Re: [PATCH] usb: misc: usb3503: Force late initialization

On Wed, Aug 14, 2013 at 11:22:39AM -0700, Greg KH wrote:
> On Wed, Aug 14, 2013 at 03:59:31PM +0530, Tushar Behera wrote:

> > Currently there is no other way to ensure that USB3503 chip is probed
> > after the USB PHY has been initialized, hence the last resort.

> Are you sure that deferred probing doesn't solve this issue?

In order for deferred probing to help the device would need to acquire
some resource from the parent USB controller once active, allowing it to
defer when it fails to get that resource.  Currently there's nothing
there for that and it's not clear that's sane and sensible (it'd be more
obvious for it to be a child of the USB controller since that's what it
really is).  

We can't just treat it as a PHY (which is the obvious workaroud) since
we do also need to use the built
in PHY in the SoC.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)