From: "Michael Walle" <mwalle@kernel.org>
To: "Bartosz Golaszewski" <brgl@kernel.org>
Cc: "Bartosz Golaszewski" <bartosz.golaszewski@oss.qualcomm.com>,
"Keerthy" <j-keerthy@ti.com>, "Linus Walleij" <linusw@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v2] gpio: davinci: implement .get_direction()
Date: Fri, 09 Jan 2026 16:00:38 +0100 [thread overview]
Message-ID: <DFK5CUIFIIIL.35VKCDMDEXVGS@kernel.org> (raw)
In-Reply-To: <CAMRc=MdJhqKMH4ap5zDf0Andy9h2XF1Z9bME6XvMSY52YRWGBQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
On Fri Jan 9, 2026 at 3:51 PM CET, Bartosz Golaszewski wrote:
> On Fri, Jan 9, 2026 at 3:48 PM Michael Walle <mwalle@kernel.org> wrote:
>>
>> >> 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).
>> >>
>> >
>> > Can you confirm, you're still seeing the issue with:
>> >
>> > https://lore.kernel.org/all/20260108-gpio-shared-false-positive-v1-1-5dbf8d1b2f7d@oss.qualcomm.com/
>>
>> Yes, latest next, with that patch applied, still causes the same
>> issue. I don't think it's a false positive as the same gpio is used
>> as enable for two different regulators :)
>>
>
> Yes, I responded under the other thread. Let's add Fixes: and use this
> as the solution?
Was just about to reply to the other thread, but lets keep it here:
Yes please, that will work for me.
Thanks,
-michael
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]
next prev parent reply other threads:[~2026-01-09 15:00 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
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 [this message]
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=DFK5CUIFIIIL.35VKCDMDEXVGS@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox