From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: "Heiko Stübner" <heiko@sntech.de>,
"Frank Wang" <frank.wang@rock-chips.com>,
"John Youn" <John.Youn@synopsys.com>
Cc: johnyoun@synopsys.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
linux-rockchip@lists.infradead.org, huangtao@rock-chips.com,
kever.yang@rock-chips.com, william.wu@rock-chips.com,
daniel.meng@rock-chips.com
Subject: Re: [PATCH v2 2/2] usb: dwc2: add multiple clocks handling
Date: Tue, 28 Mar 2017 16:49:34 +0300 [thread overview]
Message-ID: <87mvc5fr4h.fsf@linux.intel.com> (raw)
In-Reply-To: <1905699.rAdUkra9dJ@diego>
Hi,
Heiko Stübner <heiko@sntech.de> writes:
> Am Donnerstag, 9. Februar 2017, 10:44:39 CET schrieb Frank Wang:
>> Since dwc2 may have one or more input clocks need to manage for some
>> platform, so this adds change clk to clk's array of struct dwc2_hsotg
>> to handle more clocks operation.
>>
>> Signed-off-by: Frank Wang <frank.wang@rock-chips.com>
>
> for the simple clock handling the dwc2-driver does right now, this looks
> adquate and honoring EPROBE_DEFER is a nice touch ;-), so
>
> Reviewed-by: Heiko Stuebner <heiko@sntech.de>
John, care to look at this series?
--
balbi
next prev parent reply other threads:[~2017-03-28 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 2:44 [PATCH v2 0/2] add multiple clock handling for dwc2 driver Frank Wang
2017-02-09 2:44 ` [PATCH v2 1/2] Documentation: dt: dwc2: amend clocks property Frank Wang
2017-02-09 2:44 ` [PATCH v2 2/2] usb: dwc2: add multiple clocks handling Frank Wang
2017-02-09 12:31 ` Heiko Stübner
2017-03-28 13:49 ` Felipe Balbi [this message]
2017-04-17 10:33 ` Frank Wang
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=87mvc5fr4h.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=John.Youn@synopsys.com \
--cc=daniel.meng@rock-chips.com \
--cc=frank.wang@rock-chips.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=johnyoun@synopsys.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=william.wu@rock-chips.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).