From: Takashi Iwai <tiwai@suse.de>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Henrique de Moraes Holschuh <ibm-acpi@hmh.eng.br>,
ibm-acpi-devel@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: ThinkPad T480s & LED_MUTE, LED_MICMUTE
Date: Thu, 21 Jun 2018 13:29:15 +0200 [thread overview]
Message-ID: <s5hzhzojs38.wl-tiwai@suse.de> (raw)
In-Reply-To: <20180621112407.fxwnkdvgtxwifryd@pali>
On Thu, 21 Jun 2018 13:24:07 +0200,
Pali Rohár wrote:
>
> On Tuesday 19 June 2018 10:42:12 Takashi Iwai wrote:
> > On Tue, 19 Jun 2018 10:37:12 +0200,
> > Pali Rohár wrote:
> > > Interesting is this part:
> > >
> > > $ head /proc/asound/card0/codec#0
> > > Codec: Realtek ALC257
> > > Address: 0
> > > AFG Function Id: 0x1 (unsol 1)
> > > Vendor Id: 0x10ec0257
> > > Subsystem Id: 0x17aa2258
> > > Revision Id: 0x100001
> > > No Modem Function Group found
> > > Default PCM:
> > > rates [0x560]: 44100 48000 96000 192000
> > > bits [0xe]: 16 20 24
> > >
> > > It uses vendor id 0x10ec0257 and support for it was added into
> > > snd-hda-codec-realtek in commit f429e7e494 which was introduced in
> > > version v4.15.
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f429e7e494afaded76e62c6f98211a635aa03098
> > >
> > > I applied this patch to Debian's 4.9 kernel and mute & mic mute leds
> > > started working. This one patch was enough.
> > >
> > > Takashi, it is possible to backport this patch into -stable trees?
> >
> > It has already a Cc-to-stable, so it should have been backported.
> > Maybe it wasn't applicable at that time due to lack of other dependent
> > patches...
> >
> > In anyway, feel free to ping Greg for including it to 4.9.x if it
> > works for you now.
>
> I sent email to Greg, but it was eaten by "email-bot of Greg
> Kroah-Hartman's inbox". So I sent another patch email to stable ML.
Better to put '[PATCH 4.9.y]' prefix in the subject to make clear that
it's only for 4.9.y.
Also, the line indicating the upstream commit id is:
commit $ID upstream.
Last but not least, if you resubmit the patch, you must give your own
sign-off, too.
thanks,
Takashi
prev parent reply other threads:[~2018-06-21 11:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 11:10 ThinkPad T480s & LED_MUTE, LED_MICMUTE Pali Rohár
2018-06-15 11:26 ` Pavel Machek
2018-06-15 11:37 ` Pali Rohár
2018-06-15 12:30 ` Henrique de Moraes Holschuh
2018-06-15 19:09 ` Pali Rohár
2018-06-15 23:36 ` Henrique de Moraes Holschuh
2018-06-16 7:33 ` Pavel Machek
2018-06-16 14:12 ` Henrique de Moraes Holschuh
2018-06-16 15:58 ` Pavel Machek
2018-06-18 10:11 ` Pali Rohár
2018-06-21 11:37 ` Pali Rohár
2018-06-15 12:51 ` Takashi Iwai
2018-06-15 19:09 ` Pali Rohár
2018-06-16 7:05 ` Takashi Iwai
2018-06-16 15:43 ` Pali Rohár
2018-06-16 16:02 ` Takashi Iwai
2018-06-18 10:28 ` Pali Rohár
2018-06-18 10:36 ` Takashi Iwai
2018-06-18 11:21 ` Pali Rohár
2018-06-18 11:26 ` Pali Rohár
2018-06-18 15:35 ` Takashi Iwai
2018-06-21 11:30 ` Pali Rohár
2018-06-21 11:35 ` [ibm-acpi-devel] " Damjan Georgievski
2018-06-21 11:39 ` Takashi Iwai
2018-06-23 12:46 ` Damjan Georgievski
2018-06-21 11:40 ` Pali Rohár
2018-06-19 8:37 ` Pali Rohár
2018-06-19 8:42 ` Takashi Iwai
2018-06-21 11:24 ` Pali Rohár
2018-06-21 11:29 ` Takashi Iwai [this message]
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=s5hzhzojs38.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=ibm-acpi@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=platform-driver-x86@vger.kernel.org \
/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