mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v1 4/4] arm: dts: stm32mp151-prtt1l: Configure USB gadget FIFOs for multiple gadgets support
Date: Wed, 3 May 2023 13:01:21 +0200	[thread overview]
Message-ID: <20230503110121.GC6255@pengutronix.de> (raw)
In-Reply-To: <80c80104-7665-e993-cd2a-c8a3facbdb6b@pengutronix.de>

Hello Ahmad,

On Wed, May 03, 2023 at 12:25:03PM +0200, Ahmad Fatoum wrote:
> Hello Oleksij,
> 
> On 03.05.23 12:19, Oleksij Rempel wrote:
> > This patch configures the USB gadget FIFOs of PRTT1L boards to support
> > multiple gadgets at the same time. The configuration was tested with the
> > "usbgadget -S '/dev/mmc1(mmc1)' -s -A '' -b" command.
> 
> What's the downside on configuring the FIFO this way globally
> in stm32mp151.dtsi? Should the same be done for Linux?

I do not know. It seems to be the use-case and SoC specific. Probably doing
this type of configuration in the devicetree is not the best idea at
all, but currently it is only way to do it in kernel, so let's do it in
barebox too.

> > Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> > ---
> >  arch/arm/dts/stm32mp151-prtt1l.dtsi | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/arch/arm/dts/stm32mp151-prtt1l.dtsi b/arch/arm/dts/stm32mp151-prtt1l.dtsi
> > index 98a9c20d6d..fecd068fc0 100644
> > --- a/arch/arm/dts/stm32mp151-prtt1l.dtsi
> > +++ b/arch/arm/dts/stm32mp151-prtt1l.dtsi
> > @@ -56,6 +56,7 @@
> >  	phys = <&usbphyc_port1 0>;
> >  	phy-names = "usb2-phy";
> >  	status = "okay";
> > +	g-tx-fifo-size = <128 128 128 16>;
> >  };
> >  
> >  &usbphyc {
> 
> -- 
> Pengutronix e.K.                           |                             |
> Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
> 31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
> 
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2023-05-03 11:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03 10:19 [PATCH v1 0/4] Improve USB FIFO handling and enable UMS mode on PRTT1L boards Oleksij Rempel
2023-05-03 10:19 ` [PATCH v1 1/4] usb: dwc2: Port support for USB FIFO devicetree properties from Linux v6.3 Oleksij Rempel
2023-05-03 10:19 ` [PATCH v1 2/4] usb: dwc2: Port FIFO configuration sync " Oleksij Rempel
2023-05-03 10:19 ` [PATCH v1 3/4] usb: dwc2: fix multiplier handling in endpoint setup Oleksij Rempel
2023-05-03 10:19 ` [PATCH v1 4/4] arm: dts: stm32mp151-prtt1l: Configure USB gadget FIFOs for multiple gadgets support Oleksij Rempel
2023-05-03 10:25   ` Ahmad Fatoum
2023-05-03 11:01     ` Oleksij Rempel [this message]
2023-05-05  6:39 ` [PATCH v1 0/4] Improve USB FIFO handling and enable UMS mode on PRTT1L boards Sascha Hauer

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=20230503110121.GC6255@pengutronix.de \
    --to=o.rempel@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /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