From: Luke Jones <luke@ljones.dev>
To: Takashi Iwai <tiwai@suse.de>
Cc: tiwai@suse.com, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org, perex@perex.cz
Subject: Re: [PATCH v2 0/3] sound: realtek: add quirks for ASUS G513, G533Z, GA503R
Date: Fri, 16 Sep 2022 20:46:52 +1200 [thread overview]
Message-ID: <850ba9d69e23be788f1963f46c348f7fdf8806cd.camel@ljones.dev> (raw)
In-Reply-To: <87fsgsvdfq.wl-tiwai@suse.de>
Thanks Takashi,
On Thu, 2022-09-15 at 17:56 +0200, Takashi Iwai wrote:
> On Thu, 15 Sep 2022 10:09:18 +0200,
> Luke D. Jones wrote:
> >
> > This series adds quirks to fix pincfg for the ASUS ROG G513 and
> > G533Z laptops, and adds a mapping
> > for the ASUS ROG GA503R to use the previous G15/G14 quirks which
> > fix the DAC mapping.
> >
> > Changelog:
> > V2:
> > - Use smallcaps in hex string
> > - Chain the G533Z quirk with the G513 quirk as they use the same
> > base pincfg
> > - Add the quirk for GA503R series to use GA401 quirk
> >
> > Luke D. Jones (3):
> > sound: realtek: Add pincfg for ASUS G513 HP jack
> > sound: realtek: Add pincfg for ASUS G533Z HP jack
> > sound: realtek: Add quirk for ASUS GA503R laptop
>
> Now applied all patches, but I corrected the positions of the new
> entries to be in the SSID order locally. Also, the subject lines are
> adjusted to "ALSA:" prefix.
>
I'll try to remember this next time. There's bound to be a few more
with next generation of these laptops.
>
> thanks,
>
> Takashi
next prev parent reply other threads:[~2022-09-16 8:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 8:09 Luke D. Jones
2022-09-15 8:09 ` [PATCH v2 1/3] sound: realtek: Add pincfg for ASUS G513 HP jack Luke D. Jones
2022-09-15 8:09 ` [PATCH v2 2/3] sound: realtek: Add pincfg for ASUS G533Z " Luke D. Jones
2022-09-15 8:09 ` [PATCH v2 3/3] sound: realtek: Add quirk for ASUS GA503R laptop Luke D. Jones
2022-09-15 15:56 ` [PATCH v2 0/3] sound: realtek: add quirks for ASUS G513, G533Z, GA503R Takashi Iwai
2022-09-16 8:46 ` Luke Jones [this message]
2022-09-18 22:18 ` Luke Jones
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=850ba9d69e23be788f1963f46c348f7fdf8806cd.camel@ljones.dev \
--to=luke@ljones.dev \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--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®