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, 28 Jun 2016 14:18:40 -0700 From: Michael Turquette <mturquette@...libre.com> To: Rob Herring <robh@...nel.org>, "Jongsung Kim" <neidhard.kim@....com> Cc: "Maxime Ripard" <maxime.ripard@...e-electrons.com>, "Stephen Boyd" <sboyd@...eaurora.org>, linux-clk@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, "Chanho Min" <chanho.min@....com> Subject: Re: [PATCH v2] clk: fixed-factor: add optional dt-binding clock-flags Quoting Rob Herring (2016-06-28 13:55:18) > On Fri, Jun 24, 2016 at 01:12:52PM +0900, Jongsung Kim wrote: > > There is no way to set additional flags for a DT-initialized fixed- > > factor-clock, and it can be problematic i.e., when the clock rate > > needs to be changed. [1][2] > > > > This patch introduces an optional dt-binding named "clock-flags" to > > be used for passing any needed flags from dts. > > I don't think we want this in DT. If we did, the flags would need some > documentation about what the flags mean. Flags are specific to Linux implementation, so I agree with Rob. Better to create a compatible string for your hardware that bakes in the flags. Regards, Mike > > Rob
Powered by blists - more mailing lists