From: Takashi Iwai <tiwai@suse.de>
To: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Cc: alsa-devel@alsa-project.org, Danny Tholen <obiwan@mailmij.org>,
pierre-louis.bossart@linux.intel.com,
ranjani.sridharan@linux.intel.com,
Alex Deucher <alexander.deucher@amd.com>,
Dmitry Osipenko <digetx@gmail.com>,
Thierry Reding <treding@nvidia.com>
Subject: Re: [PATCH] ALSA: hda: avoid write to STATESTS if controller is in reset
Date: Tue, 12 Oct 2021 18:05:14 +0200 [thread overview]
Message-ID: <s5hee8q1b5x.wl-tiwai@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2110121805270.3554566@eliteleevi.tm.intel.com>
On Tue, 12 Oct 2021 17:48:12 +0200,
Kai Vehmanen wrote:
>
> Hi,
>
> On Tue, 12 Oct 2021, Takashi Iwai wrote:
>
> > > The snd_hdac_bus_reset_link() contains logic to clear STATESTS register
> > > before performing controller reset. This code dates back to an old
> > > bugfix in commit e8a7f136f5ed ("[ALSA] hda-intel - Improve HD-audio
> > > codec probing robustness"). Originally the code was added to
> > > azx_reset().
> [...]
> > Do we have a bug reference? I guess it worth to be pushed to 5.15-rc
> > and Cc-to-stable, if this is hitting already on the recent machines.
>
> I unfortunately don't have a public bug reference to share. This will
> impact PCIe based Intel hardware like DG1. The DRM support is quite
> recent for these, so in practise this only affects 5.15-rc and newer.
>
> And even on these, the functionality will be ok, it's just the warnings
> that fill the kernel log that are a problem.
OK, then I'll push this without Cc to stable.
thanks,
Takashi
prev parent reply other threads:[~2021-10-12 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 14:29 [PATCH] ALSA: hda: avoid write to STATESTS if controller is in reset Kai Vehmanen
2021-10-12 15:00 ` Takashi Iwai
2021-10-12 15:48 ` Kai Vehmanen
2021-10-12 16:05 ` 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=s5hee8q1b5x.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alexander.deucher@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=digetx@gmail.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=obiwan@mailmij.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=treding@nvidia.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.