From: Franklin S Cooper Jr <fcooper@ti.com>
To: Felipe Balbi <balbi@kernel.org>,
gregkh@linuxfoundation.org, robh+dt@kernel.org,
ssantosh@kernel.org, linux@armlinux.org.uk,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, nsekhar@ti.com,
rogerq@ti.com
Subject: Re: [PATCH v2 1/2] usb: dwc3: keystone: Add PM_RUNTIME Support to DWC3 Keystone USB driver
Date: Thu, 17 Aug 2017 07:28:49 -0500 [thread overview]
Message-ID: <926be30f-3a97-ab81-876f-610bdd57775d@ti.com> (raw)
In-Reply-To: <87r2waqu1s.fsf@linux.intel.com>
On 08/17/2017 07:04 AM, Felipe Balbi wrote:
>
> Hi,
>
> Franklin S Cooper Jr <fcooper@ti.com> writes:
>> For 66AK2Gx there is a requirement to use PM Runtime to properly manage
>> clocks and the power domains. Therefore, add PM runtime support. Remove
>> legacy clock api's calls since other users of this driver worked without
>> these clock apis calls.
>>
>> Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
>> ---
>
> I already have the previous version of this in my tree. Seems like the
> only difference was on binding document, right? Do I need to change
> anything in my 'next' and/or 'testing/next' branches?
Correct the binding document is the only difference. Both of your
branches looks good.
>
next prev parent reply other threads:[~2017-08-17 12:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 21:54 [PATCH v2 0/2] ARM: dts: k2g: Add support for USB instances on 66AK2G Franklin S Cooper Jr
2017-08-16 21:54 ` [PATCH v2 1/2] usb: dwc3: keystone: Add PM_RUNTIME Support to DWC3 Keystone USB driver Franklin S Cooper Jr
2017-08-17 7:08 ` Roger Quadros
2017-08-17 12:04 ` Felipe Balbi
2017-08-17 12:28 ` Franklin S Cooper Jr [this message]
2017-08-17 12:31 ` Felipe Balbi
2017-08-16 21:54 ` [PATCH v2 2/2] dt-bindings: usb: keystone-usb: Update bindings pm and clocks properties Franklin S Cooper Jr
2017-08-17 22:18 ` Rob Herring
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=926be30f-3a97-ab81-876f-610bdd57775d@ti.com \
--to=fcooper@ti.com \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=rogerq@ti.com \
--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).