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 v2] ALSA: hda/tas2781: Add speaker id check for ASUS projects
Date: Fri, 18 Oct 2024 15:31:05 +0300 [thread overview]
Message-ID: <ZxJVCb13lQ4h2KRD@smile.fi.intel.com> (raw)
In-Reply-To: <20241018071118.3298-1-baojun.xu@ti.com>
On Fri, Oct 18, 2024 at 03:11:18PM +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.
...
> + sub = acpi_get_subsystem_id(ACPI_HANDLE(physdev));
> + if (IS_ERR(sub)) {
> + dev_err(p->dev, "Failed to get SUBSYS ID.\n");
> + goto err;
> + }
> + // Speaker id was needed for ASUS projects.
> + if (strstr(sub, TAS2781_ASUS_ID)) {
strstr() is wrong. You can get 1043 in the middle of the bigger number,
or even text.
> + ret = devm_acpi_dev_add_driver_gpios(p->dev,
> + tas2781_speaker_id_gpios);
> + if (ret) {
> + dev_err(p->dev, "Unable to add GPIO.\n");
> + goto err;
No need. If this fails, the below most likely fail as well.
> + }
> + 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");
> + goto err;
> + }
> + } else {
> + p->speaker_id = NULL;
> + }
...
> + 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 || spk_id > 1) {
When "> 1" is possible? Isn't it a dead code?
> + // Speaker id is not valid, use default.
> + dev_dbg(tas_priv->dev, "Wrong spk_id = %d\n", spk_id);
> + spk_id = 0;
> + }
> + scnprintf(tas_priv->coef_binaryname,
Why 'c' variant? You do not check the return value anyway. So, what's the point?
> + sizeof(tas_priv->coef_binaryname),
> + "TAS2XXX%04X%01d.bin",
> + lower_16_bits(codec->core.subsystem_id),
> + spk_id);
> + } else {
> + scnprintf(tas_priv->coef_binaryname,
Ditto.
> + sizeof(tas_priv->coef_binaryname),
> + "TAS2XXX%04X.bin",
> + lower_16_bits(codec->core.subsystem_id));
> + }
...
> @@ -793,7 +844,6 @@ static int tas2781_hda_i2c_probe(struct i2c_client *clt)
> const char *device_name;
> int ret;
>
> -
> tas_hda = devm_kzalloc(&clt->dev, sizeof(*tas_hda), GFP_KERNEL);
> if (!tas_hda)
> return -ENOMEM;
Stray change.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-10-18 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 7:11 [PATCH v2] ALSA: hda/tas2781: Add speaker id check for ASUS projects Baojun Xu
2024-10-18 12:31 ` Andy Shevchenko [this message]
2024-10-21 7:19 ` Takashi Iwai
2024-10-21 8:19 ` 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=ZxJVCb13lQ4h2KRD@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