From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 RFC 2/6] usb: dwc2: Add DT properties to specify fifo size in host/otg mode
Date: Fri, 29 Jul 2016 16:12:29 -0500 [thread overview]
Message-ID: <20160729211229.GA3575@rob-hp-laptop> (raw)
In-Reply-To: <1469559213-16160-3-git-send-email-stefan.wahren@i2se.com>
On Tue, Jul 26, 2016 at 06:53:29PM +0000, Stefan Wahren wrote:
> Currently the fifo sizes for host/otg mode are defined per platform
> and doesn't take the mode into account. So we will get errors
> like this:
>
> dwc2 20980000.usb: 256 invalid for host_nperio_tx_fifo_size.
> dwc2 20980000.usb: Setting host_nperio_tx_fifo_size to 32
>
> So add DT properties for these mode specific fifo sizes in order
> to define them in the devicetree and avoid these errors.
>
> Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
> ---
> Documentation/devicetree/bindings/usb/dwc2.txt | 3 +++
Acked-by: Rob Herring <robh@kernel.org>
> drivers/usb/dwc2/core.c | 25 ++++++++++++++++++------
> 2 files changed, 22 insertions(+), 6 deletions(-)
next prev parent reply other threads:[~2016-07-29 21:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 18:53 [PATCH V2 RFC 0/6] ARM: dts: bcm2835: Add Raspberry Pi Zero Stefan Wahren
2016-07-26 18:53 ` [PATCH V2 RFC 1/6] usb: dwc2: core: Avoid nonsense error in gadget mode Stefan Wahren
2016-08-16 1:30 ` John Youn
2016-08-16 16:22 ` Eric Anholt
2016-08-16 16:44 ` Stefan Wahren
2016-08-16 19:20 ` John Youn
2016-08-16 20:09 ` Stefan Wahren
2016-07-26 18:53 ` [PATCH V2 RFC 2/6] usb: dwc2: Add DT properties to specify fifo size in host/otg mode Stefan Wahren
2016-07-29 21:12 ` Rob Herring [this message]
2016-08-18 18:12 ` John Youn
2016-07-26 18:53 ` [PATCH V2 RFC 3/6] ARM: dts: bcm283x: Add missing usb clock Stefan Wahren
2016-07-26 18:53 ` [PATCH V2 RFC 4/6] ARM: dts: bcm283x: Add generic USB PHY Stefan Wahren
2016-07-26 18:53 ` [PATCH V2 RFC 5/6] DT: bindings: bcm: Add Raspberry Pi Zero Stefan Wahren
2016-07-29 21:13 ` Rob Herring
2016-07-26 18:53 ` [PATCH V2 RFC 6/6] ARM: dts: bcm2835: " Stefan Wahren
2016-08-02 17:19 ` Stephen Warren
2016-08-02 19:29 ` Stefan Wahren
2016-08-02 20:56 ` Stephen Warren
2016-08-16 19:30 ` John Youn
2016-08-16 19:58 ` Stefan Wahren
2016-08-16 22:07 ` John Youn
2016-08-17 19:11 ` Stefan Wahren
2016-08-17 21:21 ` John Youn
2016-08-17 22:17 ` Stefan Wahren
2016-08-18 18:03 ` John Youn
2016-08-18 19:04 ` Stefan Wahren
2016-08-18 19:34 ` John Youn
2016-08-18 18:14 ` [PATCH V2 RFC 0/6] " Eric Anholt
2016-08-18 18:57 ` Stefan Wahren
2016-08-19 0:37 ` Eric Anholt
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=20160729211229.GA3575@rob-hp-laptop \
--to=robh@kernel.org \
--cc=linux-arm-kernel@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