From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Baojun Xu <baojun.xu@ti.com>
Cc: tiwai@suse.de, hansg@kernel.org, ilpo.jarvinen@linux.intel.com,
broonie@kernel.org, alsa-devel@alsa-project.org,
shenghao-ding@ti.com, 13916275206@139.com,
platform-driver-x86@vger.kernel.org, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org, letitia.tsai@hp.com
Subject: Re: [PATCH v3 0/1] platform/x86: serial-multi-instantiate: ACPI example code
Date: Wed, 26 Nov 2025 13:43:35 +0200 [thread overview]
Message-ID: <aSbn52j-CJp9gHzM@smile.fi.intel.com> (raw)
In-Reply-To: <20251126081741.10588-1-baojun.xu@ti.com>
On Wed, Nov 26, 2025 at 04:17:40PM +0800, Baojun Xu wrote:
> The tas2781-hda supports multi-projects, In some projects,
> GpioInt was dropped due to no IRQ connection.
GpioInt()
> See the example code below:
>
> But in smi_i2c_probe(), smi_spi_probe() (serial-multi-instantiate.c),
> if looking for IRQ by smi_get_irq() fails, it will return an error,
> will not add new device, and cause smi_probe to fail.
smi_probe()
> So need to add an exception case for these situations.
> BTW, this patch will take effect on both I2C and SPI devices.
>
> Device (SPKR)
> {
> Name (_ADR, One)
> Name (_HID, "TXNW2781")
> Method (_CRS, 0, NotSerialized)
> {
> Name (RBUF, ResourceTemplate ()
> {
> I2cSerialBusV2 (0x0038, ...)
> I2cSerialBusV2 (0x0039, ...)
> // GpioInt (Edge, ...) { 0x0000 }
> //"GpioInt (...) {}" was commented out due to no IRQ connection.
> })
> Return (RBUF)
> }
> }
And as Hans said, please fold this into the patch as part of the commit message.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2025-11-26 11:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 8:17 [PATCH v3 0/1] platform/x86: serial-multi-instantiate: ACPI example code Baojun Xu
2025-11-26 8:17 ` [PATCH v3 1/1] platform/x86: serial-multi-instantiate: Add IRQ_RESOURCE_OPT for IRQ missing projects Baojun Xu
2025-11-26 9:05 ` [PATCH v3 0/1] platform/x86: serial-multi-instantiate: ACPI example code Hans de Goede
2025-11-26 11:43 ` Andy Shevchenko [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=aSbn52j-CJp9gHzM@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=13916275206@139.com \
--cc=alsa-devel@alsa-project.org \
--cc=baojun.xu@ti.com \
--cc=broonie@kernel.org \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=letitia.tsai@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=shenghao-ding@ti.com \
--cc=tiwai@suse.de \
/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