linux-kernel - Re: [PATCH v2 0/3] clk: zynqmp: Add firmware specific clock flags

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]

Message-ID: <159554375224.3847286.3288318925600777669@swboyd.mtv.corp.google.com>
Date:   Thu, 23 Jul 2020 15:35:52 -0700
From:   Stephen Boyd <sboyd@...nel.org>
To:     Amit Sunil Dhamne <amit.sunil.dhamne@...inx.com>,
        linux-clk@...r.kernel.org, m.tretter@...gutronix.de,
        mark.rutland@....com, michal.simek@...inx.com,
        mturquette@...libre.com, sboyd@...eaurora.org
Cc:     rajanv@...inx.com, jollys@...inx.com, tejasp@...inx.com,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        Amit Sunil Dhamne <amit.sunil.dhamne@...inx.com>
Subject: Re: [PATCH v2 0/3] clk: zynqmp: Add firmware specific clock flags

Quoting Amit Sunil Dhamne (2020-07-21 23:55:29)
> This series adds supports for firmware specific flags. These include
> - Common Flags
> - Divider Flags
> - Mux Flags
> 
> The intent is to remove firmware's dependency on CCF flag values by having
> firmware specific flags with independent values.
> 
> Currently firmware is maintaining CCF specific flags and provides to
> CCF as it is. But CCF flag numbers may change and that shouldn't mean
> that the firmware needs to change. The firmware should have its own
> 'flag number space' that is distinct from the common clk framework's
> 'flag number space'. So use firmware specific clock flags in ZynqMP
> clock driver instead of CCF flags.
> 

Thanks for doing this work. Please resend with fixes.