From: Luke Jones <luke@ljones.dev>
To: Stefan Binding <sbinding@opensource.cirrus.com>
Cc: 'Takashi Iwai' <tiwai@suse.de>,
tiwai@suse.com, james.schulman@cirrus.com,
david.rhodes@cirrus.com, rf@opensource.cirrus.com,
linux-kernel@vger.kernel.org,
'Jonathan LoBue' <jlobue10@gmail.com>,
patches@opensource.cirrus.com
Subject: RE: [PATCH] ALSA: hda: cs35l41: Support ASUS 2023 laptops with missing DSD
Date: Thu, 24 Aug 2023 08:31:06 +1200 [thread overview]
Message-ID: <UB2VZR.B7HP6HUMGFA03@ljones.dev> (raw)
In-Reply-To: <000601d9d5b0$8d6817f0$a83847d0$@opensource.cirrus.com>
>
> The second member variable in cs35l41_prop_model_table is the SSID to
> match against.
> The Lenovo laptops in the initial patch didn't have different SSIDs so
> the entry was set to NULL for those.
> Future entries using CSC3551 MUST always have an accompanying SSID
> with this entry.
> Takashi was correct, the implementation is intended to also be used to
> patch incorrect DSD.
>
> We have a potential solution to workaround the SPI cs-gpios issue
> inside here,
> though the drawback for that is that it only works for laptops with 2
> SPI amps.
Can you provide me this so I can test? I have laptops with SPI 2 and 4
speaker setups.
> I also took a look at the function for applying DSD properties for the
> 2023 ROG laptops.
> Unfortunately the one-size-fits-all approach will not work, some of
> these laptops are i2c
> and some are SPI, meaning the GPIO indexes are different for different
> laptops.
Do you mean "spk-id-gpios"? For all the laptops I know of this seems to
be
Package () { "spk-id-gpios", Package () {
SPK1, 0x02, Zero, Zero,
SPK1, 0x02, Zero, Zero
} },
There is one laptop where it is One not 0x02 (the GA402N)
> Some of the laptops do no have Speaker IDs.
> Also, no laptop other than the 2 I added already should ever use
> CS35L41_EXT_BOOST_NO_VSPK_SWITCH (in fact I believe all these laptops
> are internal
> boost anyway).
Grazie.
>
> We are currently working internally on adding support for the 2023 ROG
> laptops, so we
> ask for you guys to hold off on trying to upstream support for these
> laptops.
Ah great. Thank you. I apologise for trying to rush things, but I do
have a discord server of over 4000 people, many of whom have laptops
with cirrus amps.
For now I'm including a patch in my kernel builds with this mapping:
const struct cs35l41_prop_model cs35l41_prop_model_table[] = {
{ "CLSA0100", NULL, lenovo_legion_no_acpi },
{ "CLSA0101", NULL, lenovo_legion_no_acpi },
{ "CSC3551", "10431433", asus_rog_2023_no_acpi }, // ASUS GS650P - i2c
{ "CSC3551", "10431463", asus_rog_2023_no_acpi }, // ASUS GA402X - i2c
{ "CSC3551", "10431473", asus_rog_2023_no_acpi }, // ASUS GU604V - spi
{ "CSC3551", "10431483", asus_rog_2023_no_acpi }, // ASUS GU603V - spi
{ "CSC3551", "10431493", asus_rog_2023_no_acpi }, // ASUS GV601V - spi
{ "CSC3551", "10431573", asus_rog_2023_no_acpi }, // ASUS GZ301V - spi
{ "CSC3551", "104317F3", asus_rog_2023_no_acpi }, // ASUS ROG ALLY -
i2c
{ "CSC3551", "10431B93", asus_rog_2023_no_acpi }, // ASUS G614J - spi
{ "CSC3551", "10431CAF", asus_rog_2023_no_acpi }, // ASUS G634J - spi
{ "CSC3551", "10431C9F", asus_rog_2023_no_acpi }, // ASUS G614JI -spi
{ "CSC3551", "10431D1F", asus_rog_2023_no_acpi }, // ASUS G713P - i2c
{ "CSC3551", "10431F1F", asus_rog_2023_no_acpi }, // ASUS H7604JV - spi
{}
};
These are the machines I have verified the gpios and such for.
Cheers,
Luke.
next prev parent reply other threads:[~2023-08-23 20:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 1:10 [PATCH] ALSA: hda: cs35l41: Support ASUS 2023 laptops with missing DSD Luke D. Jones
2023-08-23 1:18 ` Luke Jones
2023-08-23 6:24 ` Takashi Iwai
2023-08-23 7:28 ` Luke Jones
2023-08-23 7:37 ` Takashi Iwai
2023-08-23 8:02 ` Luke Jones
2023-08-23 8:43 ` Takashi Iwai
2023-08-23 10:57 ` Stefan Binding
2023-08-23 20:31 ` Luke Jones [this message]
2023-08-25 4:48 ` Jonathan LoBue
2023-10-03 14:45 ` Luke Jones
2023-10-03 15:06 ` Stefan Binding
2023-10-08 17:19 ` Huayu Zhang
2023-10-23 7:38 ` Jonathan LoBue
2023-10-23 16:35 ` Jonathan LoBue
2023-10-25 4:25 ` Jonathan LoBue
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=UB2VZR.B7HP6HUMGFA03@ljones.dev \
--to=luke@ljones.dev \
--cc=david.rhodes@cirrus.com \
--cc=james.schulman@cirrus.com \
--cc=jlobue10@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.