linux-kernel - Re: RFC: Platform data for onboard USB assets

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: <20110323151008.GD25754@opensource.wolfsonmicro.com>
Date:	Wed, 23 Mar 2011 15:10:08 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Greg KH <greg@...ah.com>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Nicolas Pitre <nicolas.pitre@...aro.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	andy.green@...aro.org,
	Jaswinder Singh <jaswinder.singh@...aro.org>,
	Linux USB list <linux-usb@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>, arnd@...db.de,
	roger.quadros@...ia.com, grant.likely@...retlab.ca
Subject: Re: RFC: Platform data for onboard USB assets

On Wed, Mar 23, 2011 at 08:04:13AM -0700, Greg KH wrote:

> I asked for concrete examples of a need for this type of thing (i.e.
> platform data on USB devices), and this was the only need cited.  I

No, it isn't.  I previously mentioned the example of a system where the
ethernet controller was wired to several PHYs none of which were
connected to the data lines.  The driver needed to be told to use
special PHY detection logic to work on this system.  In general anything
which may be configured via the SEPROM may need overriding from software
on a system without the SEPROM - consulting the datasheet for a USB
ethernet controller should give an idea of the things that might need to
be configured.
--
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/