alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Jason Montleon <jmontleo@redhat.com>,
	stable@vger.kernel.org,
	Linux regressions mailing list <regressions@lists.linux.dev>,
	Mark Brown <broonie@kernel.org>,
	Alsa-devel <alsa-devel@alsa-project.org>,
	Takashi Iwai <tiwai@suse.com>,
	Bard Liao <yung-chuan.liao@linux.intel.com>
Subject: Re: [REGRESSION] kbl-r5514-5663-max hdmi no longer working
Date: Thu, 23 Mar 2023 13:39:33 +0100	[thread overview]
Message-ID: <61065a7f-19ce-0308-57ed-4cd4c4d681a0@leemhuis.info> (raw)
In-Reply-To: <f96431ee-abc0-ff76-3963-c45d3b092840@leemhuis.info>

On 13.03.23 18:32, Linux regression tracking (Thorsten Leemhuis) wrote:
> [adding a push of people and lists to the recipients that dealt with the
> culprit; leaving the stable list in CC for now, even if this is a
> mainline issue (apart from the backport of the culprit to 5.10.y Takashi
> asked for a while ago)]
> 
> On 13.03.23 17:34, Jason Montleon wrote:
>> It looks like HDMI audio stopped working in 5.17-rc1. I ran a bisect
>> which points to 636110411ca726f19ef8e87b0be51bb9a4cdef06.
> 
> FWIW, that's "ASoC: Intel/SOF: use set_stream() instead of
> set_tdm_slots() for HDAudio" from Pierre-Louis Bossart.

Pierre-Louis Bossart, did you find time to look into this?

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.

#regzbot poke

>> I built
>> 5.17.14 with it reverted and it restored HDMI output, but it doesn't
>> revert cleanly from 5.18 onward.
>>
>> >From what I can tell it looks like -ENOTSUPP is returned from
>> snd_soc_dai_set_stream for hdmi1 and hdmi2 now. I'm not sure if that's
>> expected, but I made the following change and I have working HDMI
>> audio now. https://gist.github.com/jmontleon/4780154c309f956d97ca9a304a00da3f
> 
> Thanks for the report and the patch. I CCed the relevant people for this.
> 
> [TLDR For the rest of the mail: : I'm adding this report to the list of
> tracked Linux kernel regressions; the text you find below is based on a
> few templates paragraphs you might have encountered already in similar
> form. See link in footer if these mails annoy you.]
> 
> To be sure the issue doesn't fall through the cracks unnoticed, I'm
> adding it to regzbot, the Linux kernel regression tracking bot:
> 
> #regzbot ^introduced 636110411ca726f19ef8e87b0be51bb9a4cdef06
> #regzbot title alsa/asoc: kbl-r5514-5663-max hdmi stopped working
> #regzbot ignore-activity
> 
> This isn't a regression? This issue or a fix for it are already
> discussed somewhere else? It was fixed already? You want to clarify when
> the regression started to happen? Or point out I got the title or
> something else totally wrong? Then just reply and tell me -- ideally
> while also telling regzbot about it, as explained by the page listed in
> the footer of this mail.
> 
> Developers: When fixing the issue, remember to add 'Link:' tags pointing
> to the report (the parent of this mail). See page linked in footer for
> details.
> 
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> --
> Everything you wanna know about Linux kernel regression tracking:
> https://linux-regtracking.leemhuis.info/about/#tldr
> That page also explains what to do if mails like this annoy you.

      reply	other threads:[~2023-03-23 12:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJD_bPKQdtaExvVEKxhQ47G-ZXDA=k+gzhMJRHLBe=mysPnuKA@mail.gmail.com>
2023-03-13 17:32 ` [REGRESSION] kbl-r5514-5663-max hdmi no longer working Linux regression tracking (Thorsten Leemhuis)
2023-03-23 12:39   ` 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=61065a7f-19ce-0308-57ed-4cd4c4d681a0@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=jmontleo@redhat.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=tiwai@suse.com \
    --cc=yung-chuan.liao@linux.intel.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 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).