From: Andre Przywara <andre.przywara@arm.com>
To: wens@kernel.org
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinctrl: sunxi: A523: fix voltage withstand encoding
Date: Mon, 14 Sep 2026 12:08:43 +0200 [thread overview]
Message-ID: <04fe6b38-c662-4b87-9544-8df1d8367122@arm.com> (raw)
In-Reply-To: <CAGb2v67TW_E7S9Mt1RyGJdw8NbV0D0PzM8Sw0Vhx9PzMe6CVwg@mail.gmail.com>
Hi Chen-Yu,
On 9/13/26 17:34, Chen-Yu Tsai wrote:
> On Fri, Sep 11, 2026 at 4:14 AM Andre Przywara <andre.przywara@arm.com> wrote:
>>
>> On Thu, 23 Jul 2026 01:26:38 +0800
>> Chen-Yu Tsai <wens@kernel.org> wrote:
>>
>> Hi,
>>
>>> On Wed, Jul 22, 2026 at 6:43 AM Andre Przywara <andre.przywara@arm.com> wrote:
>>>>
>>>> The Allwinner A523 uses the same GPIO voltage "withstand" programming
>>>> (setting the input level voltage thresholds) as the previous SoCs, but
>>>> for some odd reason inverts the encoding of 1.8V vs. 3.3V.
>>>>
>>>> Add a new bias voltage type to note this difference, and select it for
>>>> the A523. At the same time also use the newer "CTL" version, which in
>>>> addition allows to turn off the withstand programming for I/O voltages
>>>> other than exact 1.8V or 3.3V (for instance for 2.5V sometimes used for
>>>> Ethernet PHYs). The A523 has that enable register, but didn't use it
>>>> so far.
>>>>
>>>> This fixes eMMC and reportedly Ethernet operation on some A523 boards.
>>>>
>>>> Fixes: 648be4cd9517 ("pinctrl: sunxi: Add support for the Allwinner A523")
>>>> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
>>>
>>>
>>> Reviewed-by: Chen-Yu Tsai <wens@kernel.org>
>>> Tested-by: Chen-Yu Tsai <wens@kernel.org> # Fixes eMMC on Orange Pi 4A
>>
>> so what happens to this fix? Is it good to be merged? And who is going
>> to take this? Linus? Or does it go through sunxi?
>
> Linus needs to take this. It seems you didn't send it to him, nor the
> linux-gpio mailing list?
Ah, good point, thanks for the heads up, for some reason I CC:ed DT
people, but not pinctrl. My bad, and might explain why this was somehow
forgotten about.
Sent a v2 with all the tags, thanks to the testers and reviewers!
Cheers,
Andre.
> Can you resend?
>
>> Cheers,
>> Andre
>>
>>>> ---
>>>> drivers/pinctrl/sunxi/pinctrl-sun55i-a523-r.c | 2 +-
>>>> drivers/pinctrl/sunxi/pinctrl-sun55i-a523.c | 2 +-
>>>> drivers/pinctrl/sunxi/pinctrl-sunxi.c | 6 ++++++
>>>> drivers/pinctrl/sunxi/pinctrl-sunxi.h | 2 ++
>>>> 4 files changed, 10 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/drivers/pinctrl/sunxi/pinctrl-sun55i-a523-r.c b/drivers/pinctrl/sunxi/pinctrl-sun55i-a523-r.c
>>>> index dfdcfa740ecc9..cffc1e53eef14 100644
>>>> --- a/drivers/pinctrl/sunxi/pinctrl-sun55i-a523-r.c
>>>> +++ b/drivers/pinctrl/sunxi/pinctrl-sun55i-a523-r.c
>>>> @@ -26,7 +26,7 @@ static const u8 a523_r_irq_bank_muxes[SUNXI_PINCTRL_MAX_BANKS] =
>>>> static struct sunxi_pinctrl_desc a523_r_pinctrl_data = {
>>>> .irq_banks = ARRAY_SIZE(a523_r_irq_bank_map),
>>>> .irq_bank_map = a523_r_irq_bank_map,
>>>> - .io_bias_cfg_variant = BIAS_VOLTAGE_PIO_POW_MODE_SEL,
>>>> + .io_bias_cfg_variant = BIAS_VOLTAGE_PIO_POW_MODE_CTL_INV,
>>>> .pin_base = PL_BASE,
>>>> };
>>>>
>>>> diff --git a/drivers/pinctrl/sunxi/pinctrl-sun55i-a523.c b/drivers/pinctrl/sunxi/pinctrl-sun55i-a523.c
>>>> index 801f62abc93df..001bd42afa3ef 100644
>>>> --- a/drivers/pinctrl/sunxi/pinctrl-sun55i-a523.c
>>>> +++ b/drivers/pinctrl/sunxi/pinctrl-sun55i-a523.c
>>>> @@ -26,7 +26,7 @@ static const u8 a523_irq_bank_muxes[SUNXI_PINCTRL_MAX_BANKS] =
>>>> static struct sunxi_pinctrl_desc a523_pinctrl_data = {
>>>> .irq_banks = ARRAY_SIZE(a523_irq_bank_map),
>>>> .irq_bank_map = a523_irq_bank_map,
>>>> - .io_bias_cfg_variant = BIAS_VOLTAGE_PIO_POW_MODE_SEL,
>>>> + .io_bias_cfg_variant = BIAS_VOLTAGE_PIO_POW_MODE_CTL_INV,
>>>> };
>>>>
>>>> static int a523_pinctrl_probe(struct platform_device *pdev)
>>>> diff --git a/drivers/pinctrl/sunxi/pinctrl-sunxi.c b/drivers/pinctrl/sunxi/pinctrl-sunxi.c
>>>> index cabcb8b6f38e5..634d9f1f23947 100644
>>>> --- a/drivers/pinctrl/sunxi/pinctrl-sunxi.c
>>>> +++ b/drivers/pinctrl/sunxi/pinctrl-sunxi.c
>>>> @@ -718,6 +718,7 @@ static int sunxi_pinctrl_set_io_bias_cfg(struct sunxi_pinctrl *pctl,
>>>> {
>>>> unsigned short bank;
>>>> unsigned long flags;
>>>> + bool inverted = false;
>>>> u32 val, reg;
>>>> int uV;
>>>>
>>>> @@ -757,6 +758,9 @@ static int sunxi_pinctrl_set_io_bias_cfg(struct sunxi_pinctrl *pctl,
>>>> writel(reg | val, pctl->membase +
>>>> sunxi_grp_config_reg(pctl, pin));
>>>> return 0;
>>>> + case BIAS_VOLTAGE_PIO_POW_MODE_CTL_INV:
>>>> + inverted = true;
>>>> + fallthrough;
>>>> case BIAS_VOLTAGE_PIO_POW_MODE_CTL:
>>>> val = uV > 1800000 && uV <= 2500000 ? BIT(bank) : 0;
>>>>
>>>> @@ -771,6 +775,8 @@ static int sunxi_pinctrl_set_io_bias_cfg(struct sunxi_pinctrl *pctl,
>>>> fallthrough;
>>>> case BIAS_VOLTAGE_PIO_POW_MODE_SEL:
>>>> val = uV <= 1800000 ? 1 : 0;
>>>> + if (inverted)
>>>> + val = !val;
>>>>
>>>> raw_spin_lock_irqsave(&pctl->lock, flags);
>>>> reg = readl(pctl->membase + pctl->pow_mod_sel_offset);
>>>> diff --git a/drivers/pinctrl/sunxi/pinctrl-sunxi.h b/drivers/pinctrl/sunxi/pinctrl-sunxi.h
>>>> index d0936a32123ba..2c8648c3301b6 100644
>>>> --- a/drivers/pinctrl/sunxi/pinctrl-sunxi.h
>>>> +++ b/drivers/pinctrl/sunxi/pinctrl-sunxi.h
>>>> @@ -128,8 +128,10 @@ enum sunxi_desc_bias_voltage {
>>>> * Bias voltage is set through PIO_POW_MOD_SEL_REG
>>>> * and PIO_POW_MOD_CTL_REG register, as seen on
>>>> * A100 and D1 SoC, for example.
>>>> + * Some SoCs invert the encoding for 1.8V vs. 3.3V.
>>>> */
>>>> BIAS_VOLTAGE_PIO_POW_MODE_CTL,
>>>> + BIAS_VOLTAGE_PIO_POW_MODE_CTL_INV,
>>>> };
>>>>
>>>> struct sunxi_desc_function {
>>>> --
>>>> 2.46.4
>>>>
>>>
>>
prev parent reply other threads:[~2026-09-14 10:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 22:39 Andre Przywara
2026-07-22 12:17 ` Per Larsson
2026-07-22 17:23 ` Juan Manuel López Carrillo
2026-07-22 22:23 ` Andre Przywara
2026-07-30 17:40 ` Juan Manuel
2026-07-31 13:08 ` Andre Przywara
2026-07-31 13:20 ` Chen-Yu Tsai
2026-08-03 15:35 ` Juan Manuel López Carrillo
2026-08-03 15:51 ` Chen-Yu Tsai
2026-08-04 18:11 ` Chen-Yu Tsai
2026-08-10 17:22 ` Juan Manuel López Carrillo
2026-07-22 17:26 ` Chen-Yu Tsai
2026-09-10 20:13 ` Andre Przywara
2026-09-13 15:34 ` Chen-Yu Tsai
2026-09-14 10:08 ` Andre Przywara [this message]
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=04fe6b38-c662-4b87-9544-8df1d8367122@arm.com \
--to=andre.przywara@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=robh@kernel.org \
--cc=samuel@sholland.org \
--cc=wens@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 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®