From: Sourav Poddar <sourav.poddar@ti.com>
To: Eric Witcher <ewitcher@mindspring.com>
Cc: robherring2@gmail.com, bcousson@baylibre.com,
matt.porter@linaro.org, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org,
Santosh Shilimkar <santosh.shilimkar@ti.com>
Subject: Re: [RESEND][PATCH] ARM: OMAP: devicetree: fix SPI node compatible property syntax items
Date: Fri, 8 Nov 2013 09:18:56 +0530 [thread overview]
Message-ID: <527C5F28.40007@ti.com> (raw)
In-Reply-To: <1383831938-9402-1-git-send-email-ewitcher@mindspring.com>
On Thursday 07 November 2013 07:15 PM, Eric Witcher wrote:
> Correct the SPI node compatible property items to match example code and
> match current DTS usage.
>
> Signed-off-by: Eric Witcher<ewitcher@mindspring.com>
> ---
> Documentation/devicetree/bindings/spi/omap-spi.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/spi/omap-spi.txt b/Documentation/devicetree/bindings/spi/omap-spi.txt
> index 4c85c4c..2ba5f9c 100644
> --- a/Documentation/devicetree/bindings/spi/omap-spi.txt
> +++ b/Documentation/devicetree/bindings/spi/omap-spi.txt
> @@ -2,8 +2,8 @@ OMAP2+ McSPI device
>
> Required properties:
> - compatible :
> - - "ti,omap2-spi" for OMAP2& OMAP3.
> - - "ti,omap4-spi" for OMAP4+.
> + - "ti,omap2-mcspi" for OMAP2& OMAP3.
> + - "ti,omap4-mcspi" for OMAP4+.
> - ti,spi-num-cs : Number of chipselect supported by the instance.
> - ti,hwmods: Name of the hwmod associated to the McSPI
> - ti,pindir-d0-out-d1-in: Select the D0 pin as output and D1 as
Acked-by: Sourav Poddar <sourav.poddar@ti.com>
prev parent reply other threads:[~2013-11-08 3:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 13:45 [RESEND][PATCH] ARM: OMAP: devicetree: fix SPI node compatible property syntax items Eric Witcher
2013-11-08 3:48 ` Sourav Poddar [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=527C5F28.40007@ti.com \
--to=sourav.poddar@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=ewitcher@mindspring.com \
--cc=linux-omap@vger.kernel.org \
--cc=matt.porter@linaro.org \
--cc=robherring2@gmail.com \
--cc=santosh.shilimkar@ti.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).