From: Rob Herring <robh@kernel.org>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: gregkh@linuxfoundation.org, balbi@ti.com, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, linux-usb@vger.kernel.org,
linux-sh@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3] usb: gadget: renesas_usb3: add support for Renesas USB3.0 peripheral controller
Date: Tue, 22 Dec 2015 18:47:46 -0600 [thread overview]
Message-ID: <20151223004746.GA27730@rob-hp-laptop> (raw)
In-Reply-To: <1450690804-3672-1-git-send-email-yoshihiro.shimoda.uh@renesas.com>
On Mon, Dec 21, 2015 at 06:40:04PM +0900, Yoshihiro Shimoda wrote:
> R-Car H3 has USB3.0 peripheral controllers. This controller's has the
> following features:
> - Supports super, high and full speed
> - Contains 30 pipes for bulk or interrupt transfer
> - Contains dedicated DMA controller
>
> This driver doesn't support the dedicated DMAC for now.
>
> Signed-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
> ---
> This patch is based on the latest Felipe's usb.git / testing/next branch.
> (commit id = e9284de9fae69f1d5e57a4817bfc36dc5f3adf71)
>
> Changes from v2:
> - Fix compatible string order to "<chip>-<peripheral>".
>
> Changes from v1:
> - fix build error in i386 environment if COMPILE_TEST=y
> - merge the header file code into the .c file
> - revise the device tree document about "clocks"
> - remove prototype declarations
> - use udelay(1) instead of ndelay(1) in usb3_wait()
> - remove empty function "usb3_init_phy()"
> - use module_platform_driver()
> - remove bit fields member in some structures
>
>
> .../devicetree/bindings/usb/renesas_usb3.txt | 23 +
For the binding:
Acked-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2015-12-23 0:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 9:40 [PATCH v3] usb: gadget: renesas_usb3: add support for Renesas USB3.0 peripheral controller Yoshihiro Shimoda
2015-12-23 0:47 ` Rob Herring [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=20151223004746.GA27730@rob-hp-laptop \
--to=robh@kernel.org \
--cc=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-sh@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=yoshihiro.shimoda.uh@renesas.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).