linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Murali Karicheri <m-karicheri2@ti.com>,
	rob.herring@calxeda.com, rob@landley.net,
	devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	spi-devel-general@lists.sourceforge.net,
	davinci-linux-open-source@linux.davincidsp.com,
	linux-keystone@list.ti.com
Cc: Murali Karicheri <m-karicheri2@ti.com>
Subject: Re: [linux-keystone] [PATCH v1 1/1] spi: davinci: add OF support for the spi controller
Date: Wed, 05 Dec 2012 23:49:46 +0000	[thread overview]
Message-ID: <20121205234947.0EB3D3E0E22@localhost> (raw)
In-Reply-To: <1354559918-15105-2-git-send-email-m-karicheri2@ti.com>

On Mon, 3 Dec 2012 13:38:38 -0500, Murali Karicheri <m-karicheri2@ti.com> wrote:
> This adds OF support to DaVinci SPI controller to configure platform
> data through device bindings. Also replaces clk_enable() with
> of clk_prepare_enable() as well as clk_disable() with
> clk_disable_unprepare().
> 

Hi Murali.

Thanks for the patch. Comments below...

> Signed-off-by: Murali Karicheri <m-karicheri2@ti.com>
> Reviewed-by : Grant Likely <grant.likely@secretlab.ca>
> ---
>  .../devicetree/bindings/spi/spi-davinci.txt        |   51 ++++++++++
>  drivers/spi/spi-davinci.c                          |  102 +++++++++++++++++---
>  2 files changed, 139 insertions(+), 14 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/spi/spi-davinci.txt
> 
> diff --git a/Documentation/devicetree/bindings/spi/spi-davinci.txt b/Documentation/devicetree/bindings/spi/spi-davinci.txt
> new file mode 100644
> index 0000000..a2746c5
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/spi/spi-davinci.txt
> @@ -0,0 +1,51 @@
> +Davinci SPI controller device bindings
> +
> +Required properties:
> +- #address-cells: number of cells required to define a chip select
> +	address on the SPI bus. Should be set to 1.
> +- #size-cells: should be zero.
> +- compatible:
> +	- "ti,davinci-spi-v1" for SPI version 1.0
> +	- "ti,davinci-spi-v2" for SPI version 2.0

It's better to use a specific chip name than some anonymous "v1" or "v2"
(unless you can point me at some hardware documentation that actually
uses those names).

> +- reg: Offset and length of SPI controller register space
> +- ti,davinci-spi-num-cs: Number of chip selects

Simply "num-cs" is sufficient here. There is now a common binding for
the number of chip select lines.

Otherwise the patch and the binding look fine to me.

g.

      reply	other threads:[~2012-12-05 23:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-03 18:38 [PATCH v1 0/1] spi: davinci: add OF support for the spi controller Murali Karicheri
     [not found] ` <1354559918-15105-1-git-send-email-m-karicheri2-l0cyMroinI0@public.gmane.org>
2012-12-03 18:38   ` [PATCH v1 1/1] " Murali Karicheri
2012-12-05 23:49     ` Grant Likely [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=20121205234947.0EB3D3E0E22@localhost \
    --to=grant.likely@secretlab.ca \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-keystone@list.ti.com \
    --cc=m-karicheri2@ti.com \
    --cc=rob.herring@calxeda.com \
    --cc=rob@landley.net \
    --cc=spi-devel-general@lists.sourceforge.net \
    /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).