public inbox for linux-spi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Hans de Goede <hansg@kernel.org>
Cc: Mark Brown <broonie@kernel.org>,
	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: Mon, 3 Nov 2025 11:35:00 +0200	[thread overview]
Message-ID: <aQh3RJQ95jTx7VYO@smile.fi.intel.com> (raw)
In-Reply-To: <20251102190921.30068-1-hansg@kernel.org>

On Sun, Nov 02, 2025 at 08:09:21PM +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.
> 
> Re-add the removed acpi_dev_gpio_irq_get() in acpi_register_spi_device()
> to ensure the GPIO pin is always correctly setup, while keeping the
> acpi_dev_gpio_irq_get() call added to spi_probe() to deal with
> -EPROBE_DEFER returns caused by the GPIO controller not having a driver
> yet.

Even before following the link to some papering over module via the link below
I wondered, if the I²C case should be covered as well. The
https://github.com/alexpevzner/hotfix-kvadra-touchpad refers to I²C enabled
touchpads.

> Link: https://bbs.archlinux.org/viewtopic.php?id=302348

...

I'm not against the SPI fix, but is it confirmed that it really fixes the issue?

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-11-03  9:35 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 [this message]
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
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=aQh3RJQ95jTx7VYO@smile.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=broonie@kernel.org \
    --cc=hansg@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