All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Pisoni <mmpisoni@gmail.com>
To: "Арсений Князев" <poseaydone@ya.ru>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	"Luke D. Jones" <luke@ljones.dev>,
	Stefan Binding <sbinding@opensource.cirrus.com>,
	Andy Chi <andy.chi@canonical.com>,
	Shenghao Ding <shenghao-ding@ti.com>,
	Matthew Anderson <ruinairas1992@gmail.com>,
	Luka Guzenko <l.guzenko@web.de>,
	Yuchi Yang <yangyuchi66@gmail.com>,
	Vitaly Rodionov <vitalyr@opensource.cirrus.com>,
	Yang Yingliang <yangyingliang@huawei.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] patch_realtek: Splitting the UX3402 into two separate models.
Date: Sun, 29 Oct 2023 18:26:03 -0500	[thread overview]
Message-ID: <CAJgVWNcgcmFJWeYkSGWBjsd5kqGO7wRgtW3f6dmvcEsAPac+=w@mail.gmail.com> (raw)
In-Reply-To: <282881698597547@mail.yandex.ru>

Okay so how would I go about getting the following line added to the
patch_realtek file?

SND_PCI_QUIRK(0x1043, 0x1f62, "ASUS UX7602ZM",
ALC245_FIXUP_CS35L41_SPI_2)

It works on my machine I own that model I would just like it added as other
models have been so I don't need to continue to patch the kernel module
when it's already been effectively fixed for others.
This thread looked like you all were discussing modifications to that file
for this issue so I thought it might be a good place to start.

Thank you!


On Sun, Oct 29, 2023, 11:42 AM Арсений Князев <poseaydone@ya.ru> wrote:

> The problem with this laptop is that for different models, different
> values are required, so I had to put them in two different titles.
>
> I don't know if this is a problem with your device, but I think it would
> be better to write a more precise model name.
>
> Best wishes,
> Arseniy Knyazev
>
>
> 28.10.2023, 07:37, "pizFunk" <mmpisoni@gmail.com>:
>
>
> How can I get my model number added to the patch_realtek file? It
> suffers the same issue as the UX3402 and the line that needs to be
> added for my model laptop is:
>
> SND_PCI_QUIRK(0x1043, 0x1f62, "ASUS UX7602",
> ALC245_FIXUP_CS35L41_SPI_2)
>
> Since I see you're being more specific here in splitting the model
> numbers, technically my full model number is: "UX7602ZM".
>
> Again, when I patch this locally it works for my model number, but as
> of yet only the other affected ASUS laptop modedls with my issue have
> found their way into the kernel.
>
> Thanks!
>
>
>
> --
>
>

  parent reply	other threads:[~2023-11-03 16:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13  5:33 [PATCH] patch_realtek: Splitting the UX3402 into two separate models poseaydone
2023-09-13  7:46 ` Takashi Iwai
2023-10-28  2:37 ` pizFunk
     [not found]   ` <282881698597547@mail.yandex.ru>
2023-10-29 23:26     ` Matthew Pisoni [this message]
2023-10-30 20:46     ` Matthew Pisoni

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='CAJgVWNcgcmFJWeYkSGWBjsd5kqGO7wRgtW3f6dmvcEsAPac+=w@mail.gmail.com' \
    --to=mmpisoni@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=andy.chi@canonical.com \
    --cc=l.guzenko@web.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke@ljones.dev \
    --cc=perex@perex.cz \
    --cc=poseaydone@ya.ru \
    --cc=ruinairas1992@gmail.com \
    --cc=sbinding@opensource.cirrus.com \
    --cc=shenghao-ding@ti.com \
    --cc=tiwai@suse.com \
    --cc=vitalyr@opensource.cirrus.com \
    --cc=yangyingliang@huawei.com \
    --cc=yangyuchi66@gmail.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 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.