[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <153029757874.143105.17774476792947607999@swboyd.mtv.corp.google.com>
Date: Fri, 29 Jun 2018 11:39:38 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Anson Huang <anson.huang@....com>, Shawn Guo <shawnguo@...nel.org>
Cc: "mark.rutland@....com" <mark.rutland@....com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"matteo.lisi@...icam.com" <matteo.lisi@...icam.com>,
"mturquette@...libre.com" <mturquette@...libre.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
dl-linux-imx <linux-imx@....com>,
"kernel@...gutronix.de" <kernel@...gutronix.de>,
Fabio Estevam <fabio.estevam@....com>,
"michael@...rulasolutions.com" <michael@...rulasolutions.com>,
"linux-clk@...r.kernel.org" <linux-clk@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH V2 2/2] ARM: dts: imx6ul: add GPIO clocks
Quoting Shawn Guo (2018-06-27 17:52:18)
> On Mon, Jun 25, 2018 at 03:14:39AM +0000, Anson Huang wrote:
> > Gentle Ping...
>
> I cannot apply this dts patch until the clock patch is landed on
> mainline, because it has a dependency on new clock ID IMX6UL_CLK_GPIO1
> created by clock patch.
>
Does it matter if that clk ID changes across branches? Or is everything
good if it just exists as some number? The patch adding the define
conflicts with another patch to fix the numbering scheme to be
incremental instead of changing IMX6UL and IMX6ULL which is annoying.
I'll probably make a topic branch just for the fix and merge it into
clk-fixes and this branch so you can pick it up from there if you like.
Powered by blists - more mailing lists