[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5DWpu9irOWR3rux-vV1sihfsDkTs5SJ7XXy8MgRBCd-Gw@mail.gmail.com>
Date: Fri, 22 Mar 2019 13:24:54 -0300
From: Fabio Estevam <festevam@...il.com>
To: Abel Vesa <abel.vesa@....com>
Cc: Stephen Boyd <sboyd@...nel.org>, 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: [RFC 00/19] clk: imx: Switch the imx6 and imx7 to clk_hw based API
Hi Abel,
On Fri, Mar 22, 2019 at 12:37 PM Abel Vesa <abel.vesa@....com> wrote:
>
> This work is part of the effort of switching the entire imx clock drivers
> towards clk_hw based API. In order to do that, we have to keep the old
Maybe I missed some earlier discussions on this topic, but let me ask
a fundamental question first: what is the motivation for this API
change?
I could not find the reasoning inside the series.
Powered by blists - more mailing lists