From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Simon Horman <horms@verge.net.au>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Mikhail Ulyanov <mikhail.ulyanov@cogentembedded.com>,
Magnus Damm <magnus.damm@gmail.com>,
Mauro Carvalho Chehab <m.chehab@samsung.com>,
Rob Herring <robh+dt@kernel.org>,
Grant Likely <grant.likely@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Hans Verkuil <hans.verkuil@cisco.com>,
Linux-sh list <linux-sh@vger.kernel.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 6/6] devicetree: bindings: Document Renesas JPEG Processing Unit.
Date: Wed, 27 Aug 2014 08:06:10 +0200 [thread overview]
Message-ID: <1636392.ZpHdXzEmup@avalon> (raw)
In-Reply-To: <20140827051501.GB1343@verge.net.au>
On Wednesday 27 August 2014 14:15:01 Simon Horman wrote:
> On Tue, Aug 26, 2014 at 11:27:43AM +0200, Geert Uytterhoeven wrote:
> > On Tue, Aug 26, 2014 at 11:01 AM, Simon Horman <horms@verge.net.au> wrote:
> >> On Tue, Aug 26, 2014 at 10:03:34AM +0200, Geert Uytterhoeven wrote:
> >>> On Tue, Aug 26, 2014 at 1:57 AM, Simon Horman wrote:
> >>>> On Mon, Aug 25, 2014 at 02:59:46PM +0200, Geert Uytterhoeven wrote:
> >>>>> On Mon, Aug 25, 2014 at 2:35 PM, Mikhail Ulyanov wrote:
> >>>>>> + - compatible: should containg one of the following:
> >>>>>> + - "renesas,jpu-r8a7790" for R-Car H2
> >>>>>> + - "renesas,jpu-r8a7791" for R-Car M2
> >>>>>> + - "renesas,jpu-gen2" for R-Car second
> >>>>>> generation
> >>>>>
> >>>>> Isn't "renesas,jpu-gen2" meant as a fallback?
> >>>>>
> >>>>> I.e. the DTS should have one of '7790 and '7791, AND the gen2
> >>>>> fallback, so we can make the driver match against '7790 and '7791 is
> >>>>> we find out about an incompatibility.
> >>>>
> >>>> Is there a document that clearly states that there is such a thing
> >>>> as jpu-gen2 in hardware? If not I would prefer not to add a binding
> >>>> for it.
> >>>
> >>> We do have a document that describes the "JPEG Processing Unit (JPU)",
> >>> as found in the following members of the "Second Generation R-Car
> >>> Series Products": "R-Car H2", "R-Car M2-W", "R-Car M2-N", and "R-Car
> >>> V2H".
> >>
> >> Oh, that is nice :)
> >>
> >> From my point of view that ticks a lot of boxes.
> >> But I wonder if we can come up with a better name than jpu,-gen2.
> >
> > "jpu-rcar-gen2"?
>
> I guess that is a slight improvement.
>
> But suppose some gen2 SoC exists or comes to exists that
> has different IP. Suppose there is more than one that same
> the same IP that is different to the SoCs covered by the
> existing compat string?
That's exactly the information we need to request from the hardware team :-)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-08-27 6:06 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 12:50 [PATCH 0/6] R-Car JPEG Processing Unit Mikhail Ulyanov
2014-08-19 12:50 ` [PATCH 1/6] V4L2: Add Renesas R-Car JPEG codec driver Mikhail Ulyanov
2014-08-19 13:37 ` Hans Verkuil
2014-08-22 13:39 ` Mikhail Ulianov
2014-08-22 17:03 ` Hans Verkuil
2014-08-25 12:29 ` [PATCH v2 " Mikhail Ulyanov
2014-08-25 12:39 ` Hans Verkuil
2014-08-25 12:49 ` Hans Verkuil
2014-09-21 17:56 ` Sergei Shtylyov
2014-09-21 17:56 ` Sergei Shtylyov
2014-09-23 13:31 ` Kamil Debski
2014-09-25 12:49 ` Sergei Shtylyov
2014-09-26 14:01 ` Laurent Pinchart
2014-09-23 14:02 ` [PATCH " Geert Uytterhoeven
2014-08-19 12:50 ` [PATCH 2/6] ARM: shmobile: r8a7790: Add JPU clock dt and CPG define Mikhail Ulyanov
2014-08-20 23:07 ` Laurent Pinchart
2014-08-22 1:57 ` Simon Horman
2014-08-19 12:50 ` [PATCH 3/6] ARM: shmobile: r8a7790: Add JPU device node Mikhail Ulyanov
2014-08-22 1:54 ` [3/6] " Simon Horman
2014-08-19 12:50 ` [PATCH 4/6] ARM: shmobile: r8a7791: Add JPU clock dt and CPG define Mikhail Ulyanov
2014-08-20 23:07 ` Laurent Pinchart
2014-08-22 1:56 ` Simon Horman
2014-08-19 12:50 ` [PATCH 5/6] ARM: shmobile: r8a7791: Add JPU device node Mikhail Ulyanov
2014-08-19 12:50 ` [PATCH 6/6] devicetree: bindings: Document Renesas JPEG Processing Unit Mikhail Ulyanov
2014-08-20 23:01 ` Laurent Pinchart
2014-08-22 14:20 ` Mikhail Ulianov
2014-08-25 9:49 ` Laurent Pinchart
2014-08-25 12:35 ` [PATCH v2 " Mikhail Ulyanov
2014-08-25 12:59 ` Geert Uytterhoeven
2014-08-25 23:57 ` Simon Horman
2014-08-26 0:02 ` Laurent Pinchart
2014-08-26 2:42 ` Simon Horman
2014-09-24 13:38 ` Mikhail Ulianov
2014-08-26 8:03 ` Geert Uytterhoeven
2014-08-26 9:01 ` Simon Horman
2014-08-26 9:27 ` Geert Uytterhoeven
2014-08-27 5:15 ` Simon Horman
2014-08-27 6:06 ` Laurent Pinchart [this message]
2014-08-27 6:16 ` Simon Horman
-- strict thread matches above, loose matches on Subject: below --
2014-08-26 0:17 Ray
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=1636392.ZpHdXzEmup@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=grant.likely@linaro.org \
--cc=hans.verkuil@cisco.com \
--cc=horms@verge.net.au \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-media@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=mikhail.ulyanov@cogentembedded.com \
--cc=robh+dt@kernel.org \
/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).