From: Andrea della Porta <andrea.porta@suse.com>
To: Alex Tran <alex.t.tran@gmail.com>
Cc: Andrea della Porta <andrea.porta@suse.com>,
Linus Walleij <linusw@kernel.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinctrl: pinctrl-rp1: Make use of str_hi_lo helper
Date: Mon, 6 Jul 2026 14:19:23 +0200 [thread overview]
Message-ID: <akudSxVwFByyeHA7@apocalypse> (raw)
In-Reply-To: <20260705-rp1-str-hi-lo-v1-1-1b452a5a8780@gmail.com>
Hi Alex,
On 09:01 Sun 05 Jul , Alex Tran wrote:
> Use the str_hi_lo helper API to print value
> of a pin for debugging instead of using
> ternary operator.
>
> Signed-off-by: Alex Tran <alex.t.tran@gmail.com>
> ---
> drivers/pinctrl/pinctrl-rp1.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/pinctrl/pinctrl-rp1.c b/drivers/pinctrl/pinctrl-rp1.c
> index fc4ed68ea5ac0bd272afe82076a36e93beba0539..dd0e85c2ca33a1ac506bf7ff0ceb424a7bde97d9 100644
> --- a/drivers/pinctrl/pinctrl-rp1.c
> +++ b/drivers/pinctrl/pinctrl-rp1.c
> @@ -1085,7 +1085,7 @@ static void rp1_pctl_pin_dbg_show(struct pinctrl_dev *pctldev,
>
> seq_printf(s, "function %s (%s) in %s; irq %d (%s)",
> rp1_func_names[fsel].name, rp1_func_names[func].name,
> - value ? "hi" : "lo",
> + str_hi_lo(value),
> irq, irq_type_names[pin->irq_type]);
> }
>
>
> ---
> base-commit: 2b763db0c2763d6bf73d7d3e69665222d1f377cf
> change-id: 20260704-rp1-str-hi-lo-cc64c3614be2
>
> Best regards,
> --
> Alex Tran <alex.t.tran@gmail.com>
>
Thanks for your submission!
Reviewed-by: Andrea della Porta <andrea.porta@suse.com>
next prev parent reply other threads:[~2026-07-06 12:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-05 16:01 [PATCH] pinctrl: pinctrl-rp1: Make use of str_hi_lo helper Alex Tran
2026-07-06 12:19 ` Andrea della Porta [this message]
2026-07-10 18:56 ` 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=akudSxVwFByyeHA7@apocalypse \
--to=andrea.porta@suse.com \
--cc=alex.t.tran@gmail.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.