From: Takashi Iwai <tiwai@suse.de>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: alsa-devel@alsa-project.org,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Subject: Re: [PATCH 1/3] ALSA: hda - Handle error from snd_hda_power_up*()
Date: Wed, 27 Jun 2018 18:09:35 +0200 [thread overview]
Message-ID: <s5ho9fw2ou8.wl-tiwai@suse.de> (raw)
In-Reply-To: <153011487107.8693.7624551348316365861@mail.alporthouse.com>
On Wed, 27 Jun 2018 17:54:31 +0200,
Chris Wilson wrote:
>
> Quoting Takashi Iwai (2018-06-27 10:10:32)
> > Although snd_hda_power_up() and snd_hda_power_up_pm() may fail, we
> > haven't dealt with the error properly in many places. It's an unusual
> > situation but still possible.
> >
> > This patch spots these places and adds the proper error paths.
> >
> > Signed-off-by: Takashi Iwai <tiwai@suse.de>
>
> Verdict from CI,
>
> https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_2430/issues.html
>
> is that this one causes a bunch of pm fallout.
>
> Do you mind doing a quick revert? Or working with our CI to find the bad
> chunk?
Hrm, it doesn't look good -- I revert the branch merge now.
Thanks for the quick heads up.
Takashi
>
> On a second look,
>
> > @@ -7310,7 +7339,8 @@ static void ca0132_free(struct hda_codec *codec)
> > struct ca0132_spec *spec = codec->spec;
> >
> > cancel_delayed_work_sync(&spec->unsol_hp_work);
> > - snd_hda_power_up(codec);
> > + if (snd_hda_power_up(codec) < 0)
> > + goto skip_shutdown;
> > switch (spec->quirk) {
> > case QUIRK_SBZ:
> > sbz_exit_chip(codec);
> > @@ -7326,6 +7356,7 @@ static void ca0132_free(struct hda_codec *codec)
> > break;
> > }
> > snd_hda_power_down(codec);
> > + skip_shutdown:
> > if (spec->mem_base)
> > iounmap(spec->mem_base);
> > kfree(spec->spec_init_verbs);
>
> would seem to be the only chunk more complicated than the rest.
> -Chris
>
next prev parent reply other threads:[~2018-06-27 16:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 9:10 [PATCH 0/3] ALSA: PM-related fixes/cleanups Takashi Iwai
2018-06-27 9:10 ` [PATCH 1/3] ALSA: hda - Handle error from snd_hda_power_up*() Takashi Iwai
2018-06-27 9:36 ` Chris Wilson
2018-06-27 9:50 ` Takashi Iwai
2018-06-27 15:54 ` Chris Wilson
2018-06-27 16:09 ` Takashi Iwai [this message]
2018-06-27 21:48 ` Takashi Iwai
2018-06-27 16:12 ` Ville Syrjälä
2018-06-27 21:49 ` Takashi Iwai
2018-06-28 9:02 ` [alsa-devel] " Dan Carpenter
2018-06-27 9:10 ` [PATCH 2/3] ALSA: hda - Move in_pm accessors to HDA core Takashi Iwai
2018-06-27 9:38 ` Chris Wilson
2018-06-27 22:05 ` Takashi Iwai
2018-06-27 9:10 ` [PATCH 3/3] ALSA: hda/hdmi - Don't fall back to generic when i915 binding fails Takashi Iwai
2018-06-27 13:57 ` [PATCH 0/3] ALSA: PM-related fixes/cleanups Chris Wilson
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=s5ho9fw2ou8.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=chris@chris-wilson.co.uk \
--cc=ville.syrjala@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