linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: nickel@altlinux.org
Cc: linux-kernel@vger.kernel.org, Oleg Obidin <obidinog@basealt.ru>,
	Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] Revert "ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()"
Date: Fri, 30 Dec 2022 11:00:52 +0100	[thread overview]
Message-ID: <1c8b2b1b-d6bd-91f4-fec5-47ad3619205e@leemhuis.info> (raw)
In-Reply-To: <Y661FSRlfUFeXB26@kroah.com>



On 30.12.22 10:53, Greg KH wrote:
> On Fri, Dec 30, 2022 at 12:30:53PM +0300, nickel@altlinux.org wrote:
>> From: Nikolai Kostrigin <nickel@altlinux.org>
>>
>> This reverts commit c34db0d6b88b1da95e7ab3353e674f4f574cccee.
>>
>> Sudden sound disappearance was reported for some laptops, e.g.
>> Acer Swift 3 SF314-59-78UR 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
>>
>> lspci
>> 0000:00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller (rev 20)
>>         Subsystem: Acer Incorporated [ALI] Device 148c
>>         Flags: bus master, fast devsel, latency 32, IRQ 197, IOMMU group 12
>>         Memory at 601f270000 (64-bit, non-prefetchable) [size=16K]
>>         Memory at 601f000000 (64-bit, non-prefetchable) [size=1M]
>>         Capabilities: [50] Power Management version 3
>>         Capabilities: [80] Vendor Specific Information: Len=14 <?>
>>         Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
>>         Kernel driver in use: sof-audio-pci
>>
>> Bisection revealed the commit being reverted.
>>
>> Reported-by: Oleg Obidin <obidinog@basealt.ru>
>> Link: https://bugzilla.altlinux.org/44690
>> Link: https://bugzilla.kernel.org/show_bug.cgi?id=216861
>> Signed-off-by: Nikolai Kostrigin <nickel@altlinux.org>
>> ---
>>  sound/soc/soc-pcm.c | 5 +++++
>>  1 file changed, 5 insertions(+)
> 
> <formletter>
> 
> This is not the correct way to submit patches for inclusion in the
> stable kernel tree.  Please read:
>     https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> for how to do this properly.
> 
> </formletter>

Also FWIW & FYI: I earlier today brought the regression in question to
the attention of the people that are responsible to fix this issue:
https://lore.kernel.org/all/bebd692d-7d21-6648-6b7a-c91063bb51c2@leemhuis.info/

With a bit of luck they will soon look into this and fix it, but given
the time of year it might take a day or two longer than usual...

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.

      reply	other threads:[~2022-12-30 10:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-30  9:30 [PATCH 0/1] Revert patch to fix sound sudden dissapearance nickel
2022-12-30  9:30 ` [PATCH] Revert "ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()" nickel
2022-12-30  9:53   ` Greg KH
2022-12-30 10:00     ` Thorsten Leemhuis [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=1c8b2b1b-d6bd-91f4-fec5-47ad3619205e@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickel@altlinux.org \
    --cc=obidinog@basealt.ru \
    /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;
as well as URLs for NNTP newsgroup(s).