From: Rob Herring <robh@kernel.org>
To: Frank Wang <frank.wang@rock-chips.com>
Cc: heiko@sntech.de, kishon@ti.com, mark.rutland@arm.com,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-rockchip@lists.infradead.org, huangtao@rock-chips.com,
william.wu@rock-chips.com, daniel.meng@rock-chips.com,
kever.yang@rock-chips.com, andy.yan@rock-chips.com,
wmc@rock-chips.com
Subject: Re: [PATCH v3 2/5] dt-bindings: phy-rockchip-inno-usb2: add companion grf quirk
Date: Thu, 10 Aug 2017 12:05:08 -0500 [thread overview]
Message-ID: <20170810170508.pwf35mud4ffnrzzd@rob-hp-laptop> (raw)
In-Reply-To: <1501747753-6983-3-git-send-email-frank.wang@rock-chips.com>
On Thu, Aug 03, 2017 at 04:09:10PM +0800, Frank Wang wrote:
> Add rockchip,usbgrf and rockchip,companion_grf_quirk to support
> the registers of usb-phy that are distributed in grf and usbgrf
> on some special Rockchip SoCs (e.g RV1108).
>
> Signed-off-by: Frank Wang <frank.wang@rock-chips.com>
> ---
> Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt b/Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt
> index 84d59b0..ddf868a 100644
> --- a/Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt
> +++ b/Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt
> @@ -18,6 +18,10 @@ Optional properties:
> usb-phy output 480m and xin24m.
> Refer to clk/clock-bindings.txt for generic clock
> consumer properties.
> + - rockchip,usbgrf : phandle to the syscon managing the "usb general
> + register files".
> + - rockchip,companion_grf_quirk : when set driver will request
> + "rockchip,usbgrf" phandle as one companion-grf.
Why isn't presence of rockchip,usbgrf or being implied by an SoC
specific compatible string enough?
In any case, use '-' rather than '_'.
>
> Required nodes : a sub-node is required for each port the phy provides.
> The sub-node name is used to identify host or otg port,
> --
> 2.0.0
>
>
next prev parent reply other threads:[~2017-08-10 17:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 8:09 [PATCH v3 0/5] add some quirks for Rockchip usb2-phy and add rv1108 SoCs' support Frank Wang
2017-08-03 8:09 ` [PATCH v3 1/5] phy: rockchip-inno-usb2: add companion grf quirk Frank Wang
2017-08-03 8:09 ` [PATCH v3 2/5] dt-bindings: phy-rockchip-inno-usb2: " Frank Wang
2017-08-10 17:05 ` Rob Herring [this message]
2017-08-11 1:43 ` Frank Wang
2017-08-03 8:09 ` [PATCH v3 3/5] phy: rockchip-inno-usb2: add support for otg-mux interrupt Frank Wang
2017-08-03 8:09 ` [PATCH v3 4/5] dt-bindings: phy-rockchip-inno-usb2: add " Frank Wang
2017-08-10 17:06 ` Rob Herring
2017-08-11 1:46 ` Frank Wang
2017-08-03 8:10 ` [PATCH v3 5/5] phy: rockchip-inno-usb2: add support of usb2-phy for rv1108 SoCs Frank Wang
2017-08-10 17:07 ` 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=20170810170508.pwf35mud4ffnrzzd@rob-hp-laptop \
--to=robh@kernel.org \
--cc=andy.yan@rock-chips.com \
--cc=daniel.meng@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--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=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=william.wu@rock-chips.com \
--cc=wmc@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
all inboxes | Powered by JetHome®