From: Rustam Adilov <adilov@disroot.org>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: Linus Walleij <linusw@kernel.org>,
Sander Vanheule <sander@svanheule.net>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] gpio: realtek-otto: decide bank_read/write by device endianness
Date: Wed, 15 Jul 2026 19:00:45 +0000 [thread overview]
Message-ID: <3d6b8d6ab53aadef56e68c925030dd3b@disroot.org> (raw)
In-Reply-To: <CAMRc=MddZxoi_=QCFYp1PM8OwsWbz-Tsmoa7TMkQ1bh+qf-pdA@mail.gmail.com>
Hello,
On 2026-07-15 09:39, Bartosz Golaszewski wrote:
> On Fri, 10 Jul 2026 20:34:39 +0200, Rustam Adilov <adilov@disroot.org> said:
>> In order to have a working gpio controller with SWAP_IO_SPACE,
>> the way bank_read and bank_write are defined must be changed and
>> separated from GPIO_PORTS_REVERSED flag. That also includes the
>> flags parameter used by gpio_generic_chip_config.
>>
>> To achieve it, use the device_is_big_endian() to decide the
>> bank_read/write parameter and the flag.
>>
>> Signed-off-by: Rustam Adilov <adilov@disroot.org>
>> ---
>> drivers/gpio/gpio-realtek-otto.c | 15 +++++++++------
>> 1 file changed, 9 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/gpio/gpio-realtek-otto.c b/drivers/gpio/gpio-realtek-otto.c
>> index 491fde846d46..f96072fbce92 100644
>> --- a/drivers/gpio/gpio-realtek-otto.c
>> +++ b/drivers/gpio/gpio-realtek-otto.c
>> @@ -393,16 +393,19 @@ static int realtek_gpio_probe(struct platform_device *pdev)
>>
>> raw_spin_lock_init(&ctrl->lock);
>>
>> - if (dev_flags & GPIO_PORTS_REVERSED) {
>> - gen_gc_flags = 0;
>> - ctrl->bank_read = realtek_gpio_bank_read;
>> - ctrl->bank_write = realtek_gpio_bank_write;
>> + if (dev_flags & GPIO_PORTS_REVERSED)
>> ctrl->line_imr_pos = realtek_gpio_line_imr_pos;
>> - } else {
>> + else
>> + ctrl->line_imr_pos = realtek_gpio_line_imr_pos_swapped;
>> +
>> + if (device_is_big_endian(dev)) {
>> gen_gc_flags = GPIO_GENERIC_BIG_ENDIAN_BYTE_ORDER;
>> ctrl->bank_read = realtek_gpio_bank_read_swapped;
>> ctrl->bank_write = realtek_gpio_bank_write_swapped;
>> - ctrl->line_imr_pos = realtek_gpio_line_imr_pos_swapped;
>> + } else {
>> + gen_gc_flags = 0;
>> + ctrl->bank_read = realtek_gpio_bank_read;
>> + ctrl->bank_write = realtek_gpio_bank_write;
>> }
>>
>> config = (struct gpio_generic_chip_config) {
>> --
>> 2.55.0
>>
>>
>
> Can you look at the sashiko report? I think it's right about this change
> possibly breaking existing devicetrees. Can we keep big-endian as the
> default?
>
> Bart
Oh i didn't know sashiko was looking after this subsystem too.
But yes, it does require the rtl8380-gpio, rtl8390-gpio, rtl9310-gpio
to append big-endian or native-endian (as they are all big endian chips).
I was thinking earlier whatever it is appropriate to make changes to
the arch/mips/boot/dts/realtek in this commit because it is different
subsystem entirely but i guess this (previous sentence) answers the
question, doesn't it.
Also, what exactly do you mean by "Can we keep big-endian as the
default?" ? My only reading off is to change the if statement
so that the big endian flag and the _swapped functions to be
under the else part, is it correct?
Best,
Rustam
prev parent reply other threads:[~2026-07-15 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 18:34 [PATCH 0/2] gpio: realtek-otto: make the driver work with SWAP_IO_SPACE Rustam Adilov
2026-07-10 18:34 ` [PATCH 1/2] gpio: realtek-otto: use __raw_readl/writel in realtek_gpio_update_line_imr() Rustam Adilov
2026-07-10 18:34 ` [PATCH 2/2] gpio: realtek-otto: decide bank_read/write by device endianness Rustam Adilov
2026-07-15 9:39 ` Bartosz Golaszewski
2026-07-15 19:00 ` Rustam Adilov [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=3d6b8d6ab53aadef56e68c925030dd3b@disroot.org \
--to=adilov@disroot.org \
--cc=brgl@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sander@svanheule.net \
/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