From: Michal Simek <monstr@monstr.eu>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Rob Herring <robh@kernel.org>,
Sai Krishna Potthuri <lakshmi.sai.krishna.potthuri@xilinx.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<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, 2 Aug 2021 19:21:58 +0200 [thread overview]
Message-ID: <CAHTX3dLbRcfBhaqfbcK=RbQOAG5uxpSzHmMx7aP+QYHaP-idew@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdZu2-EE1hqJ4nVA5uxaPuJRGWDH_ciKxRvrNncQ2Pyd5w@mail.gmail.com>
po 2. 8. 2021 v 15:20 odesílatel Linus Walleij
<linus.walleij@linaro.org> napsal:
>
> On Fri, Jul 30, 2021 at 2:46 PM Michal Simek <michal.simek@xilinx.com> wrote:
>
> > Linux Zynq pinctrl driver and in tree dts files are using io-standard
> > properties at least from 2015.
>
> Ooops my wrong.
>
> What about supporting both the new property and io-standard as
> a fallback, simply?
That's exactly what I have Sai to do and PIN_CONFIG_IOSTANDARD is still there.
https://lore.kernel.org/linux-arm-kernel/1626868353-96475-1-git-send-email-lakshmi.sai.krishna.potthuri@xilinx.com/T/#md7d304d9d8f746e51d909237b9073f2ae8930543
But IIRC I have also asked to show any warning message when io
standard property is used to convert to new property.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal SoCs
next prev parent reply other threads:[~2021-08-02 17:22 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
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 [this message]
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='CAHTX3dLbRcfBhaqfbcK=RbQOAG5uxpSzHmMx7aP+QYHaP-idew@mail.gmail.com' \
--to=monstr@monstr.eu \
--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).