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
Subject: Re: [PATCH v3] ALSA: hda/tas2781: Add speaker id check for ASUS projects
Date: Mon, 28 Oct 2024 11:42:04 +0200 [thread overview]
Message-ID: <Zx9cbCq5jl3tOJAk@smile.fi.intel.com> (raw)
In-Reply-To: <20241027143935.1340-1-baojun.xu@ti.com>
On Sun, Oct 27, 2024 at 10:39:35PM +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 (!strncasecmp(sub, TAS2781_ASUS_ID, sizeof(TAS2781_ASUS_ID))) {
Why "case"? Just use strcmp() since the second one is constant and you use it's
length.
> + devm_acpi_dev_add_driver_gpios(p->dev,
> + tas2781_speaker_id_gpios);
I don't know why you completely removed the check, I would leave a debug
message on the error path to give a clue to the user if it fails here.
See how other driver do with this.
Something like
ret = devm_acpi_dev_add_driver_gpios(p->dev, tas2781_speaker_id_gpios);
if (ret)
dev_dbg(...);
> + p->speaker_id = devm_gpiod_get(p->dev, "speakerid", GPIOD_IN);
> + if (IS_ERR(p->speaker_id)) {
> + dev_err(p->dev, "Failed to get Speaker id.\n");
Wrong value in ret, right?
> + goto err;
> + }
> + } else {
> + p->speaker_id = NULL;
> + }
>
> acpi_dev_free_resource_list(&resources);
> strscpy(p->dev_name, hid, sizeof(p->dev_name));
> + put_device(physdev);
> acpi_dev_put(adev);
>
> return 0;
>
> err:
> dev_err(p->dev, "read acpi error, ret: %d\n", ret);
> + put_device(physdev);
> acpi_dev_put(adev);
>
> return ret;
...
> + if (tas_priv->speaker_id != NULL) {
> + // Speaker id need to be checked for ASUS only.
> + spk_id = gpiod_get_value(tas_priv->speaker_id);
> + if (spk_id < 0) {
> + // Speaker id is not valid, use default.
> + dev_dbg(tas_priv->dev, "Wrong spk_id = %d\n", spk_id);
> + spk_id = 0;
> + }
> + snprintf(tas_priv->coef_binaryname,
> + sizeof(tas_priv->coef_binaryname),
> + "TAS2XXX%04X%01d.bin",
%01d makes a little sense. Just use %d.
> + lower_16_bits(codec->core.subsystem_id),
> + spk_id);
> + } else {
> + snprintf(tas_priv->coef_binaryname,
> + sizeof(tas_priv->coef_binaryname),
> + "TAS2XXX%04X.bin",
> + lower_16_bits(codec->core.subsystem_id));
> + }
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-10-28 9:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-27 14:39 [PATCH v3] ALSA: hda/tas2781: Add speaker id check for ASUS projects Baojun Xu
2024-10-28 9:42 ` 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=Zx9cbCq5jl3tOJAk@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=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