From: Jon Hunter <jonathanh@nvidia.com>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: Linus Walleij <linusw@kernel.org>,
linux-gpio@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] gpiolib: Make deferral warnings debug messages
Date: Thu, 2 Apr 2026 09:18:50 +0100 [thread overview]
Message-ID: <f91fe309-9c7e-486d-8d35-90cf64869082@nvidia.com> (raw)
In-Reply-To: <CAMRc=Me4-KS0=GL8SdwnhzP-YYWoYZpyzciS1L1iF=ip=1FQ9g@mail.gmail.com>
On 02/04/2026 09:10, Bartosz Golaszewski wrote:
> On Wed, Apr 1, 2026 at 3:35 PM Jon Hunter <jonathanh@nvidia.com> wrote:
>>
>> With the recent addition of the shared GPIO support, warning messages
>> such as the following are being observed ...
>>
>> reg-fixed-voltage regulator-vdd-3v3-pcie: cannot find GPIO chip
>> gpiolib_shared.proxy.6, deferring
>>
>> These are seen even with GPIO_SHARED_PROXY=y.
I meant CONFIG_GPIO_SHARED_PROXY=y here :-)
Let me know if you want me to send an updated version?
>>
>> Given that the GPIOs are successfully found a bit later during boot and
>> the code is intentionally returning -EPROBE_DEFER when they are not
>> found, downgrade these messages to debug prints to avoid unnecessary
>> warnings being observed.
>>
>> Note that although the 'cannot find GPIO line' warning has not been
>> observed in this case, it seems reasonable to make this print a debug
>> print for consistency too.
>>
>> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
>> ---
>
> Yes, this makes sense. FYI I also have a grand plan of introducing
> support for fw_devlink for software nodes and assigning them to shared
> proxies with the aim of them respecting the probe order that way.
OK, good to know.
Thanks
Jon
--
nvpublic
next prev parent reply other threads:[~2026-04-02 8:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 13:34 [PATCH] gpiolib: Make deferral warnings debug messages Jon Hunter
2026-04-02 8:10 ` Bartosz Golaszewski
2026-04-02 8:18 ` Jon Hunter [this message]
2026-04-03 9:03 ` 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=f91fe309-9c7e-486d-8d35-90cf64869082@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=brgl@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-tegra@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