From: Rob Herring <robh@kernel.org>
To: Keiji Hayashibara <hayashibara.keiji@socionext.com>
Cc: broonie@kernel.org, mark.rutland@arm.com,
yamada.masahiro@socionext.com, linux-spi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
stable@vger.kernel.org, masami.hiramatsu@linaro.org,
jaswinder.singh@linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: uniphier: fix incorrect property items
Date: Thu, 25 Oct 2018 14:59:07 -0500 [thread overview]
Message-ID: <20181025195906.GA22391@bogus> (raw)
In-Reply-To: <1540373669-18969-1-git-send-email-hayashibara.keiji@socionext.com>
On Wed, Oct 24, 2018 at 06:34:29PM +0900, Keiji Hayashibara wrote:
> This commit fixes incorrect property because it was different
> from the actual.
> The parameters of '#address-cells' and '#size-cells' were removed,
> and 'interrupts', 'pinctrl-names' and 'pinctrl-0' were added.
>
> Fixes: 4dcd5c2781f3 ("spi: add DT bindings for UniPhier SPI controller")
> Signed-off-by: Keiji Hayashibara <hayashibara.keiji@socionext.com>
> ---
> Documentation/devicetree/bindings/spi/spi-uniphier.txt | 14 ++++++++------
> 1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/spi/spi-uniphier.txt b/Documentation/devicetree/bindings/spi/spi-uniphier.txt
> index 504a4ec..b04e66a 100644
> --- a/Documentation/devicetree/bindings/spi/spi-uniphier.txt
> +++ b/Documentation/devicetree/bindings/spi/spi-uniphier.txt
> @@ -5,18 +5,20 @@ UniPhier SoCs have SCSSI which supports SPI single channel.
> Required properties:
> - compatible: should be "socionext,uniphier-scssi"
> - reg: address and length of the spi master registers
> - - #address-cells: must be <1>, see spi-bus.txt
> - - #size-cells: must be <0>, see spi-bus.txt
How is removing these correct? They are needed if you have any child
devices.
> - - clocks: A phandle to the clock for the device.
> - - resets: A phandle to the reset control for the device.
> + - interrupts: a single interrupt specifier
> + - pinctrl-names: should be "default"
> + - pinctrl-0: pin control state for the default mode
> + - clocks: a phandle to the clock for the device
> + - resets: a phandle to the reset control for the device
>
> Example:
>
> spi0: spi@54006000 {
> compatible = "socionext,uniphier-scssi";
> reg = <0x54006000 0x100>;
> - #address-cells = <1>;
> - #size-cells = <0>;
> + interrupts = <0 39 4>;
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_spi0>;
> clocks = <&peri_clk 11>;
> resets = <&peri_rst 11>;
> };
> --
> 2.7.4
>
next prev parent reply other threads:[~2018-10-25 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 9:34 [PATCH] spi: uniphier: fix incorrect property items Keiji Hayashibara
2018-10-24 10:32 ` Applied "spi: uniphier: fix incorrect property items" to the spi tree Mark Brown
2018-10-25 19:59 ` Rob Herring [this message]
2018-10-26 0:12 ` [PATCH] spi: uniphier: fix incorrect property items Keiji Hayashibara
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=20181025195906.GA22391@bogus \
--to=robh@kernel.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hayashibara.keiji@socionext.com \
--cc=jaswinder.singh@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=masami.hiramatsu@linaro.org \
--cc=stable@vger.kernel.org \
--cc=yamada.masahiro@socionext.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).