From: Marek Vasut <marex@nabladev.com>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: linux-i2c@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Srinivas Kandagatla <srini@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvmem: core: Mark nWP GPIO as non-exclusive
Date: Mon, 27 Jul 2026 15:24:11 +0200 [thread overview]
Message-ID: <6b7f6317-97bf-420a-84b1-6338ad236d13@nabladev.com> (raw)
In-Reply-To: <CAMRc=Mfm1R+CNt5nRY=A29TqTxHFZCHzZsWYd-WpE1yGrwt3Vw@mail.gmail.com>
On 7/27/26 3:10 PM, Bartosz Golaszewski wrote:
Hello Bartosz,
>>> No, this is literally how you do it. If you enable HAVE_SHARED_GPIOs and
>>> DEBUG_GPIO, you should see it being picked up in the kernel log.
>> Ah, HAVE_SHARED_GPIOS is what I did not have enabled. Is there any
>> reason why this is not enabled by default ?
>>
>
> It will be. I'm doing it gradually. It's enabled for Qualcomm platforms by
> default and - by extension - in arm64 defconfig. I plan to enable it for other
> platforms and architectures too, I just don't want to rush it. Enabling it for
> arm64 defconfig had caused quite a lot of regressions a few months ago so I
> prefer to be careful.
>
> What platform are you running this on?
NXP i.MX8M Nano (arm64)
next prev parent reply other threads:[~2026-07-28 3:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 16:35 Marek Vasut
2026-05-12 10:04 ` Bartosz Golaszewski
2026-05-18 19:22 ` Marek Vasut
2026-07-23 19:35 ` Marek Vasut
2026-07-24 7:30 ` Bartosz Golaszewski
2026-07-24 12:51 ` Marek Vasut
2026-07-27 13:10 ` Bartosz Golaszewski
2026-07-27 13:24 ` Marek Vasut [this message]
2026-07-28 8:32 ` Bartosz Golaszewski
2026-07-28 11:21 ` Marek Vasut
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=6b7f6317-97bf-420a-84b1-6338ad236d13@nabladev.com \
--to=marex@nabladev.com \
--cc=arnd@arndb.de \
--cc=brgl@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srini@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®