From: "Pritam Manohar Sutar" <pritam.sutar@samsung.com>
To: "'Thinh Nguyen'" <Thinh.Nguyen@synopsys.com>
Cc: <gregkh@linuxfoundation.org>, <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <rosa.pila@samsung.com>,
<dev.tailor@samsung.com>, <faraz.ata@samsung.com>,
<muhammed.ali@samsung.com>, <selvarasu.g@samsung.com>
Subject: RE: [PATCH] usb: dwc3: Allow usb role swich control from userspace
Date: Thu, 23 Oct 2025 15:25:41 +0530 [thread overview]
Message-ID: <058201dc4403$334b0f20$99e12d60$@samsung.com> (raw)
In-Reply-To: <20251021220935.5njyz5lyiwrsf3rw@synopsys.com>
Hi Thinh,
> -----Original Message-----
> From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
> Sent: 22 October 2025 03:40 AM
> To: Pritam Manohar Sutar <pritam.sutar@samsung.com>
> Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>;
> gregkh@linuxfoundation.org; linux-usb@vger.kernel.org; linux-
> kernel@vger.kernel.org; rosa.pila@samsung.com; dev.tailor@samsung.com;
> faraz.ata@samsung.com; muhammed.ali@samsung.com;
> selvarasu.g@samsung.com
> Subject: Re: [PATCH] usb: dwc3: Allow usb role swich control from userspace
>
> On Mon, Oct 20, 2025, Pritam Manohar Sutar wrote:
> > There is a possibility of user needs for USB mode switching on boards
> > that lack external hardware support for dynamic host/device role
> > detection.
>
> It's fine to enable this. But base on this change log, it sounds like there's no use
> case at the moment? If there is one, even if it's only for debugging purpose,
> please note it so. I'm hesitant to accept changes base on use case speculation
> only.
>
Thank you for your comments.
Yes, a use case exists, especially in automotive, where this feature
is needed to allow user-space applications to switch modes
(host to device or vice-versa) at runtime during CarPlay or Android
Auto operations.
Can you please confirm updated commit message with usecase added as below?
"
usb: dwc3: Allow usb role swich control from userspace
There is a possibility of user needs for USB mode switching on boards
that lack external hardware support for dynamic host/device role
detection. This is particularly relevant in automotive applications
where userspace applications need to switch USB roles (host to device)
at runtime for CarPlay/Android Auto integration.
Add an `allow_userspace_control` flag to handle such cases. When
enabled, it exposes a sysfs attribute that allows userspace to switch
the USB role manually between host and device. This provides flexibility
for platforms that cannot rely on hardware-based mode detection.
The role switch can be done as below
echo host > /sys/class/usb_role/<ADDR>.usb-role-switch/role
echo device > /sys/class/usb_role/<ADDR>.usb-role-switch/role
"
> Thanks,
> Thinh
>
> >
> > Add an `allow_userspace_control` flag to handle such cases. When
> > enabled, it exposes a sysfs attribute that allows userspace to switch
> > the USB role manually between host and device. This provides
> > flexibility for platforms that cannot rely on hardware-based mode detection.
> >
> > The role switch can be done as below
> > echo host > /sys/class/usb_role/<ADDR>.usb-role-switch/role
> > echo device > /sys/class/usb_role/<ADDR>.usb-role-switch/role
> >
> > Signed-off-by: Pritam Manohar Sutar <pritam.sutar@samsung.com>
> > ---
> > drivers/usb/dwc3/drd.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/usb/dwc3/drd.c b/drivers/usb/dwc3/drd.c index
> > 4c91240eb429..589bbeb27454 100644
> > --- a/drivers/usb/dwc3/drd.c
> > +++ b/drivers/usb/dwc3/drd.c
> > @@ -515,6 +515,7 @@ static int dwc3_setup_role_switch(struct dwc3 *dwc)
> > dwc3_role_switch.set = dwc3_usb_role_switch_set;
> > dwc3_role_switch.get = dwc3_usb_role_switch_get;
> > dwc3_role_switch.driver_data = dwc;
> > + dwc3_role_switch.allow_userspace_control = true;
> > dwc->role_sw = usb_role_switch_register(dwc->dev,
> &dwc3_role_switch);
> > if (IS_ERR(dwc->role_sw))
> > return PTR_ERR(dwc->role_sw);
> > --
> > 2.34.1
> >
Thank you,
Regards,
Pritam
next prev parent reply other threads:[~2025-10-23 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20251020112840epcas5p28d8eded5200f096e7b80f71899371f2c@epcas5p2.samsung.com>
2025-10-20 11:37 ` [PATCH] usb: dwc3: Allow usb role swich control from userspace Pritam Manohar Sutar
2025-10-21 22:09 ` Thinh Nguyen
2025-10-23 9:55 ` Pritam Manohar Sutar [this message]
2025-10-23 22:45 ` Thinh Nguyen
2025-10-24 8:32 ` Pritam Manohar Sutar
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='058201dc4403$334b0f20$99e12d60$@samsung.com' \
--to=pritam.sutar@samsung.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=dev.tailor@samsung.com \
--cc=faraz.ata@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=muhammed.ali@samsung.com \
--cc=rosa.pila@samsung.com \
--cc=selvarasu.g@samsung.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