linux-kernel - Re: [PATCH v4] clk: vc5: use a dedicated struct to describe the output drivers

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] [day] [month] [year] [list]

Message-ID: <159554367631.3847286.15394463918985779147@swboyd.mtv.corp.google.com>
Date:   Thu, 23 Jul 2020 15:34:36 -0700
From:   Stephen Boyd <sboyd@...nel.org>
To:     Luca Ceresoli <luca@...aceresoli.net>, linux-clk@...r.kernel.org
Cc:     Luca Ceresoli <luca@...aceresoli.net>,
        linux-kernel@...r.kernel.org,
        Michael Turquette <mturquette@...libre.com>,
        Adam Ford <aford173@...il.com>,
        Marek Vasut <marek.vasut@...il.com>
Subject: Re: [PATCH v4] clk: vc5: use a dedicated struct to describe the output drivers

Quoting Luca Ceresoli (2020-07-23 00:26:03)
> Reusing the generic struct vc5_hw_data for all blocks is handy. However it
> implies we allocate space the div_int and div_frc fields even for the
> output drivers where they are unused, and the clk_output_cfg0 and
> clk_output_cfg0_mask fields for all components even though they are used
> only for the output drivers.
> 
> Use a dedicated struct for the output drivers so that each block uses
> exactly the fields it needs, not more.
> 
> Signed-off-by: Luca Ceresoli <luca@...aceresoli.net>
> 
> ---

Applied to clk-next