From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
alsa-devel@alsa-project.org
Cc: Maarten Lankhorst <dev@lankhorst.se>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Cezary Rojewski <cezary.rojewski@intel.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
Mark Brown <broonie@kernel.org>,
Daniel Baluta <daniel.baluta@nxp.com>,
linux-kernel@vger.kernel.org,
sound-open-firmware@alsa-project.org
Subject: Re: [PATCH v3 2/9] ALSA: hda/i915: Allow override of gpu binding.
Date: Mon, 7 Aug 2023 09:06:42 -0500 [thread overview]
Message-ID: <cd826184-0a94-425b-8a6e-0988c997bf6f@linux.intel.com> (raw)
In-Reply-To: <20230807090045.198993-3-maarten.lankhorst@linux.intel.com>
On 8/7/23 04:00, Maarten Lankhorst wrote:
> Selecting CONFIG_DRM selects CONFIG_VIDEO_NOMODESET, which exports
> video_firmware_drivers_only(). This can be used as a first
> approximation on whether i915 will be available. It's safe to use as
> this is only built when CONFIG_SND_HDA_I915 is selected by CONFIG_I915.
>
> It's not completely fool proof, as you can boot with "nomodeset
> i915.modeset=1" to make i915 load regardless, or use
> "i915.force_probe=!*" to never load i915, but the common case of
> booting with nomodeset to disable all GPU drivers this will work as
> intended.
>
> Because of this, we add an extra module parameter,
> snd_hda_core.gpu_bind that can be used to signal users intent.
> -1 follows nomodeset, 0 disables binding, 1 forces wait/-EPROBE_DEFER
> on binding.
>
> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Reviewed-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
> Reviewed-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
next prev parent reply other threads:[~2023-08-07 14:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 9:00 [PATCH v3 0/9] sound: Use -EPROBE_DEFER instead of i915 module loading Maarten Lankhorst
2023-08-07 9:00 ` [PATCH v3 1/9] ALSA: hda/intel: Fix error handling in azx_probe() Maarten Lankhorst
2023-08-07 9:00 ` [PATCH v3 2/9] ALSA: hda/i915: Allow override of gpu binding Maarten Lankhorst
2023-08-07 14:06 ` Pierre-Louis Bossart [this message]
2023-08-07 9:00 ` [PATCH v3 3/9] ALSA: hda/i915: Add an allow_modprobe argument to snd_hdac_i915_init Maarten Lankhorst
2023-08-07 14:08 ` Pierre-Louis Bossart
2023-08-12 8:21 ` Takashi Iwai
2023-08-12 14:43 ` Maarten Lankhorst
2023-08-07 9:00 ` [PATCH v3 4/9] ALSA: hda/i915: Allow xe as match for i915_component_master_match Maarten Lankhorst
2023-08-07 14:11 ` Pierre-Louis Bossart
2023-08-07 9:00 ` [PATCH v3 5/9] ASoC: Intel: avs: Move snd_hdac_i915_init to before probe_work Maarten Lankhorst
2023-08-07 14:13 ` Pierre-Louis Bossart
2023-08-07 9:00 ` [PATCH v3 6/9] ASoC: Intel: Skylake: " Maarten Lankhorst
2023-08-07 9:00 ` [PATCH v3 7/9] ALSA: hda/intel: " Maarten Lankhorst
2023-08-07 14:17 ` Pierre-Louis Bossart
2023-08-07 9:00 ` [PATCH v3 8/9] ASoC: SOF: Intel: Move binding to display driver outside of deferred probe Maarten Lankhorst
2023-08-07 14:26 ` Pierre-Louis Bossart
2023-08-12 8:17 ` Takashi Iwai
2023-08-14 14:26 ` Maarten Lankhorst
2023-08-18 10:39 ` Takashi Iwai
2023-08-18 12:24 ` Kai Vehmanen
2023-08-18 12:46 ` Takashi Iwai
2023-08-07 9:00 ` [PATCH v3 9/9] ALSA: hda/i915: Remove extra argument from snd_hdac_i915_init Maarten Lankhorst
2023-08-07 14:28 ` Pierre-Louis Bossart
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=cd826184-0a94-425b-8a6e-0988c997bf6f@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=daniel.baluta@nxp.com \
--cc=dev@lankhorst.se \
--cc=kai.vehmanen@linux.intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sound-open-firmware@alsa-project.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).