[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190312073654.GA85609@thor.local>
Date: Tue, 12 Mar 2019 08:36:54 +0100
From: Patrick Wildt <patrick@...eri.se>
To: Stephen Boyd <sboyd@...nel.org>
Cc: Abel Vesa <abel.vesa@....com>,
Fabio Estevam <fabio.estevam@....com>,
Lucas Stach <l.stach@...gutronix.de>,
Mark Rutland <mark.rutland@....com>,
Rob Herring <robh@...nel.org>,
Sascha Hauer <kernel@...gutronix.de>,
Shawn Guo <shawnguo@...nel.org>,
dl-linux-imx <linux-imx@....com>,
"devicetree@...r.kernel.org" <devicetree@...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: [PATCH] dt-bindings: clock: imx8mq: Fix numbering overlaps and
gaps
On Fri, Mar 08, 2019 at 07:29:05AM -0800, Stephen Boyd wrote:
> It's mostly about making sure that any existing dtbs don't have their
> numbers shifted around. So hopefully any overlapping identifiers aren't
> in use yet and then those ids can be changed while leaving the ones that
> are in use how they are.
In practice I bet no one uses Linux 5.0's i.MX8M device trees since they
lack too much support. It's so basic it's not useful. You'd still run
your existing non-mainline bindings until it is. Thus I would argue
changing the ABI right now would be the only chance there is.
If you think that chance is gone, then I guess the reasonable thing is
to keep the numbers and only move those (to the end) which overlap. Or
put them into that erreneous number gap.
Patrick
Powered by blists - more mailing lists