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, 18 Jul 2013 18:13:35 +0200
From:	Martin Nordholts <enselic@...il.com>
To:	Benson Leung <bleung@...omium.org>
Cc:	matthew.garrett@...ula.com, linux-kernel@...r.kernel.org,
	platform-driver-x86@...r.kernel.org, adurbin@...omium.org,
	olofj@...omium.org, axel.lin@...ics.com
Subject: Re: [PATCH 0/2] Platform: x86: chromeos_laptop - Deferred Probing

2013/7/18 Benson Leung <bleung@...omium.org>
>
> The following patch series refactors the dmi check system and
> returns -EPROBE_DEFER when an expected i2c adapter is not present
> at probe time.
>
> This will allow the touchpad, touchscreen, and light sensors on
> Pixel to load even if the i915 DDC and PANEL buses are instantiated
> after chromeos_laptop.
>
> [PATCH 1/2] Platform: x86: chromeos_laptop - Restructure device associations
> [PATCH 2/2] Platform: x86: chromeos_laptop - Use deferred probing


Hi,

I have worked on the same problem for the last days and just submitted
my solution proposal for review:
http://www.mail-archive.com/platform-driver-x86@vger.kernel.org/msg04440.html

One downside with the solution in this set of patches is that more
lines are added to the driver.
By making use of the i2c_driver.detect() mechanism like in my patch,
we can actually reduce the number of lines in the driver.

Looking forward to your comments on my other solution proposal!

/ Martin
--
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