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] [day] [month] [year] [list]
Message-ID: <20141223162357.GA4467@katana>
Date:	Tue, 23 Dec 2014 17:23:58 +0100
From:	Wolfram Sang <wsa@...-dreams.de>
To:	Ezequiel Garcia <ezequiel@...guardiasur.com.ar>
Cc:	Walter Lozano <walter@...guardiasur.com.ar>,
	mika.westerberg@...ux.intel.com, Romain.Baeriswyl@...lis.com,
	atull@...nsource.altera.com, raymond.tan@...el.com,
	carlpeng008@...il.com, linux-i2c@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] i2c: designware: Avoid initcall and initialize the driver
 like a regular one


> >> This means there won't be any early users of the I2C platform driver in this
> >> scenario.
> > 
> > There won't be with platform as well.
> 
> Oh, OK. Then maybe you can clarify why all those i2c busses need to be
> registered with initcall in the first place?

Because they want to access PMICs early to have voltages ready when
other drivers are probed. This, again, is DT/platform independent.
All this is cruft from the pre-deferred-probe era. And pretty annoying
to deprecated although I'd love to do that.


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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ