From: Hans de Goede <hansg@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Andy Shevchenko <andy@kernel.org>,
linux-spi@vger.kernel.org, linux-acpi@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] spi: Try to get ACPI GPIO IRQ earlier
Date: Thu, 6 Nov 2025 13:23:21 +0100 [thread overview]
Message-ID: <935e8578-1c25-4015-bd6e-a41cd0f07c81@kernel.org> (raw)
In-Reply-To: <176242886085.2357454.1138821772017853306.b4-ty@kernel.org>
Hi Mark,
On 6-Nov-25 12:34 PM, Mark Brown wrote:
> On Sun, 02 Nov 2025 20:09:21 +0100, Hans de Goede wrote:
>> Since commit d24cfee7f63d ("spi: Fix acpi deferred irq probe"), the
>> acpi_dev_gpio_irq_get() call gets delayed till spi_probe() is called
>> on the SPI device.
>>
>> If there is no driver for the SPI device then the move to spi_probe()
>> results in acpi_dev_gpio_irq_get() never getting called. This may
>> cause problems by leaving the GPIO pin floating because this call is
>> responsible for setting up the GPIO pin direction and/or bias according
>> to the values from the ACPI tables.
>>
>> [...]
>
> Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
>
> Thanks!
>
> [1/1] spi: Try to get ACPI GPIO IRQ earlier
> commit: 3cd2018e15b3d66d2187d92867e265f45ad79e6f
Thank you.
I believe that Andy's Reviewed-by was intended for a v2 with extending
the comment with an extra paragraph with something like:
"TODO: ideally the setup of the GPIO should be handled in a generic manner
in the ACPI/gpiolib core code".
Since you've already merged this now l'll prepare a follow-up patch
to extend the comment with that info.
Regards,
Hans
next prev parent reply other threads:[~2025-11-06 12:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-02 19:09 [PATCH] spi: Try to get ACPI GPIO IRQ earlier Hans de Goede
2025-11-03 9:35 ` Andy Shevchenko
2025-11-03 9:57 ` Hans de Goede
2025-11-03 10:13 ` Andy Shevchenko
2025-11-03 10:20 ` Hans de Goede
2025-11-03 13:15 ` Andy Shevchenko
2025-11-06 10:16 ` Andy Shevchenko
2025-11-06 11:34 ` Mark Brown
2025-11-06 12:23 ` Hans de Goede [this message]
2025-11-06 13:05 ` Mark Brown
2025-11-06 13:09 ` Andy Shevchenko
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=935e8578-1c25-4015-bd6e-a41cd0f07c81@kernel.org \
--to=hansg@kernel.org \
--cc=andy@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).