devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	alsa-devel@alsa-project.org, linux-sh@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 1/5] ASoC: sh: fsi: Document SoC-specific bindings
Date: Tue, 11 Nov 2014 09:24:59 +0900	[thread overview]
Message-ID: <20141111002458.GE29665@verge.net.au> (raw)
In-Reply-To: <1415646044-4168-2-git-send-email-geert+renesas@glider.be>

On Mon, Nov 10, 2014 at 08:00:40PM +0100, Geert Uytterhoeven wrote:
> The documentation only mentioned the generic fallback compatible
> property.
> Add the missing SoC-specific compatible properties, some of which are
> already in use.
> 
> Also fix a small typo, while we're at it.
> 
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>

Acked-by: Simon Horman <horms+renesas@verge.net.au>

> ---
>  Documentation/devicetree/bindings/sound/renesas,fsi.txt | 9 +++++++--
>  1 file changed, 7 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/sound/renesas,fsi.txt b/Documentation/devicetree/bindings/sound/renesas,fsi.txt
> index c5be003f413e3aa3..0d0ab51105b01ece 100644
> --- a/Documentation/devicetree/bindings/sound/renesas,fsi.txt
> +++ b/Documentation/devicetree/bindings/sound/renesas,fsi.txt
> @@ -1,11 +1,16 @@
>  Renesas FSI
>  
>  Required properties:
> -- compatible			: "renesas,sh_fsi2" or "renesas,sh_fsi"
> +- compatible			: "renesas,fsi2-<soctype>",
> +				  "renesas,sh_fsi2" or "renesas,sh_fsi" as
> +				  fallback.
> +				  Examples with soctypes are:
> +				    - "renesas,fsi2-r8a7740" (R-Mobile A1)
> +				    - "renesas,fsi2-sh73a0" (SH-Mobile AG5)
>  - reg				: Should contain the register physical address and length
>  - interrupts			: Should contain FSI interrupt
>  
> -- fsia,spdif-connection		: FSI is connected by S/PDFI
> +- fsia,spdif-connection		: FSI is connected by S/PDIF
>  - fsia,stream-mode-support	: FSI supports 16bit stream mode.
>  - fsia,use-internal-clock	: FSI uses internal clock when master mode.
>  
> -- 
> 1.9.1
> 

  reply	other threads:[~2014-11-11  0:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10 19:00 [PATCH 0/5] ARM: shmobile: Sound binding updates Geert Uytterhoeven
2014-11-10 19:00 ` [PATCH 1/5] ASoC: sh: fsi: Document SoC-specific bindings Geert Uytterhoeven
2014-11-11  0:24   ` Simon Horman [this message]
2014-11-12 22:31   ` Mark Brown
2014-11-10 19:00 ` [PATCH 2/5] ARM: shmobile: sh73a0 dtsi: Add SoC-specific FSI2 compatible property Geert Uytterhoeven
2014-11-10 19:00 ` [PATCH 3/5] ASoC: rsnd: Document SoC-specific bindings Geert Uytterhoeven
2014-11-11  0:25   ` Simon Horman
2014-11-12 22:31   ` Mark Brown
2014-11-10 19:00 ` [PATCH 4/5] ARM: shmobile: r8a7790 dtsi: Drop "renesas,rcar_sound" compatible value Geert Uytterhoeven
2014-11-10 19:00 ` [PATCH 5/5] ARM: shmobile: r8a7791 " Geert Uytterhoeven

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=20141111002458.GE29665@verge.net.au \
    --to=horms@verge.net.au \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.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).