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
| ||
|
Message-ID: <20151021072817.GM1526@lahna.fi.intel.com> Date: Wed, 21 Oct 2015 10:28:17 +0300 From: Mika Westerberg <mika.westerberg@...ux.intel.com> To: Ken Xue <Ken.Xue@....com> Cc: baruch@...s.co.il, SPG_Linux_Kernel@....com, linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org, stable@...r.kernel.org Subject: Re: [PATCH 1/2] i2c: designware: register clkdev during acpi device configuration On Wed, Oct 21, 2015 at 09:11:33AM +0800, Ken Xue wrote: > On Tue, 2015-10-20 at 14:17 +0300, Mika Westerberg wrote: > > On Tue, Oct 20, 2015 at 02:38:01PM +0800, Ken Xue wrote: > > > DW I2C driver tries to register a clk from id->driver_data as an > > > alternative way besides intel lpss. But code doesn't register the > > > clk to clkdev. So, devm_clk_get will fail during probe. > > > > > > The patch can fix this issue. > > > > Since you now have drivers/acpi/acpi_apd.c for AMD ACPI stuff, can you > > create the clock there just like we do for Intel stuff? > Sure. APD already creates the clock for AMD0010 as you expected. And the > next patch([PATCH 2/2] i2c: designware: remove freq definition for > "AMD0010" in acpi_device_id) is dropping the old way for getting freq. So this patch is not necessary, right? -- 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