From: Antti Laakso <antti.laakso@linux.intel.com>
To: Junjie Cao <junjie.cao@intel.com>
Cc: Miguel Vadillo <miguel.vadillo@intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Kate Hsuan <hpa@redhat.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] media: i2c: cvs: Get the wake IRQ without claiming the GPIO
Date: Wed, 16 Sep 2026 12:34:52 +0300 [thread overview]
Message-ID: <aqpivLIxfxcZSj30@alaakso-desk> (raw)
In-Reply-To: <20260908105717.496232-1-junjie.cao@intel.com>
On Tue, Sep 08, 2026 at 06:57:17PM +0800, Junjie Cao wrote:
> The wake line is only used as an IRQ source, yet the driver requests
> it with devm_gpiod_get() before the I2C handshake. Where ipu-bridge
> does not expose the CSI endpoints, CSI init returns -EPROBE_DEFER and
> every retry claims the line again for the length of the handshake.
>
> On the Dell XPS 14 DA14260 (Panther Lake) the four CS35L57 amplifiers
> read their speaker ID from one GpioIo (DSDT decoded in the second
> link):
>
> GpioIo (Shared, PullNone, 0, 0, IoRestrictionInputOnly,
> "\_SB.GPI1", 0, ResourceConsumer,,) {20}
>
> A request that lands while another consumer holds the line fails, and
> cs35l56 does not retry:
>
> cs35l56 sdw:0:2:01fa:3557:01:2: error -EBUSY: Failed to get spk-id-gpios
>
> All four fail on Fedora 7.1.13, the first Fedora 7.1 kernel with the
> driver enabled; the same board on 7.1.12 without it creates the card.
> The second link shows the same failure on openSUSE 7.2.2, whose
> config also enables the driver.
>
> The INTC10E1 _CRS of this machine has not been decoded. The vendor
> driver in intel/vision-drivers requests req, resp and rst the same
> way but maps wake to an IRQ with acpi_dev_gpio_irq_get_by() without
> requesting it, and on another DA14260 (board 0VRKYR, BIOS 1.8.2) a
> build of it is bound while the amplifiers probe. The wake entry is
> the line that differs.
>
> Take the IRQ from the GpioInt entry the same way, as the I2C core
> does for client->irq; this also applies the trigger type from _CRS.
> The driver binds as a platform device too, hence the explicit lookup.
>
> Fixes: 8e2b43d2c10b ("media: i2c: cvs: Add driver of Intel Computer Vision Sensing Controller(CVS)")
> Cc: stable@vger.kernel.org
> Link: https://bugzilla.redhat.com/show_bug.cgi?id=2529031
> Link: https://github.com/thesofproject/sof/issues/11152
> Signed-off-by: Junjie Cao <junjie.cao@intel.com>
> ---
Tested-by: Antti Laakso <antti.laakso@linux.intel.com>
> drivers/media/i2c/cvs/core.c | 16 ++++++----------
> 1 file changed, 6 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/media/i2c/cvs/core.c b/drivers/media/i2c/cvs/core.c
> index d4a3b9c3bab1e..8d857bbd8ab51 100644
> --- a/drivers/media/i2c/cvs/core.c
> +++ b/drivers/media/i2c/cvs/core.c
> @@ -725,8 +725,6 @@ static int cvs_core_probe(struct device *dev, struct i2c_client *i2c)
> }
>
> if (ctx->res == ICVS_FULLCAP) {
> - struct gpio_desc *wake;
> -
> ctx->rst = devm_gpiod_get(dev, "rst", GPIOD_OUT_HIGH);
> if (IS_ERR(ctx->rst)) {
> ret = dev_err_probe(dev, PTR_ERR(ctx->rst),
> @@ -734,14 +732,12 @@ static int cvs_core_probe(struct device *dev, struct i2c_client *i2c)
> goto err_put_ipu;
> }
>
> - wake = devm_gpiod_get(dev, "wake", GPIOD_IN);
> - if (IS_ERR(wake)) {
> - ret = dev_err_probe(dev, PTR_ERR(wake),
> - "failed to get wake GPIO\n");
> - goto err_put_ipu;
> - }
> -
> - ctx->irq = gpiod_to_irq(wake);
> + /*
> + * Do not request the line: another device's _CRS may list
> + * the same pin, and its driver would then fail with -EBUSY.
> + */
> + ctx->irq = acpi_dev_gpio_irq_get_by(ACPI_COMPANION(dev),
> + "wake", 0);
> if (ctx->irq < 0) {
> ret = dev_err_probe(dev, ctx->irq,
> "failed to get wake IRQ\n");
> --
> 2.43.0
>
>
prev parent reply other threads:[~2026-09-16 9:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 10:57 Junjie Cao
2026-09-14 7:50 ` Manuel Knitza
2026-09-14 9:34 ` Junjie Cao
2026-09-14 9:13 ` Manuel Knitza
2026-09-16 9:34 ` Antti Laakso [this message]
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=aqpivLIxfxcZSj30@alaakso-desk \
--to=antti.laakso@linux.intel.com \
--cc=hpa@redhat.com \
--cc=junjie.cao@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=miguel.vadillo@intel.com \
--cc=sakari.ailus@linux.intel.com \
--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
all inboxes | Powered by JetHome®