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: <AANLkTimwUUBNtQ7qG5NXCOs+fODZHypNesA9mooseW9+@mail.gmail.com>
Date:	Fri, 11 Mar 2011 16:39:39 -0700
From:	Grant Likely <grant.likely@...retlab.ca>
To:	andy.green@...aro.org
Cc:	Andy Green <andy@...mcat.com>,
	Linux USB list <linux-usb@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Arnd Bergmann <arnd@...db.de>,
	Greg Kroah-Hartman <gregkh@...e.de>
Subject: Re: RFC: Platform data for onboard USB assets

On Fri, Mar 11, 2011 at 3:47 PM, Andy Green <andy@...mcat.com> wrote:
> On 03/11/2011 10:45 PM, Somebody in the thread at some point said:
>>
>> On Fri, Mar 11, 2011 at 2:50 AM, Andy Green<andy@...mcat.com>  wrote:
>>>
>>> Hi -
>>>
>>> platform_data is a well established way in Linux to pass configuration
>>> data
>>> up to on-board assets from a machine file like mach-xyz.c.  It's also
>>> supported to pass platform_data up to devices that are probed
>>> asynchronously
>>> from busses like i2c as well, which is very handy.
>>>
>>> However AFAIK it's not possible to bind platform_data to probed USB
>>> devices
>>> as it stands.
>>
>> Oh, please no.
>>
>> platform_data is an ugly non-type-checked anonymous pointer.  If you
>> need to pass data to a driver, use something better designed.  A
>> device tree fragment would work, or provide some kind of query api.
>> platform_data is definitely the wrong approach.
>
> $ grep platform_data drivers/* -R | wc -l
> 2110

I'm not disputing that it is widely used; and it does make a certain
amount of sense for static device registrations, but it is not a nice
interface, and it is a horrible idea for dynamic devices.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ