From: "Michael Walle" <mwalle@kernel.org>
To: "Bartosz Golaszewski" <bartosz.golaszewski@oss.qualcomm.com>,
"Keerthy" <j-keerthy@ti.com>, "Linus Walleij" <linusw@kernel.org>,
"Bartosz Golaszewski" <brgl@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v2] gpio: davinci: implement .get_direction()
Date: Fri, 09 Jan 2026 15:12:23 +0100 [thread overview]
Message-ID: <DFK4BWTWHHQF.2IBES82YDKAEC@kernel.org> (raw)
In-Reply-To: <20260109130832.27326-1-bartosz.golaszewski@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]
Hi,
On Fri Jan 9, 2026 at 2:08 PM CET, Bartosz Golaszewski wrote:
> It's strongly recommended for GPIO drivers to always implement the
> .get_direction() callback - even for fixed-direction controllers.
>
> GPIO core will even emit a warning if the callback is missing, when
> users try to read the direction of a pin.
>
> Implement .get_direction() for gpio-davinci.
I must be blind! I didn't see the direction register and I assumed
that the direction is fixed and only known by the pinctrl (as on k3
SoCs, you have to hardcode the directions of GPIOs in the device
tree.
Thanks for taking care.
> Reported-by: Michael Walle <mwalle@kernel.org>
> Closes: https://lore.kernel.org/all/DFJAFK3DTBOZ.3G2P3A5IH34GF@kernel.org/
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
This will need a
Fixes: a060b8c511ab ("gpiolib: implement low-level, shared GPIO support")
Otherwise the sa67 board will be broken with the defconfig (or any
config enabled ARCH_QCOM).
Tested-by: Michael Walle <mwalle@kernel.org> # on sa67
-michael
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]
next prev parent reply other threads:[~2026-01-09 14:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 13:08 [PATCH v2] gpio: davinci: implement .get_direction() Bartosz Golaszewski
2026-01-09 14:12 ` Michael Walle [this message]
2026-01-09 14:22 ` Bartosz Golaszewski
2026-01-09 14:48 ` Michael Walle
2026-01-09 14:51 ` Bartosz Golaszewski
2026-01-09 15:00 ` Michael Walle
2026-01-09 14:32 ` Linus Walleij
2026-01-12 8:41 ` Bartosz Golaszewski
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=DFK4BWTWHHQF.2IBES82YDKAEC@kernel.org \
--to=mwalle@kernel.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=j-keerthy@ti.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.