linux-kernel - Re: [EXT] Re: [RFC 00/19] clk: imx: Switch the imx6 and imx7 to clk

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: <155620761362.15276.4197988939287759775@swboyd.mtv.corp.google.com>
Date:   Thu, 25 Apr 2019 08:53:33 -0700
From:   Stephen Boyd <sboyd@...nel.org>
To:     Abel Vesa <abel.vesa@....com>
Cc:     Fabio Estevam <festevam@...il.com>,
        Shawn Guo <shawnguo@...nel.org>,
        Fabio Estevam <fabio.estevam@....com>,
        Aisheng Dong <aisheng.dong@....com>,
        Lucas Stach <l.stach@...gutronix.de>,
        Sascha Hauer <kernel@...gutronix.de>,
        "linux-clk@...r.kernel.org" <linux-clk@...r.kernel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [EXT] Re: [RFC 00/19] clk: imx: Switch the imx6 and imx7 to clk_hw based API

Quoting Abel Vesa (2019-04-24 00:13:48)
> 
> Can you please be more specific and point out exactly which one isn't ?

Is this a question for me?

> 
> > 
> > FYI, I'm dropping this from my review queue under the assumption it will
> > be sent again. Also, it would be nice to not have the wrappers at all in
> > the next series so that everything is clk_hw based instead of clk based.
> > Otherwise, it looks good to me and I'd like to see this work completed.
> > Thanks!
> > 
> 
> I'll try to resend this before the end of next week.
> 
> As for the wrappers, they need to stay in until the last user of the clk
> based API is switched to clk_hw based. That means all the remaining imx
> platforms (1 through 5, and then 8). I chosed to do the imx6 and imx7
> first because these are easier to find. Once this is in, I'll move on
> with the imx8 and then the imx1 through imx5 (which are harder to find
> nowadays).
> 

Ok. I'm not thrilled to keep around legacy code because nobody is
testing out new kernels on these devices. If we can, we should try to
delete old drivers that don't get used anymore, but if we can't then
we should be able to modify and compile those drivers and wait for the
bug reports to come in if something is broken.