From: Takashi Iwai <tiwai@suse.de>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: "Cezary Rojewski" <cezary.rojewski@intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
broonie@kernel.org, alsa-devel@alsa-project.org,
linux-sound@vger.kernel.org, tiwai@suse.com, perex@perex.cz,
jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
tvrtko.ursulin@linux.intel.com, intel-gfx@lists.freedesktop.org,
amadeuszx.slawinski@linux.intel.com,
pierre-louis.bossart@linux.intel.com, hdegoede@redhat.com
Subject: Re: [PATCH 1/4] ALSA: hda: Skip i915 initialization on CNL/LKF-based platforms
Date: Fri, 23 Feb 2024 09:47:43 +0100 [thread overview]
Message-ID: <878r3b4le8.wl-tiwai@suse.de> (raw)
In-Reply-To: <Zde0kkWX5TrZu-U7@intel.com>
On Thu, 22 Feb 2024 21:54:42 +0100,
Rodrigo Vivi wrote:
>
> On Thu, Feb 22, 2024 at 06:53:12PM +0100, Cezary Rojewski wrote:
> > On 2024-02-22 6:24 PM, Ville Syrjälä wrote:
> > > On Thu, Feb 22, 2024 at 06:06:11PM +0100, Cezary Rojewski wrote:
> > > > Commit 78f613ba1efb ("drm/i915: finish removal of CNL") and its friends
> > > > removed support for i915 for all CNL-based platforms. HDAudio library,
> > > > however, still treats such platforms as valid candidates for i915
> > > > binding. Update query mechanism to reflect changes made in drm tree.
> > > >
> > > > At the same time, i915 support for LKF-based platforms has not been
> > > > provided so remove them from valid binding candidates.
> >
> > ...
> >
> > > > @@ -127,15 +128,26 @@ static int i915_component_master_match(struct device *dev, int subcomponent,
> > > > /* check whether Intel graphics is present and reachable */
> > > > static int i915_gfx_present(struct pci_dev *hdac_pci)
> > > > {
> > > > + /* List of known platforms with no i915 support. */
> > > > + static struct pci_device_id denylist[] = {
> > > > + INTEL_CNL_IDS(NULL),
> > > > + INTEL_LKF_IDS(NULL),
> > > > + { 0 }
> > > > + };
> > >
> > > I thought these don't actually exist in the wild?
> >
> > To my knowledge the opposite is true - while LKFs were shipped in limited
> > number, they still were. I did ask few weeks ago my friends from Windows
> > side about the support and they're still running full-scopes on HDMI
> > endpoints on LKF platforms in their CIs. It seems the drm support is there
> > though. Once you re-boot to linux we get -19 during probe().
> >
> > In regard to CNL, the commit removing CNL-support left the IDs intact what's
>
> I would prefer to go the other way around and remove the unused/unsupported
> IDs entirely and for good.
>
> > very handy to us - we have a lot of spare CNL boards for our validation
> > purposes - CNL-based AudioDSP spans multiple platforms, e.g.:
> > CNL/CFL/WHL/CML. The number of newer boards is lower, unfortunately.
>
> Well, I do see your point here and you are not asking for us to add gfx
> support back, but only help to have this protection here.
>
> However I'm afraid that these entries in the list would only cause
> further confusion. Couldn't they get defined inside your .c directly as
> a const deny_list? so when we go there and remove the missing bits
> of CNL we don't conflict or cause undersired issues to you.
That makes sense. Maybe drm people would get rid of the dead CNL*()
definitions from the header as a cleanup in near future, and we'll hit
a trouble.
thanks,
Takashi
next prev parent reply other threads:[~2024-02-23 8:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 17:06 [PATCH 0/4] ALSA/ASoC: Conditionally skip i915 init and cleanups Cezary Rojewski
2024-02-22 17:06 ` [PATCH 1/4] ALSA: hda: Skip i915 initialization on CNL/LKF-based platforms Cezary Rojewski
2024-02-22 17:24 ` Ville Syrjälä
2024-02-22 17:53 ` Cezary Rojewski
2024-02-22 20:54 ` Rodrigo Vivi
2024-02-23 8:47 ` Takashi Iwai [this message]
2024-02-23 10:30 ` Cezary Rojewski
2024-02-22 17:06 ` [PATCH 2/4] ASoC: codecs: hda: Skip HDMI/DP registration if i915 is missing Cezary Rojewski
2024-02-22 17:06 ` [PATCH 3/4] ASoC: codecs: hda: Cleanup error messages Cezary Rojewski
2024-02-22 17:06 ` [PATCH 4/4] ALSA: hda: Reuse for_each_pcm_streams() Cezary Rojewski
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=878r3b4le8.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=hdegoede@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=tiwai@suse.com \
--cc=tvrtko.ursulin@linux.intel.com \
--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