devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: nicolas saenz julienne <nsaenz@kernel.org>
To: Stefan Wahren <stefan.wahren@i2se.com>, Rob Herring <robh+dt@kernel.org>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	Ray Jui <rjui@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>,
	bcm-kernel-feedback-list@broadcom.com,
	devicetree@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	Pavel Hofman <pavel.hofman@ivitera.com>
Subject: Re: [PATCH] Revert "ARM: dts: bcm283x: increase dwc2's RX FIFO size"
Date: Tue, 08 Jun 2021 12:06:52 +0200	[thread overview]
Message-ID: <31a7c717b404f1dfd82bb2cc3cbd16c4b1830dde.camel@kernel.org> (raw)
In-Reply-To: <1622293371-5997-1-git-send-email-stefan.wahren@i2se.com>

On Sat, 2021-05-29 at 15:02 +0200, Stefan Wahren wrote:
> This reverts commit 278407a53c3b33fb820332c4d39eb39316c3879a.
> 
> The original change breaks USB config on Raspberry Pi Zero and Pi 4 B,
> because it exceeds the total fifo size of 4080. A naive attempt to reduce
> g-tx-fifo-size doesn't help on Raspberry Pi Zero. So better go back.
> 
> Fixes: 278407a53c3b ("ARM: dts: bcm283x: increase dwc2's RX FIFO size")
> Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
> Cc: Pavel Hofman <pavel.hofman@ivitera.com>
> ---

Applied for next.

Regards,
Nicolas


      reply	other threads:[~2021-06-08 10:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-29 13:02 [PATCH] Revert "ARM: dts: bcm283x: increase dwc2's RX FIFO size" Stefan Wahren
2021-06-08 10:06 ` nicolas saenz julienne [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=31a7c717b404f1dfd82bb2cc3cbd16c4b1830dde.camel@kernel.org \
    --to=nsaenz@kernel.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=pavel.hofman@ivitera.com \
    --cc=rjui@broadcom.com \
    --cc=robh+dt@kernel.org \
    --cc=sbranden@broadcom.com \
    --cc=stefan.wahren@i2se.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;
as well as URLs for NNTP newsgroup(s).