Linux Sound subsystem development
 help / color / mirror / Atom feed
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, 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,
	stuart.a.hayhurst@gmail.com
Subject: Re: [PATCH v1] ALSA: hda/tas2781: Ignore SUBSYS_ID not found for tas2563 projects
Date: Mon, 13 Jan 2025 10:37:52 +0200	[thread overview]
Message-ID: <Z4TQ4MAjFwVOjWtt@smile.fi.intel.com> (raw)
In-Reply-To: <20241230064910.1583-1-baojun.xu@ti.com>

On Mon, Dec 30, 2024 at 02:49:10PM +0800, Baojun Xu wrote:
> Driver will return error if no SUBSYS_ID found in BIOS(acpi).
> It will cause error in tas2563 projects, which have no SUBSYS_ID.

...

> +		/* No subsys id in older tas2563 projects. */
> +		if (!strncmp(hid, "INT8866", sizeof("INT8866")))
> +			goto end_2563;

Is this ID was used on old platforms?

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2025-01-13  8:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-30  6:49 [PATCH v1] ALSA: hda/tas2781: Ignore SUBSYS_ID not found for tas2563 projects Baojun Xu
2024-12-30 10:40 ` Takashi Iwai
2025-01-13  8:37 ` Andy Shevchenko [this message]
2025-01-13  8:45   ` [EXTERNAL] " Xu, Baojun
  -- strict thread matches above, loose matches on Subject: below --
2025-01-11  9:57 Baojun Xu
2025-01-12  8:26 ` Takashi Iwai
2025-01-13  5:33   ` Dan Carpenter

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=Z4TQ4MAjFwVOjWtt@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=robh+dt@kernel.org \
    --cc=shenghao-ding@ti.com \
    --cc=stuart.a.hayhurst@gmail.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