From: Takashi Iwai <tiwai@suse.de>
To: Baojun Xu <baojun.xu@ti.com>
Cc: <tiwai@suse.de>, <robh+dt@kernel.org>,
<andriy.shevchenko@linux.intel.com>, <lgirdwood@gmail.com>,
<perex@perex.cz>, <shenghao-ding@ti.com>, <navada@ti.com>,
<13916275206@139.com>, <v-hampiholi@ti.com>, <v-po@ti.com>,
<linux-sound@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<liam.r.girdwood@intel.com>, <yung-chuan.liao@linux.intel.com>,
<broonie@kernel.org>, <antheas.dk@gmail.com>, <philm@manjaro.org>
Subject: Re: [PATCH v6] ALSA: hda/tas2781: Add speaker id check for ASUS projects
Date: Tue, 26 Nov 2024 08:55:54 +0100 [thread overview]
Message-ID: <87v7wajunp.wl-tiwai@suse.de> (raw)
In-Reply-To: <20241123073718.475-1-baojun.xu@ti.com>
On Sat, 23 Nov 2024 08:37:18 +0100,
Baojun Xu wrote:
>
> Add speaker id check by gpio in ACPI for ASUS projects.
> In other vendors, speaker id was checked by BIOS, and was applied in
> last bit of subsys id, so we can load corresponding firmware binary file
> for its speaker by subsys id.
> But in ASUS project, the firmware binary name will be appended an extra
> number to tell the speakers from different vendors. And this single digit
> come from gpio level of speaker id in BIOS.
>
> Signed-off-by: Baojun Xu <baojun.xu@ti.com>
I applied this now, as it's been cooked for long time and we don't
want miss 6.12 merge. If any issue is found, let's fix on the top.
thanks,
Takashi
next prev parent reply other threads:[~2024-11-26 7:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-23 7:37 [PATCH v6] ALSA: hda/tas2781: Add speaker id check for ASUS projects Baojun Xu
2024-11-26 7:55 ` Takashi Iwai [this message]
2024-12-23 22:54 ` Stuart Hayhurst
2024-12-30 11:08 ` Takashi Iwai
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=87v7wajunp.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=13916275206@139.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=antheas.dk@gmail.com \
--cc=baojun.xu@ti.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=navada@ti.com \
--cc=perex@perex.cz \
--cc=philm@manjaro.org \
--cc=robh+dt@kernel.org \
--cc=shenghao-ding@ti.com \
--cc=v-hampiholi@ti.com \
--cc=v-po@ti.com \
--cc=yung-chuan.liao@linux.intel.com \
/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