public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Benson Leung <bleung@google.com>
Cc: Takashi Iwai <tiwai@suse.de>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Won Chung <wonchung@google.com>, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>, Benson Leung <bleung@chromium.org>,
	Prashant Malani <pmalani@chromium.org>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] sound/hda: Add NULL check to component match callback function
Date: Thu, 31 Mar 2022 19:10:20 +0300	[thread overview]
Message-ID: <YkXSbPG+PuyGub2V@lahna> (raw)
In-Reply-To: <YkXJr2KhSzHJHxRF@google.com>

Hi,

On Thu, Mar 31, 2022 at 08:33:03AM -0700, Benson Leung wrote:
> > --- a/sound/hda/hdac_i915.c
> > +++ b/sound/hda/hdac_i915.c
> > @@ -102,18 +102,13 @@ static int i915_component_master_match(struct device *dev, int subcomponent,
> >  	struct pci_dev *hdac_pci, *i915_pci;
> >  	struct hdac_bus *bus = data;
> >  
> > -	if (!dev_is_pci(dev))
> > +	if (subcomponent != I915_COMPONENT_AUDIO || !dev_is_pci(dev))
> >  		return 0;
> >  
> 
> If I recall this bug correctly, it's not the usb port perse that is falling
> through this !dev_is_pci(dev) check, it's actually the usb4-port in a new
> proposed patch by Heikki and Mika to extend the usb type-c component to
> encompass the usb4 specific pieces too. Is it possible usb4 ports are considered
> pci devices, and that's how we got into this situation?

For usb4_port the dev_ic_pci(dev) returns false:

  #define dev_is_pci(d) ((d)->bus == &pci_bus_type)

We don't attach them to PCI bus (well they are not PCI devices).

  parent reply	other threads:[~2022-03-31 16:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-30 21:19 [PATCH v2] sound/hda: Add NULL check to component match callback function Won Chung
2022-03-31  7:27 ` Takashi Iwai
2022-03-31  8:38   ` Won Chung
2022-03-31  9:12     ` Takashi Iwai
2022-03-31  9:25       ` Heikki Krogerus
2022-03-31  9:28         ` Takashi Iwai
2022-03-31  9:34           ` Heikki Krogerus
2022-03-31  9:45             ` Takashi Iwai
2022-03-31 13:29               ` Takashi Iwai
2022-03-31 14:19                 ` Takashi Iwai
2022-03-31 15:33                   ` Benson Leung
2022-03-31 15:37                     ` Takashi Iwai
2022-03-31 16:10                     ` Mika Westerberg [this message]
2022-03-31 16:38                     ` Greg KH
2022-03-31 16:58                       ` Won Chung
2022-03-31 17:18                         ` Greg KH
2022-03-31 17:33                           ` Benson Leung
2022-03-31 17:46                             ` Greg KH
2022-04-01  7:02                   ` Heikki Krogerus
2022-03-31 11:39         ` Greg KH
2022-03-31 12:52           ` Heikki Krogerus
2022-03-31 12:56             ` Greg KH
2022-03-31 13:15             ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2022-03-30 20:55 Won Chung
2022-03-30 21:15 ` Won Chung

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=YkXSbPG+PuyGub2V@lahna \
    --to=mika.westerberg@linux.intel.com \
    --cc=bleung@chromium.org \
    --cc=bleung@google.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=pmalani@chromium.org \
    --cc=stable@vger.kernel.org \
    --cc=tiwai@suse.com \
    --cc=tiwai@suse.de \
    --cc=wonchung@google.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