From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Baojun Xu <baojun.xu@ti.com>
Cc: tiwai@suse.de, robh+dt@kernel.org, lgirdwood@gmail.com,
perex@perex.cz, pierre-louis.bossart@linux.intel.com,
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 v5] ALSA: hda/tas2781: Add speaker id check for ASUS projects
Date: Mon, 18 Nov 2024 11:14:14 +0200 [thread overview]
Message-ID: <ZzsFZnWeEAbIjgbN@smile.fi.intel.com> (raw)
In-Reply-To: <20241116075006.11994-1-baojun.xu@ti.com>
On Sat, Nov 16, 2024 at 03:50:06PM +0800, 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.
...
> + // Speaker id was needed for ASUS projects.
> + if (!strncmp(sub, TAS2781_ASUS_ID, strlen(TAS2781_ASUS_ID))) {
Better approach is
ret = sscanf(sub, "%04x%04x", &vid, &did);
if (ret == 2 && vid == ASUS_ID) {
... // matched to ASUS_ID
} else {
... // no match
}
Alternatively it can be
u32 subid;
ret = kstrtou32(sub, 16, &subid);
if (ret || upper_16_bits(subid) != ASUS_ID) {
... // no match (as in previous 'else')
} else {
... // matched to ASUS_ID
}
With it it will be clearer to see what's going on here.
With the above you can get rid of the custom constant and
use PCI_VENDOR_ID_ASUSTEK directly.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-11-18 9:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-16 7:50 [PATCH v5] ALSA: hda/tas2781: Add speaker id check for ASUS projects Baojun Xu
2024-11-16 8:05 ` Christophe JAILLET
2024-11-18 9:14 ` Andy Shevchenko [this message]
2024-11-18 9:14 ` 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=ZzsFZnWeEAbIjgbN@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=13916275206@139.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=pierre-louis.bossart@linux.intel.com \
--cc=robh+dt@kernel.org \
--cc=shenghao-ding@ti.com \
--cc=tiwai@suse.de \
--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