From: Rob Herring <robh@kernel.org>
To: Guodong Xu <guodong.xu@linaro.org>
Cc: pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
jh80.chung@samsung.com, ulf.hansson@linaro.org,
shawn.lin@rock-chips.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: Re: [PATCH 1/2] Documentation: synopsys-dw-mshc: add binding for resets
Date: Fri, 4 Mar 2016 22:28:11 -0600 [thread overview]
Message-ID: <20160305042811.GR13525@rob-hp-laptop> (raw)
In-Reply-To: <1456968818-22140-1-git-send-email-guodong.xu@linaro.org>
On Thu, Mar 03, 2016 at 09:33:37AM +0800, Guodong Xu wrote:
> Add resets property to synopsys-dw-mshc bindings. It is intended to
> represent the hardware reset signal present internally in some host
> controller IC designs.
>
> See Documentation/devicetree/bindings/reset/reset.txt for details.
>
> Signed-off-by: Guodong Xu <guodong.xu@linaro.org>
> ---
> Documentation/devicetree/bindings/mmc/synopsys-dw-mshc.txt | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/mmc/synopsys-dw-mshc.txt b/Documentation/devicetree/bindings/mmc/synopsys-dw-mshc.txt
> index 8636f5a..9b4896c 100644
> --- a/Documentation/devicetree/bindings/mmc/synopsys-dw-mshc.txt
> +++ b/Documentation/devicetree/bindings/mmc/synopsys-dw-mshc.txt
> @@ -39,6 +39,10 @@ Required Properties:
>
> Optional properties:
>
> +* resets: phandle + reset specifier pair, intended to represent hardware
> + reset signal present internally in some host controller IC designs.
> + See Documentation/devicetree/bindings/reset/reset.txt for details.
> +
> * clocks: from common clock binding: handle to biu and ciu clocks for the
> bus interface unit clock and the card interface unit clock.
>
> @@ -48,7 +52,7 @@ Optional properties:
> clock-frequency. It is an error to omit both the ciu clock and the
> clock-frequency.
>
> -* clock-frequency: should be the frequency (in Hz) of the ciu clock. If this
> +* clock-frequency: should be tke frequency (in Hz) of the ciu clock. If this
You've added a typo here.
Otherwise,
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2016-03-05 4:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 1:33 [PATCH 1/2] Documentation: synopsys-dw-mshc: add binding for resets Guodong Xu
2016-03-03 1:33 ` [PATCH 2/2] mmc: dw_mmc: add resets support to dw_mci_parse_dt() Guodong Xu
2016-03-03 2:00 ` Shawn Lin
2016-03-04 3:27 ` zhangfei
[not found] ` <56D900A8.9070204-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-03-04 3:45 ` Shawn Lin
2016-03-05 4:28 ` Rob Herring [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-06 8:47 [PATCH 1/2] Documentation: synopsys-dw-mshc: add binding for resets Guodong Xu
2016-03-07 0:53 ` Jaehoon Chung
2016-03-07 9:35 ` Shawn Lin
2016-03-07 9:51 ` Jaehoon Chung
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=20160305042811.GR13525@rob-hp-laptop \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=guodong.xu@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jh80.chung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=shawn.lin@rock-chips.com \
--cc=ulf.hansson@linaro.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