From: Mark Cave-Ayland <mark.caveayland@nutanix.com>
To: William Breathitt Gray <wbg@kernel.org>, mwalle@kernel.org
Cc: linus.walleij@linaro.org, brgl@bgdev.pl,
andriy.shevchenko@linux.intel.com, broonie@kernel.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: gpio: gpio-pci-idio-16 regression after LTS upgrade
Date: Thu, 9 Oct 2025 10:05:58 +0100 [thread overview]
Message-ID: <df4857cb-daae-4428-bd93-5878564624c5@nutanix.com> (raw)
In-Reply-To: <20251007081657.30422-1-wbg@kernel.org>
On 07/10/2025 09:16, William Breathitt Gray wrote:
> On Mon, Oct 06, 2025 at 09:37:14AM +0100, Mark Cave-Ayland wrote:
>> root@debian12:~# gpioget 0 0
>> gpioget: error reading GPIO values: Input/output error
>>
>> which also output:
>>
>> [ 329.529321] gpio-512 (gpioget): gpiod_direction_input: missing
>> direction_input() operation and line is output
>>
>> My guess is that this is because
>> drivers/gpio/gpio-regmap.c::gpio_regmap_get_direction() isn't able to
>> can't handle the situation where lines 0-15 are outputs and lines 16-31
>> are inputs, compared with the old idio_16_gpio_get_direction() function
>> it replaced.
>>
>> What would be the best way forward? Possibly add the .get_direction
>> callback to the gpio_regmap_config? Or is there another way to have
>> mixed inputs and outputs with the gpio_regmap API?
>
> So the intention I had with gpio-idio-16 was to provide reg_dat_base and
> reg_set_base to define the input and output bases, and then
> reg_mask_xlate would do the translation between input and outputs. I
> think this design is allowed by gpio-regmap, is it not Michael?
>
> In theory, gpio_regmap_get_direction should call gpio->reg_mask_xlate()
> which is mapped to idio_16_reg_mask_xlate(), and thus set reg and mask
> which then is evaluated at the end of gpio_regmap_get_direction() to
> determine which direction to return.
>
> Is it possible idio_16_reg_mask_xlate() is returning the wrong values
> for reg and mask?
>
> William Breathitt Gray
The only logic around .reg_dat_base and .reg_set_base in
gpio_regmap_get_direction() is this:
if (gpio->reg_dat_base && !gpio->reg_set_base)
return GPIO_LINE_DIRECTION_IN;
if (gpio->reg_set_base && !gpio->reg_dat_base)
return GPIO_LINE_DIRECTION_OUT;
Otherwise it attempts to use .reg_dir_out_base and .reg_dir_in_base
which are not set for gpio-idio-16 because the GPIO directions are fixed
and not controlled via a data-direction register. And as these are not
set, gpio_regmap_get_direction() returns -ENOTSUPP.
Were you thinking that gpio_regmap_get_direction() should have some
additional direction logic if both .reg_dat_base and .reg_set_base are
set, based upon their comparative values?
ATB,
Mark.
next prev parent reply other threads:[~2025-10-09 9:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 8:37 Mark Cave-Ayland
2025-10-07 8:16 ` William Breathitt Gray
2025-10-09 9:05 ` Mark Cave-Ayland [this message]
2025-10-09 9:49 ` William Breathitt Gray
2025-10-14 9:03 ` Michael Walle
2025-10-14 11:21 ` Ioana Ciornei
2025-10-14 11:25 ` Michael Walle
2025-10-14 11:40 ` Ioana Ciornei
2025-10-12 14:22 ` William Breathitt Gray
2025-10-13 10:32 ` Mark Cave-Ayland
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=df4857cb-daae-4428-bd93-5878564624c5@nutanix.com \
--to=mark.caveayland@nutanix.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mwalle@kernel.org \
--cc=wbg@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®