All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: Marek Vasut <marex@denx.de>, <u-boot@lists.denx.de>
Cc: Michal Simek <michal.simek@xilinx.com>
Subject: Re: [PATCH] usb: dwc3: Fix support for usb3-phy PHY configuration
Date: Fri, 20 May 2022 08:28:22 +0200	[thread overview]
Message-ID: <465050ff-bb8d-3dac-3010-5d95840a6f32@xilinx.com> (raw)
In-Reply-To: <20220519210319.256526-1-marex@denx.de>



On 5/19/22 23:03, Marek Vasut wrote:
> The dev_read_stringlist_search() in generic_phy_get_by_name()
> returns -ENODATA in case of missing "phy-names", which is the
> case on everything except ZynqMP. Handle this -ENODATA instead
> of failing outright, which fixes the glue on everything else.
> 
> Fixes: 142d50fbce7 ("usb: dwc3: Add support for usb3-phy PHY configuration")
> Signed-off-by: Marek Vasut <marex@denx.de>
> Cc: Michal Simek <michal.simek@xilinx.com>
> ---
>   drivers/usb/dwc3/dwc3-generic.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/usb/dwc3/dwc3-generic.c b/drivers/usb/dwc3/dwc3-generic.c
> index 6e1a1d066b4..9608c5c599a 100644
> --- a/drivers/usb/dwc3/dwc3-generic.c
> +++ b/drivers/usb/dwc3/dwc3-generic.c
> @@ -468,7 +468,7 @@ static int dwc3_glue_probe(struct udevice *dev)
>   		ret = generic_phy_init(&phy);
>   		if (ret)
>   			return ret;
> -	} else if (ret != -ENOENT) {
> +	} else if (ret != -ENOENT && ret != -ENODATA) {
>   		debug("could not get phy (err %d)\n", ret);
>   		return ret;
>   	}

Is already handle by one of these in queue.

https://lore.kernel.org/all/c5a71c30-e55d-c8ab-d372-e5aaa859cf2a@siemens.com/
https://lore.kernel.org/all/360eefb2-b835-840e-8513-6e9e35a002ec@xilinx.com

Thanks,
Michal

      reply	other threads:[~2022-05-20  6:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19 21:03 [PATCH] usb: dwc3: Fix support for usb3-phy PHY configuration Marek Vasut
2022-05-20  6:28 ` Michal Simek [this message]

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=465050ff-bb8d-3dac-3010-5d95840a6f32@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=marex@denx.de \
    --cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.