| 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
| ||
|
Date: Tue, 05 May 2015 08:17:34 +0100 From: Srinivas Kandagatla <srinivas.kandagatla@...aro.org> To: Patrick Lai <plai@...eaurora.org>, Mark Brown <broonie@...nel.org>, Rob Herring <robh+dt@...nel.org>, Pawel Moll <pawel.moll@....com>, Ian Campbell <ijc+devicetree@...lion.org.uk>, Kumar Gala <galak@...eaurora.org>, Banajit Goswami <bgoswami@...eaurora.org>, Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.de>, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, alsa-devel@...a-project.org, linux-arm-msm@...r.kernel.org Subject: Re: [RFC PATCH 07/14] ASoC: qcom: add no osr clk flag to lpass variant On 03/05/15 00:58, Kenneth Westfield wrote: > On Thu, Apr 30, 2015 at 06:17:24PM +0100, Srinivas Kandagatla wrote: >> Some LPASS integrations like on APQ8016 do not have OSR clk, so adding >> no osr clk bit would allow such integrations to use lpass driver. > > Going forward, as the code is generalized, perhaps having an enable flag > for each clock, rather than a flag that negates an existing clock? > Or checking that the clock pointer is NULL after probing would be the > indication? Mark also suggested the same thing, I will fix it in next version. --srini -- 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