| 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, 20 Mar 2012 17:40:02 -0600 (MDT) From: Paul Walmsley <paul@...an.com> To: Arnd Bergmann <arnd@...db.de> cc: "Turquette, Mike" <mturquette@...com>, linux-arm-kernel@...ts.infradead.org, Amit Kucheria <amit.kucheria@...aro.org>, Nicolas Pitre <nicolas.pitre@...aro.org>, linaro-dev@...ts.linaro.org, Linus Walleij <linus.walleij@...aro.org>, Grant Likely <grant.likely@...retlab.ca>, Saravana Kannan <skannan@...eaurora.org>, Jeremy Kerr <jeremy.kerr@...onical.com>, Magnus Damm <magnus.damm@...il.com>, Deepak Saxena <dsaxena@...aro.org>, patches@...aro.org, Sascha Hauer <s.hauer@...gutronix.de>, Rob Herring <rob.herring@...xeda.com>, Russell King <linux@....linux.org.uk>, Thomas Gleixner <tglx@...utronix.de>, Richard Zhao <richard.zhao@...aro.org>, Shawn Guo <shawn.guo@...escale.com>, Linus Walleij <linus.walleij@...ricsson.com>, Mark Brown <broonie@...nsource.wolfsonmicro.com>, Stephen Boyd <sboyd@...eaurora.org>, linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v7 1/3] Documentation: common clk API Hello Arnd, On Sat, 17 Mar 2012, Arnd Bergmann wrote: > I think it's rather pointless, because the option is not going to > be user selectable but will get selected by the platform unless I'm > mistaken. The platform maintainers that care already know the state > of the framework. This is where we have differing views, I think. Clearly, Sascha, Saravana, Rob, and I have at least slightly different opinions on the durability of the existing API and code. So it seems reasonable to assume that others who have not followed the development of the common clock code might mistake the implementation or API as being stable and well-defined. It sounds like the primary objection is to the use of CONFIG_EXPERIMENTAL. So here is a patch to simply note the status of this code in its Kconfig text. - Paul From: Paul Walmsley <paul@...an.com> Date: Tue, 20 Mar 2012 17:19:06 -0600 Subject: [PATCH] clk: note that the common clk code is still subject to significant change Indicate that the common clk code and API is still likely to require significant change. The API is not well-defined and both it and the underlying mechanics are likely to need significant changes to support non-trivial uses of the rate changing code, such as DVFS with external I/O devices. So any platforms that switch their implementation over to this may need to revise much of their driver code and revalidate their implementations until the behavior of the code is better-defined. A good time for removing this help text would be after at least two platforms that do DVFS on groups of external I/O devices have ported their clock implementations over to the common clk code. Signed-off-by: Paul Walmsley <paul@...an.com> Cc: Mike Turquette <mturquette@...com> --- drivers/clk/Kconfig | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig index 2eaf17e..dd2d528 100644 --- a/drivers/clk/Kconfig +++ b/drivers/clk/Kconfig @@ -21,6 +21,11 @@ menuconfig COMMON_CLK this option for loadable modules requiring the common clock framework. + The API and implementation enabled by this option is still + incomplete. The API and implementation is expected to be + fluid and subject to change at any time, potentially + breaking existing users. + If in doubt, say "N". if COMMON_CLK -- 1.7.9.1 -- 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