From: Michal Simek <michal.simek@xilinx.com>
To: Sai Krishna Potthuri <lakshmi.sai.krishna.potthuri@xilinx.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
Michal Simek <michal.simek@xilinx.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-gpio@vger.kernel.org>,
<git@xilinx.com>, <saikrishna12468@gmail.com>
Subject: Re: [PATCH] pinctrl: pinctrl-zynq: Add warning for not to use 'io-standard'
Date: Wed, 18 Aug 2021 08:00:03 +0200 [thread overview]
Message-ID: <447d7205-f562-72c2-8317-031cd733d60c@xilinx.com> (raw)
In-Reply-To: <1629265999-33358-1-git-send-email-lakshmi.sai.krishna.potthuri@xilinx.com>
On 8/18/21 7:53 AM, Sai Krishna Potthuri wrote:
> This patch add warning message saying 'io-standard' property is deprecated
> and instead use 'power-source' property for configuring power supplies.
> This gives an indication for Zynq pinctrl users to migrate to use
> 'power-source' property.
>
> Signed-off-by: Sai Krishna Potthuri <lakshmi.sai.krishna.potthuri@xilinx.com>
> ---
> drivers/pinctrl/pinctrl-zynq.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/pinctrl/pinctrl-zynq.c b/drivers/pinctrl/pinctrl-zynq.c
> index a96af8a..5b269b6 100644
> --- a/drivers/pinctrl/pinctrl-zynq.c
> +++ b/drivers/pinctrl/pinctrl-zynq.c
> @@ -1028,6 +1028,8 @@ static int zynq_pinconf_cfg_get(struct pinctrl_dev *pctldev,
> break;
> }
> case PIN_CONFIG_IOSTANDARD:
> + dev_warn(pctldev->dev, "io-standard is deprecated, please use power-source");
> + fallthrough;
> case PIN_CONFIG_POWER_SOURCE:
> arg = zynq_pinconf_iostd_get(reg);
> break;
> @@ -1079,6 +1081,8 @@ static int zynq_pinconf_cfg_set(struct pinctrl_dev *pctldev,
>
> break;
> case PIN_CONFIG_IOSTANDARD:
> + dev_warn(pctldev->dev, "io-standard is deprecated, please use power-source");
> + fallthrough;
> case PIN_CONFIG_POWER_SOURCE:
> if (arg <= zynq_iostd_min || arg >= zynq_iostd_max) {
> dev_warn(pctldev->dev,
>
Acked-by: Michal Simek <michal.simek@xilinx.com>
Linus: would be good to know how long we should keep the support for
this deprecated dt property.
Thanks,
Michal
next prev parent reply other threads:[~2021-08-18 6:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 5:53 Sai Krishna Potthuri
2021-08-18 6:00 ` Michal Simek [this message]
2021-08-18 23:37 ` 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=447d7205-f562-72c2-8317-031cd733d60c@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=git@xilinx.com \
--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=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
all inboxes | Powered by JetHome®