public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Roger Quadros <rogerq@kernel.org>,
	Siddharth Vadapalli <s-vadapalli@ti.com>,
	trini@konsulko.com, marex@denx.de, bmeng.cn@gmail.com,
	jonas@kwiboo.se
Cc: u-boot@lists.denx.de, srk@ti.com
Subject: Re: [PATCH] usb: xhci-dwc3: Bail out if "dr_mode" is "peripheral"
Date: Thu, 16 Jan 2025 10:36:45 +0100	[thread overview]
Message-ID: <87cygn85hu.fsf@baylibre.com> (raw)
In-Reply-To: <ceb060fa-d430-458d-b711-508a4bd34d48@kernel.org>

Hi Siddharth,

On lun., déc. 09, 2024 at 15:20, Roger Quadros <rogerq@kernel.org> wrote:

> Hi Siddharth,
>
> On 06/12/2024 13:04, Siddharth Vadapalli wrote:
>> Since the compatible "snps,dwc3" can be specified in the device-tree for
>> the Designware USB Controller configured for not only Host and OTG modes
>> of operation, but also for Peripheral mode of operation, bail out if
>> "dr_mode" is "peripheral".
>> 
>> Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>
>> ---
>> 
>> Hello,
>> 
>> This patch is based on commit
>> 448add55297 Merge branch 'master' of https://source.denx.de/u-boot/custodians/u-boot-pmic
>> of the master branch of U-Boot.
>> 
>> Regards,
>> Siddharth.
>> 
>>  drivers/usb/host/xhci-dwc3.c | 3 +++
>>  1 file changed, 3 insertions(+)
>> 
>> diff --git a/drivers/usb/host/xhci-dwc3.c b/drivers/usb/host/xhci-dwc3.c
>> index e3e0ceff43e..7b1311503fe 100644
>> --- a/drivers/usb/host/xhci-dwc3.c
>> +++ b/drivers/usb/host/xhci-dwc3.c
>> @@ -208,6 +208,9 @@ static int xhci_dwc3_probe(struct udevice *dev)
>>  	writel(reg, &dwc3_reg->g_usb2phycfg[0]);
>>  
>>  	dr_mode = usb_get_dr_mode(dev_ofnode(dev));
>> +	if (dr_mode == USB_DR_MODE_PERIPHERAL)
>> +		return -ENODEV;
>> +
>>  	if (dr_mode == USB_DR_MODE_OTG &&
>>  	    dev_read_bool(dev, "usb-role-switch")) {
>>  		dr_mode = usb_get_role_switch_default_mode(dev_ofnode(dev));
>
> Although this proposal was suggested in [1] and later clarified in
> [2] I will summarize the discussion here.
>
> This patch fix is not sufficient for all cases as the xhci-dwc3.c
> driver will still be probed if dr_mode is OTG or HOST along with
> other platform drivers if enabled in config.
>
> The only current solution is not not enable CONFIG_USB_XHCI_DWC3
> together with another platform driver config (e.g. CONFIG_USB_DWC3_GENERIC)
> if snps,dwc3 should not be managed by xhci-dwc3.c.

Given Roger's explanation, should we simply drop this, or is any other
action expected from the U-Boot maintainers?

Thanks,
Mattijs

>
> [1] - https://lore.kernel.org/all/unf757pwgah5ylkcfdumtdo5zs2ny3nxct5u26t6up7aldqim2@mxhhtb53gw4x/
> [2] - https://lore.kernel.org/all/a9c458f8-68e5-448b-9977-e7bf37b00d35@kernel.org/
>
> -- 
> cheers,
> -roger

  reply	other threads:[~2025-01-16  9:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06 11:04 [PATCH] usb: xhci-dwc3: Bail out if "dr_mode" is "peripheral" Siddharth Vadapalli
2024-12-09 13:20 ` Roger Quadros
2025-01-16  9:36   ` Mattijs Korpershoek [this message]
2025-01-16 10:18     ` Siddharth Vadapalli
2025-01-16 10:28       ` Mattijs Korpershoek

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=87cygn85hu.fsf@baylibre.com \
    --to=mkorpershoek@baylibre.com \
    --cc=bmeng.cn@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=marex@denx.de \
    --cc=rogerq@kernel.org \
    --cc=s-vadapalli@ti.com \
    --cc=srk@ti.com \
    --cc=trini@konsulko.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox