[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5DWphRs_ZdDiNPLo0MPo45vBTEojWhYnZyWYF6+t12jxw@mail.gmail.com>
Date: Thu, 31 Oct 2019 09:07:22 -0300
From: Fabio Estevam <festevam@...il.com>
To: Peng Fan <peng.fan@....com>
Cc: "sboyd@...nel.org" <sboyd@...nel.org>,
"shawnguo@...nel.org" <shawnguo@...nel.org>,
"s.hauer@...gutronix.de" <s.hauer@...gutronix.de>,
Abel Vesa <abel.vesa@....com>,
"kernel@...gutronix.de" <kernel@...gutronix.de>,
dl-linux-imx <linux-imx@....com>,
Anson Huang <anson.huang@....com>,
Jacky Bai <ping.bai@....com>,
"linux-clk@...r.kernel.org" <linux-clk@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Leonard Crestez <leonard.crestez@....com>
Subject: Re: [PATCH 2/2] clk: imx: imx7d: remove clk_set_parent
Hi Peng,
On Thu, Oct 31, 2019 at 7:02 AM Peng Fan <peng.fan@....com> wrote:
>
> From: Peng Fan <peng.fan@....com>
>
> Since the set parent could be done by assigned-clock-parents in
> dts, so no need clk_set_parent in driver.
It looks like this will cause breakage if someone is using an old dtb, right?
We try not to break existing dtbs.
Powered by blists - more mailing lists