[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_Jsq+281knebcN--jQgYWtDQO4OV6ZO5CvnYpaYqrAaiGmPQ@mail.gmail.com>
Date: Mon, 2 Aug 2021 11:29:35 -0600
From: Rob Herring <robh@...nel.org>
To: Michal Simek <michal.simek@...inx.com>
Cc: Sai Krishna Potthuri <lakshmi.sai.krishna.potthuri@...inx.com>,
Linus Walleij <linus.walleij@...aro.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
devicetree@...r.kernel.org,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
git <git@...inx.com>, saikrishna12468@...il.com
Subject: Re: [PATCH 4/4] arm: dts: zynq: Replace 'io-standard' with
'power-source' property
On Thu, Jul 29, 2021 at 10:59 PM Michal Simek <michal.simek@...inx.com> wrote:
>
>
>
> On 7/29/21 9:59 PM, Rob Herring wrote:
> > On Wed, Jul 21, 2021 at 05:22:33PM +0530, Sai Krishna Potthuri wrote:
> >> Replace 'io-standard' property with 'power-source' property in all zynq dts
> >> files to be in sync with Zynq pinctrl driver.
> >>
> >> Signed-off-by: Sai Krishna Potthuri <lakshmi.sai.krishna.potthuri@...inx.com>
> >> ---
> >> arch/arm/boot/dts/zynq-ebaz4205.dts | 8 ++++----
> >> arch/arm/boot/dts/zynq-microzed.dts | 2 +-
> >> arch/arm/boot/dts/zynq-zc702.dts | 20 ++++++++++----------
> >> arch/arm/boot/dts/zynq-zc706.dts | 18 +++++++++---------
> >> 4 files changed, 24 insertions(+), 24 deletions(-)
> >>
> >> diff --git a/arch/arm/boot/dts/zynq-ebaz4205.dts b/arch/arm/boot/dts/zynq-ebaz4205.dts
> >> index b0b836aedd76..be7eae611fb7 100644
> >> --- a/arch/arm/boot/dts/zynq-ebaz4205.dts
> >> +++ b/arch/arm/boot/dts/zynq-ebaz4205.dts
> >> @@ -57,7 +57,7 @@
> >>
> >> conf {
> >> groups = "gpio0_20_grp", "gpio0_32_grp";
> >> - io-standard = <3>;
> >> + power-source = <3>;
> >
> > This will break using a new DT with a kernel without patch 3.
> >
>
> What do you suggest? Not to update any old DT?
Your options are don't change the dts files, patch 3 needs to go to
stable kernels, or you document the breakage (if you don't care).
Rob
Powered by blists - more mailing lists