From: Peter Chen <hzpeterchen@gmail.com>
To: Jisheng Zhang <jszhang@marvell.com>
Cc: robh+dt@kernel.org, mark.rutland@arm.com, peter.chen@nxp.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: ci-hdrc-usb2: s/gadget-itc-setting/itc-setting in example
Date: Tue, 21 Jun 2016 12:29:05 +0800 [thread overview]
Message-ID: <20160621042905.GH26936@shlinux2> (raw)
In-Reply-To: <1466064798-867-1-git-send-email-jszhang@marvell.com>
On Thu, Jun 16, 2016 at 04:13:18PM +0800, Jisheng Zhang wrote:
> What the code expect is "itc-setting" rather than "gadget-itc-setting",
> and this is also correctly described in the optional properties.
>
> Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
> ---
> Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt b/Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt
> index 1084e2b..341dc67 100644
> --- a/Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt
> +++ b/Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt
> @@ -93,7 +93,7 @@ Example:
> phys = <&usb_phy0>;
> phy-names = "usb-phy";
> vbus-supply = <®_usb0_vbus>;
> - gadget-itc-setting = <0x4>; /* 4 micro-frames */
> + itc-setting = <0x4>; /* 4 micro-frames */
> /* Incremental burst of unspecified length */
> ahb-burst-config = <0x0>;
> tx-burst-size-dword = <0x10>; /* 64 bytes */
> --
Applied, thanks.
--
Best Regards,
Peter Chen
prev parent reply other threads:[~2016-06-21 4:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 8:13 [PATCH] dt-bindings: ci-hdrc-usb2: s/gadget-itc-setting/itc-setting in example Jisheng Zhang
2016-06-19 14:54 ` Rob Herring
2016-06-21 4:29 ` Peter Chen [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=20160621042905.GH26936@shlinux2 \
--to=hzpeterchen@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jszhang@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peter.chen@nxp.com \
--cc=robh+dt@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).