From: Felipe Balbi <balbi@kernel.org>
To: gregkh@linuxfoundation.org, heiko@sntech.de
Cc: linux-rockchip@lists.infradead.org, briannorris@google.com,
dianders@google.com, kever.yang@rock-chips.com,
huangtao@rock-chips.com, frank.wang@rock-chips.com,
eddie.cai@rock-chips.com, John.Youn@synopsys.com,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
William Wu <william.wu@rock-chips.com>
Subject: Re: [PATCH v3 2/5] usb: dwc3: add dis_u2_freeclk_exists_quirk
Date: Fri, 27 May 2016 15:54:14 +0300 [thread overview]
Message-ID: <87eg8npsp5.fsf@linux.intel.com> (raw)
In-Reply-To: <1464348488-20760-3-git-send-email-william.wu@rock-chips.com>
[-- Attachment #1: Type: text/plain, Size: 405 bytes --]
Hi,
William Wu <william.wu@rock-chips.com> writes:
> Add a quirk to clear the GUSB2PHYCFG.U2_FREECLK_EXISTS bit,
> which specifies whether the USB2.0 PHY provides a free-running
> PHY clock, which is active when the clock control input is active.
>
> Signed-off-by: William Wu <william.wu@rock-chips.com>
can you rebase on top of my testing/next? We're dropping pdata support.
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-05-27 12:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 11:28 [PATCH v3 0/5] support rockchip dwc3 driver William Wu
2016-05-27 11:28 ` [PATCH v3 1/5] usb: dwc3: of-simple: add compatible for rockchip William Wu
[not found] ` <1464348488-20760-1-git-send-email-william.wu-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-05-27 11:28 ` [PATCH v3 2/5] usb: dwc3: add dis_u2_freeclk_exists_quirk William Wu
2016-05-27 12:54 ` Felipe Balbi [this message]
2016-05-27 11:28 ` [PATCH v3 4/5] usb: dwc3: add dis_del_phy_power_chg_quirk William Wu
2016-05-27 11:28 ` [PATCH v3 3/5] usb: dwc3: add phyif_utmi_quirk William Wu
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=87eg8npsp5.fsf@linux.intel.com \
--to=balbi@kernel.org \
--cc=John.Youn@synopsys.com \
--cc=briannorris@google.com \
--cc=dianders@google.com \
--cc=eddie.cai@rock-chips.com \
--cc=frank.wang@rock-chips.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.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