From: "santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com>
To: Franklin S Cooper Jr <fcooper@ti.com>,
gregkh@linuxfoundation.org, robh+dt@kernel.org,
ssantosh@kernel.org, linux@armlinux.org.uk, balbi@kernel.org,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] ARM: dts: k2g: Add support for USB instances on 66AK2G
Date: Mon, 7 Aug 2017 06:41:20 -0700 [thread overview]
Message-ID: <804f13a3-fa4b-6902-d6dc-1c9d4aa0b8fb@oracle.com> (raw)
In-Reply-To: <20170802201724.11439-1-fcooper@ti.com>
On 8/2/17 1:17 PM, Franklin S Cooper Jr wrote:
> Add support for 66AK2G usb instances. However, the driver needs to be updated
> to support PM_RUNTIME. This update has been validated to work on K2L and boot
> tested on K2HK and K2E.
>
> Franklin S Cooper Jr (2):
> usb: dwc3: keystone: Add PM_RUNTIME Support to DWC3 Keystone USB
> driver
> dt-bindings: usb: keystone-usb: Update bindings pm and clocks
> properties
>
> Vitaly Andrianov (1):
> ARM: dts: k2g: Add USB instances
>
> .../devicetree/bindings/usb/keystone-usb.txt | 18 ++++++-
> arch/arm/boot/dts/keystone-k2g.dtsi | 56 ++++++++++++++++++++++
> drivers/usb/dwc3/dwc3-keystone.c | 22 ++++-----
> 3 files changed, 82 insertions(+), 14 deletions(-)
>
Once you get you driver patch lined up, post
the DTS patch separately.
Regards,
Santosh
prev parent reply other threads:[~2017-08-07 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 20:17 [PATCH 0/3] ARM: dts: k2g: Add support for USB instances on 66AK2G Franklin S Cooper Jr
2017-08-02 20:17 ` [PATCH 1/3] usb: dwc3: keystone: Add PM_RUNTIME Support to DWC3 Keystone USB driver Franklin S Cooper Jr
2017-08-02 20:17 ` [PATCH 2/3] dt-bindings: usb: keystone-usb: Update bindings pm and clocks properties Franklin S Cooper Jr
2017-08-10 16:33 ` Rob Herring
2017-08-02 20:17 ` [PATCH 3/3] ARM: dts: k2g: Add USB instances Franklin S Cooper Jr
2017-08-07 13:41 ` santosh.shilimkar [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=804f13a3-fa4b-6902-d6dc-1c9d4aa0b8fb@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fcooper@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=robh+dt@kernel.org \
--cc=ssantosh@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).