From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms+renesas@verge.net.au>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Cc: Magnus Damm <magnus.damm@gmail.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-sh@vger.kernel.org
Subject: Re: [PATCH] rcar_jpu: add fallback compatibility string
Date: Tue, 8 Dec 2015 15:39:09 +0300 [thread overview]
Message-ID: <5666CF6D.70802@cogentembedded.com> (raw)
In-Reply-To: <1449553349-20458-1-git-send-email-horms+renesas@verge.net.au>
Hello.
On 12/8/2015 8:42 AM, Simon Horman wrote:
> Add fallback compatibility string.
> This is in keeping with the fallback scheme being adopted wherever
> appropriate for drivers for Renesas SoCs.
>
> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> ---
> Documentation/devicetree/bindings/media/renesas,jpu.txt | 13 +++++++------
> drivers/media/platform/rcar_jpu.c | 1 +
> 2 files changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/media/renesas,jpu.txt b/Documentation/devicetree/bindings/media/renesas,jpu.txt
> index 0cb94201bf92..c96de75f0089 100644
> --- a/Documentation/devicetree/bindings/media/renesas,jpu.txt
> +++ b/Documentation/devicetree/bindings/media/renesas,jpu.txt
> @@ -5,11 +5,12 @@ and decoding function conforming to the JPEG baseline process, so that the JPU
> can encode image data and decode JPEG data quickly.
>
> Required properties:
> - - compatible: should containg one of the following:
> - - "renesas,jpu-r8a7790" for R-Car H2
> - - "renesas,jpu-r8a7791" for R-Car M2-W
> - - "renesas,jpu-r8a7792" for R-Car V2H
> - - "renesas,jpu-r8a7793" for R-Car M2-N
> +- compatible: "renesas,jpu-<soctype>", "renesas,jpu" as fallback.
Not "renesas,rcar[-gen2]-jpu"?
[...]
MBR, Sergei
prev parent reply other threads:[~2015-12-08 12:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 5:42 [PATCH] rcar_jpu: add fallback compatibility string Simon Horman
2015-12-08 12:39 ` Sergei Shtylyov [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=5666CF6D.70802@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=devicetree@vger.kernel.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-media@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mchehab@osg.samsung.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).