From: Daniel Vetter <daniel@ffwll.ch>
To: Takashi Iwai <tiwai@suse.de>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 1/3] drm/i915/hda: Add audio component stub
Date: Tue, 17 May 2016 15:59:17 +0200 [thread overview]
Message-ID: <20160517135916.GP27098@phenom.ffwll.local> (raw)
In-Reply-To: <s5hshxgu6r9.wl-tiwai@suse.de>
On Tue, May 17, 2016 at 03:57:30PM +0200, Takashi Iwai wrote:
> On Tue, 17 May 2016 14:53:40 +0200,
> Takashi Iwai wrote:
> >
> > On Tue, 17 May 2016 14:39:26 +0200,
> > Daniel Vetter wrote:
> > >
> > > And if we _really_ want this to work at runtime too, then we need a
> > > system-wide nomodeset option that snd-hda can look up and act accordingly.
> >
> > Yes, this would be one option.
>
> And I noticed that this can be easily added to patch 3, just like i915
> driver does:
>
> diff --git a/sound/hda/hdac_i915.c b/sound/hda/hdac_i915.c
> index c9af022676c2..c48a014be7b4 100644
> --- a/sound/hda/hdac_i915.c
> +++ b/sound/hda/hdac_i915.c
> @@ -361,6 +361,11 @@ int snd_hdac_i915_init(struct hdac_bus *bus)
> if (WARN_ON(hdac_acomp))
> return -EBUSY;
>
> +#ifdef CONFIG_VGA_CONSOLE
> + if (vgacon_text_force())
> + return -ENODEV;
> +#endif
There's a dummy vgacon_text_force now, so you don't even need the #ifdef.
-Daniel
> +
> if (!i915_gfx_present())
> return -ENODEV;
>
>
> It's hackish, but should work practically enough...
>
>
> Takashi
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-05-17 14:11 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 10:57 [PATCH 0/3] More robust i915 / audio binding Takashi Iwai
2016-04-07 10:57 ` [PATCH 1/3] drm/i915/hda: Add audio component stub Takashi Iwai
2016-04-07 11:55 ` Ville Syrjälä
2016-04-07 12:30 ` Imre Deak
2016-04-25 12:46 ` Takashi Iwai
2016-05-12 18:06 ` [PATCH v2 " Imre Deak
2016-05-13 7:48 ` Takashi Iwai
2016-05-13 9:50 ` Imre Deak
2016-05-13 10:04 ` Takashi Iwai
2016-05-13 10:44 ` Imre Deak
2016-05-17 7:20 ` Daniel Vetter
2016-05-17 7:37 ` Takashi Iwai
2016-05-17 9:42 ` Daniel Vetter
2016-05-17 9:59 ` Takashi Iwai
2016-05-17 10:22 ` Imre Deak
2016-05-17 11:10 ` Daniel Vetter
2016-05-17 12:11 ` Imre Deak
2016-05-17 12:34 ` Daniel Vetter
2016-05-17 12:37 ` Daniel Vetter
2016-05-17 12:39 ` Daniel Vetter
2016-05-17 12:53 ` Takashi Iwai
2016-05-17 13:57 ` Takashi Iwai
2016-05-17 13:59 ` Daniel Vetter [this message]
2016-05-17 15:03 ` Takashi Iwai
2016-05-17 12:51 ` Takashi Iwai
2016-05-17 12:47 ` Takashi Iwai
2016-05-17 12:56 ` Daniel Vetter
2016-05-17 13:20 ` Takashi Iwai
2016-05-17 16:18 ` Daniel Vetter
2016-05-17 16:23 ` Daniel Vetter
2016-05-17 18:19 ` Takashi Iwai
2016-05-17 21:11 ` Daniel Vetter
2016-05-18 9:06 ` Takashi Iwai
2016-05-17 17:24 ` Takashi Iwai
2016-05-17 9:10 ` Imre Deak
2016-04-07 10:57 ` [PATCH 2/3] ALSA: hda - Immediately fail if the i915 audio component is disabled Takashi Iwai
2016-04-07 10:57 ` [PATCH 3/3] ALSA: hda - Support deferred i915 audio component binding Takashi Iwai
2016-04-07 14:09 ` ✗ Fi.CI.BAT: failure for More robust i915 / audio binding Patchwork
2016-05-12 18:49 ` ✗ Ro.CI.BAT: failure for More robust i915 / audio binding (rev2) Patchwork
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=20160517135916.GP27098@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--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