linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nguyen An Hoan <na-hoan@jinso.co.jp>
To: linux-renesas-soc@vger.kernel.org,
	ramesh.shanmugasundaram@bp.renesas.com, horms@verge.net.au
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	kuninori.morimoto.gx@renesas.com, magnus.damm@gmail.com,
	yoshihiro.shimoda.uh@renesas.com, h-inayoshi@jinso.co.jp,
	na-hoan@jinso.co.jp, cv-dong@jinso.co.jp
Subject: [PATCH 1/2] media: dt-bindings: media: Add r8a77965 DRIF bindings
Date: Tue, 23 Apr 2019 19:09:58 +0900	[thread overview]
Message-ID: <1556014199-12698-1-git-send-email-na-hoan@jinso.co.jp> (raw)

From: Hoan Nguyen An <na-hoan@jinso.co.jp>

Add r8a77965 DRIF bindings.

Signed-off-by: Hoan Nguyen An <na-hoan@jinso.co.jp>
---
 Documentation/devicetree/bindings/media/renesas,drif.txt | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/devicetree/bindings/media/renesas,drif.txt b/Documentation/devicetree/bindings/media/renesas,drif.txt
index 0d8974a..16cdee3 100644
--- a/Documentation/devicetree/bindings/media/renesas,drif.txt
+++ b/Documentation/devicetree/bindings/media/renesas,drif.txt
@@ -41,6 +41,7 @@ Required properties of an internal channel:
 -------------------------------------------
 - compatible:	"renesas,r8a7795-drif" if DRIF controller is a part of R8A7795 SoC.
 		"renesas,r8a7796-drif" if DRIF controller is a part of R8A7796 SoC.
+		"renesas,r8a77965-drif" if DRIF controller is a part of R8A77965 SoC.
 		"renesas,rcar-gen3-drif" for a generic R-Car Gen3 compatible device.
 
 		When compatible with the generic version, nodes must list the
-- 
2.7.4


             reply	other threads:[~2019-04-23 10:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23 10:09 Nguyen An Hoan [this message]
2019-04-23 10:09 ` [PATCH 2/2] arm64: dts: r8a77965: Add DRIF support Nguyen An Hoan
2019-04-23 10:50 ` [PATCH 1/2] media: dt-bindings: media: Add r8a77965 DRIF bindings Simon Horman
2019-06-06 13:32   ` Simon Horman

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=1556014199-12698-1-git-send-email-na-hoan@jinso.co.jp \
    --to=na-hoan@jinso.co.jp \
    --cc=cv-dong@jinso.co.jp \
    --cc=devicetree@vger.kernel.org \
    --cc=h-inayoshi@jinso.co.jp \
    --cc=horms@verge.net.au \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=ramesh.shanmugasundaram@bp.renesas.com \
    --cc=yoshihiro.shimoda.uh@renesas.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).