From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
intel-gfx@lists.freedesktop.org, "Kurmi,
Suresh Kumar" <suresh.kumar.kurmi@intel.com>,
intel-xe@lists.freedesktop.org
Subject: Re: [Intel-gfx] [Intel-xe] [PATCH 11/14] ALSA: hda/intel: Move snd_hdac_i915_init to before probe_work.
Date: Tue, 14 Nov 2023 15:39:57 +0200 [thread overview]
Message-ID: <ZVN4rQjLxROOjTE-@intel.com> (raw)
In-Reply-To: <87bkbwsebl.fsf@intel.com>
On Tue, Nov 14, 2023 at 02:35:10PM +0200, Jani Nikula wrote:
> On Tue, 14 Nov 2023, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> > On Mon, Oct 02, 2023 at 09:38:44PM +0200, maarten.lankhorst@linux.intel.com wrote:
> >> From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> >>
> >> Now that we can use -EPROBE_DEFER, it's no longer required to spin off
> >> the snd_hdac_i915_init into a workqueue.
> >>
> >> Use the -EPROBE_DEFER mechanism instead, which must be returned in the
> >> probe function.
> >
> > This completely broke i915 audio!
> >
> > I also can't see any trace of this stuff ever being posted to
> > intel-gfx so it never went through the CI.
> >
> > Please fix or revert ASAP.
>
> Cc: Jani, Suresh
>
> Ville, please file a bug at gitlab so we can track this, thanks.
https://gitlab.freedesktop.org/drm/intel/-/issues/9671
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2023-11-14 13:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231002193847.7134-1-maarten.lankhorst@linux.intel.com>
[not found] ` <20231002193847.7134-11-maarten.lankhorst@linux.intel.com>
2023-11-14 11:06 ` [Intel-gfx] [Intel-xe] [PATCH 11/14] ALSA: hda/intel: Move snd_hdac_i915_init to before probe_work Ville Syrjälä
2023-11-14 12:35 ` Jani Nikula
2023-11-14 13:29 ` Maarten Lankhorst
2023-11-14 13:31 ` Saarinen, Jani
2023-11-14 16:52 ` Takashi Iwai
2023-11-14 17:24 ` Jani Nikula
2023-11-15 8:15 ` Kai Vehmanen
2023-11-14 13:39 ` Ville Syrjälä [this message]
2023-11-14 14:39 ` Maarten Lankhorst
2023-11-14 15:50 ` Takashi Iwai
2023-11-14 15:52 ` Maarten Lankhorst
2023-11-14 15:09 ` Takashi Iwai
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=ZVN4rQjLxROOjTE-@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=suresh.kumar.kurmi@intel.com \
--cc=tiwai@suse.de \
/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