From: Roger Quadros <rogerq@ti.com>
To: balbi@kernel.org
Cc: tony@atomide.com, Joao.Pinto@synopsys.com,
sergei.shtylyov@cogentembedded.com, peter.chen@freescale.com,
jun.li@freescale.com, grygorii.strashko@ti.com,
yoshihiro.shimoda.uh@renesas.com, nsekhar@ti.com,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: Re: [PATCH v7 0/4] usb: dwc3: dual-role support
Date: Fri, 10 Jun 2016 16:26:09 +0300 [thread overview]
Message-ID: <575ABFF1.1040503@ti.com> (raw)
In-Reply-To: <1465564650-27516-1-git-send-email-rogerq@ti.com>
On 10/06/16 16:17, Roger Quadros wrote:
> Hi,
>
> This series adds dual role support to dwc3 controller driver.
> Series depends on the OTG/dual-role framework [1].
>
> [1] - http://thread.gmane.org/gmane.linux.usb.general/143568
>
> Patches are based on Felipe's balbi/usb.git testing/next
This patch is also a pre-requisite for this series.
http://article.gmane.org/gmane.linux.kernel/2240761
>
> Changelog:
>
> v7:
> - rebased to v4.7-rc1 + balbi/usb.git testing/next
> - cleaned up otg irq resource code
>
> v6:
> - use just otg irq to get otg events and don't depend on extcon at all.
> - follow OTG flow in TRM strictly.
> - use tracepoints instead of dev_dbg().
> - match IRQ flags in dwc3_omap and core.c for shared otg interrupt.
>
> v5: Internal revision. Not sent to mailing list.
>
> v4: first version that was reviewed.
>
> cheers,
> -roger
>
>
> Roger Quadros (4):
> usb: dwc3: core.h: add some register definitions
> usb: dwc3: add dual-role support
> ARM: dts: dra7*-evm: Enable dual-role for usb1
> ARM: dts: am43xx: Enable dual-role on USB1
>
> arch/arm/boot/dts/am437x-gp-evm.dts | 5 +-
> arch/arm/boot/dts/am437x-sk-evm.dts | 5 +-
> arch/arm/boot/dts/am43x-epos-evm.dts | 5 +-
> arch/arm/boot/dts/dra7-evm.dts | 5 +-
> arch/arm/boot/dts/dra72-evm-common.dtsi | 5 +-
> drivers/usb/dwc3/core.c | 546 +++++++++++++++++++++++++++++++-
> drivers/usb/dwc3/core.h | 114 ++++++-
> drivers/usb/dwc3/gadget.c | 6 +-
> drivers/usb/dwc3/host.c | 2 +
> 9 files changed, 677 insertions(+), 16 deletions(-)
>
prev parent reply other threads:[~2016-06-10 13:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 13:17 [PATCH v7 0/4] usb: dwc3: dual-role support Roger Quadros
2016-06-10 13:17 ` [PATCH v7 1/4] usb: dwc3: core.h: add some register definitions Roger Quadros
2016-06-20 9:28 ` Felipe Balbi
[not found] ` <87fus8qkep.fsf-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2016-06-20 11:53 ` Roger Quadros
2016-06-20 12:04 ` Felipe Balbi
2016-06-10 13:17 ` [PATCH v7 2/4] usb: dwc3: add dual-role support Roger Quadros
[not found] ` <1465564650-27516-3-git-send-email-rogerq-l0cyMroinI0@public.gmane.org>
2016-06-12 9:11 ` Peter Chen
2016-06-13 7:09 ` Roger Quadros
[not found] ` <575E5C21.8040103-l0cyMroinI0@public.gmane.org>
2016-06-13 8:25 ` Roger Quadros
2016-06-10 13:17 ` [PATCH v7 3/4] ARM: dts: dra7*-evm: Enable dual-role for usb1 Roger Quadros
2016-06-10 13:17 ` [PATCH v7 4/4] ARM: dts: am43xx: Enable dual-role on USB1 Roger Quadros
2016-06-10 13:26 ` Roger Quadros [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=575ABFF1.1040503@ti.com \
--to=rogerq@ti.com \
--cc=Joao.Pinto@synopsys.com \
--cc=balbi@kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=jun.li@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=peter.chen@freescale.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=tony@atomide.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