From: Michal Simek <michal.simek@xilinx.com>
To: Rob Herring <robh@kernel.org>, Michal Simek <michal.simek@xilinx.com>
Cc: Sai Krishna Potthuri <lakshmi.sai.krishna.potthuri@xilinx.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
git <git@xilinx.com>, <saikrishna12468@gmail.com>
Subject: Re: [PATCH 4/4] arm: dts: zynq: Replace 'io-standard' with 'power-source' property
Date: Mon, 16 Aug 2021 11:08:06 +0200 [thread overview]
Message-ID: <c49c9633-4bc6-0cdd-cb3d-8b9ffc92b671@xilinx.com> (raw)
In-Reply-To: <fd759de0-d74f-3aa1-ad46-e3ee7f7f7e3f@xilinx.com>
Hi Rob,
On 8/5/21 9:52 AM, Michal Simek wrote:
>
>
> On 8/2/21 7:29 PM, Rob Herring wrote:
>> On Thu, Jul 29, 2021 at 10:59 PM Michal Simek <michal.simek@xilinx.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@xilinx.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).
>
> There is no intention to go to stable kernel and I don't think this is
> stable material. Linus has applied 3 patches and this one should go via
> my tree. It means I will make sure that this DT change will be in the
> tree when pinctrl changes are applied.
Any issue with this patch? Or can I apply it to my tree?
Thanks,
Michal
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-08-16 9:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 11:52 [PATCH 0/4] pinctrl: pinctrl-zynq: yaml conversion and minor driver updates Sai Krishna Potthuri
2021-07-21 11:52 ` [PATCH 1/4] dt-bindings: pinctrl: pinctrl-zynq: Convert to yaml Sai Krishna Potthuri
2021-07-29 19:56 ` Rob Herring
2021-07-21 11:52 ` [PATCH 2/4] dt-bindings: pinctrl-zynq: Replace 'io-standard' with 'power-source' Sai Krishna Potthuri
2021-07-21 11:52 ` [PATCH 3/4] pinctrl: pinctrl-zynq: Add support for 'power-source' parameter Sai Krishna Potthuri
2021-07-21 11:52 ` [PATCH 4/4] arm: dts: zynq: Replace 'io-standard' with 'power-source' property Sai Krishna Potthuri
2021-07-29 19:59 ` Rob Herring
2021-07-30 4:59 ` Michal Simek
2021-08-02 17:29 ` Rob Herring
2021-08-05 7:52 ` Michal Simek
2021-08-16 9:08 ` Michal Simek [this message]
2021-07-30 12:43 ` Linus Walleij
2021-07-30 12:46 ` Michal Simek
2021-08-02 13:19 ` Linus Walleij
2021-08-02 17:21 ` Michal Simek
2021-07-30 12:41 ` [PATCH 0/4] pinctrl: pinctrl-zynq: yaml conversion and minor driver updates Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c49c9633-4bc6-0cdd-cb3d-8b9ffc92b671@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=gregkh@linuxfoundation.org \
--cc=lakshmi.sai.krishna.potthuri@xilinx.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=saikrishna12468@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).