linux-kernel - Re: [PATCH v1 1/2] clk: intel: Add CGU clock driver for a new SoC

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: <20190916183619.50926206C2@mail.kernel.org>
Date:   Mon, 16 Sep 2019 11:36:18 -0700
From:   Stephen Boyd <sboyd@...nel.org>
To:     "Kim, Cheol Yong" <cheol.yong.kim@...ux.intel.com>,
        "Tanwar, Rahul" <rahul.tanwar@...ux.intel.com>,
        Martin Blumenstingl <martin.blumenstingl@...glemail.com>
Cc:     andriy.shevchenko@...el.com, cheol.yong.kim@...el.com,
        linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org,
        mark.rutland@....com, mturquette@...libre.com,
        qi-ming.wu@...el.com, rahul.tanwar@...el.com, robh+dt@...nel.org,
        robh@...nel.org, yixin.zhu@...ux.intel.com
Subject: Re: [PATCH v1 1/2] clk: intel: Add CGU clock driver for a new SoC

Quoting Kim, Cheol Yong (2019-09-09 07:16:29)
> 
> I've discussed internally the amount of efforts to create a reusable 
> regmap clock driver which might be reused by other companies too.
> 
> It seems it requires significant efforts for implementation/tests. As we 
> don't plan to support our old SOCs for now, I'm not sure if we need to 
> put such a big efforts.
> 
> Stephan,
> 
> It seems you don't like both meson/qcom regmap clock implementation.
> 
> What is your opinion for our current CGU clock driver implementation?
> 
> 

If you're not going to use regmap in CGU then it doesn't matter to try
to consolidate the regmap clk implementations.