mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jean-Loïc Charroud" <lagiraudiere+linux@free.fr>
To: Takashi Iwai <tiwai@suse.de>
Cc: Stefan Binding <sbinding@opensource.cirrus.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Richard Fitzgerald <rf@opensource.cirrus.com>,
	linux-sound <linux-sound@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	patches <patches@opensource.cirrus.com>
Subject: Re: [PATCH v2] ALSA: hda/realtek: cs35l41: Fix internal speaker support for ASUS UM3402 with missing DSD
Date: Wed, 7 Feb 2024 18:48:13 +0100	[thread overview]
Message-ID: <4879c094-5fdc-4fe4-a7ba-21168d7b2afe@free.fr> (raw)
In-Reply-To: <87jzng5mzv.wl-tiwai@suse.de>

Le 07/02/2024 à 16:10, Takashi Iwai a écrit :
> Jean-Loïc Charroud wrote:
>> Fix device ID for "ASUS UM3402" and "ASUS UM6702RA/RC".
> This change is only about the string in the table, not the actual
> behavior, right?

Well, not sure it doesn't matter.
Before the device ID were swapped, my syslog reported :
     cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Error: ACPI _DSD
     Properties are missing for HID CSC3551.
And then, after the patch 51d976079976c800ef19ed1b542602fcf63f0edb, it
reports :
     cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Failed property
     cirrus,dev-index: -22
So, as it looks like a regression, it makes me think that the model name
may be checked along the device ID...

> The name string there is only for debug info, so
> it's no big problem even if it's not 100% right.
> That is, this can be again split to another patch -- with the
> additional Fixes tag to the commit that introduced the entries.
> 
>> Add DSD values for "ASUS UM3402" to cs35l41_config_table[].
> ... and this one is the mandatory fix for your device.  It should be
> the patch 1.  Then we'll have two more, one for correcting the entry
> names, and another for sorting the entries.
I already submitted that last one
> 
> I'm a bit picky, but now you see how the things work.
> Divide-and-conquer is the basic strategy.
Yes, but not smooth, as I have to workaround my broken mailer...

regards
Loïc

  parent reply	other threads:[~2024-02-07 17:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06 17:05 Jean-Loïc Charroud
2024-02-07 13:42 ` Takashi Iwai
2024-02-07 14:30   ` Jean-Loïc Charroud
2024-02-07 15:10     ` Takashi Iwai
2024-02-07 16:45       ` Jean-Loïc Charroud
2024-02-07 16:51       ` [PATCH] ALSA: hda/realtek: cs35l41: Fix device ID / model name Jean-Loïc Charroud
2024-02-07 17:10         ` Takashi Iwai
2024-02-07 18:05           ` Jean-Loïc Charroud
2024-02-07 17:48       ` Jean-Loïc Charroud [this message]
2024-02-07 18:13         ` [PATCH v2] ALSA: hda/realtek: cs35l41: Fix internal speaker support for ASUS UM3402 with missing DSD 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=4879c094-5fdc-4fe4-a7ba-21168d7b2afe@free.fr \
    --to=lagiraudiere+linux@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=perex@perex.cz \
    --cc=rf@opensource.cirrus.com \
    --cc=sbinding@opensource.cirrus.com \
    --cc=tiwai@suse.com \
    --cc=tiwai@suse.de \
    /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

all inboxes | Powered by JetHome®