From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: Pavel Hofman <pavel.hofman@ivitera.com>,
Minas Harutyunyan <hminas@synopsys.com>,
Rob Herring <robh+dt@kernel.org>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org
Subject: Re: [PATCH] overlays: dwc2: Increase RX FIFO size
Date: Fri, 07 Feb 2020 18:25:09 +0100 [thread overview]
Message-ID: <9b0f8daeb12ad4e5be74ff93e64c38087af199cf.camel@suse.de> (raw)
In-Reply-To: <43db1d9c-6fa2-88bd-11df-6ae2f48a4ac9@ivitera.com>
[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]
Hi Pavel,
Could you change the patch title to something like this (see other patches
changing the device-trees, you'll see it's the common pattern):
ARM: dts: bcm283x: increase dwc2's RX FIFO size
On Fri, 2020-02-07 at 17:30 +0100, Pavel Hofman wrote:
> The previous version of the dwc2 overlay set the RX FIFO size to
> 256 4-byte words. This sounds large enough for a 1024 byte packet (the
> largest isochronous high speed packet allowed), but it doesn't take
> into account some extra space needed by the hardware.
>
> Minas Harutyunyan at Synopsys (the source of the DWC OTG design)
> came up with a more correct value, 301, but since there is spare packet
> RAM this can be increased to 558 to allow two packets per frame.
I suggest making a short summary of your github explanation[1] instead of just
citing Minas. On one hand Minas' memory might get fuzzy after some time (or not
be able to access the documentation) and...
> See: https://github.com/raspberrypi/linux/issues/3447
...you're assuming this link will be always available. Which is unlikely. After
properly explaining the issue, you won't need the link anyway. Ultimately a
patch description should be as self-contained/self-explanatory as possible.
Other than that the patch looks good.
Thanks!
Nicolas
[1] https://github.com/raspberrypi/linux/issues/3447#issuecomment-581815066
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-02-07 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 16:30 [PATCH] overlays: dwc2: Increase RX FIFO size Pavel Hofman
2020-02-07 17:25 ` 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=9b0f8daeb12ad4e5be74ff93e64c38087af199cf.camel@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=hminas@synopsys.com \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=pavel.hofman@ivitera.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).