linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: Stephan Gerhold <stephan@gerhold.net>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-tegra@vger.kernel.org
Subject: Re: [PATCH] usb: common: ulpi: Fix crash in ulpi_match()
Date: Mon, 17 Jan 2022 16:10:51 +0200	[thread overview]
Message-ID: <YeV466hTEyDwvmyL@kuha.fi.intel.com> (raw)
In-Reply-To: <20220114100217.59541-1-jonathanh@nvidia.com>

Hi Jon,

On Fri, Jan 14, 2022 at 10:02:17AM +0000, Jon Hunter wrote:
> Commit 7495af930835 ("ARM: multi_v7_defconfig: Enable drivers for
> DragonBoard 410c") enables the CONFIG_PHY_QCOM_USB_HS for the ARM
> multi_v7_defconfig. Enabling this Kconfig is causing the kernel to crash
> on the Tegra20 Ventana platform in the ulpi_match() function.
> 
> The Qualcomm USB HS PHY driver that is enabled by CONFIG_PHY_QCOM_USB_HS,
> registers a ulpi_driver but this driver does not provide an 'id_table',
> so when ulpi_match() is called on the Tegra20 Ventana platform, it
> crashes when attempting to deference the id_table pointer which is not
> valid. The Qualcomm USB HS PHY driver uses device-tree for matching the
> ULPI driver with the device and so fix this crash by using device-tree
> for matching if the id_table is not valid.
> 
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>

So is this fixing commit 7495af930835, or perhaps commit ef6a7bcfb01c
("usb: ulpi: Support device discovery via DT")?

I would assume ef6a7bcfb01c ("usb: ulpi: Support device discovery via
DT"). Please include the appropriate Fixes tag.

> ---
>  drivers/usb/common/ulpi.c | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/usb/common/ulpi.c b/drivers/usb/common/ulpi.c
> index 4169cf40a03b..8f8405b0d608 100644
> --- a/drivers/usb/common/ulpi.c
> +++ b/drivers/usb/common/ulpi.c
> @@ -39,8 +39,11 @@ static int ulpi_match(struct device *dev, struct device_driver *driver)
>  	struct ulpi *ulpi = to_ulpi_dev(dev);
>  	const struct ulpi_device_id *id;
>  
> -	/* Some ULPI devices don't have a vendor id so rely on OF match */
> -	if (ulpi->id.vendor == 0)
> +	/*
> +	 * Some ULPI devices don't have a vendor id
> +	 * or provide an id_table so rely on OF match.
> +	 */
> +	if (ulpi->id.vendor == 0 || !drv->id_table)
>  		return of_driver_match_device(dev, driver);
>  
>  	for (id = drv->id_table; id->vendor; id++)
> -- 
> 2.25.1

thanks,

-- 
heikki

  reply	other threads:[~2022-01-17 14:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 10:02 [PATCH] usb: common: ulpi: Fix crash in ulpi_match() Jon Hunter
2022-01-17 14:10 ` Heikki Krogerus [this message]
2022-01-17 15:01   ` Jon Hunter

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=YeV466hTEyDwvmyL@kuha.fi.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stephan@gerhold.net \
    /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).