From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Konstantin Kozhevnikov
<Konstantin.Kozhevnikov@cogentembedded.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: Re: [PATCH v5] media: platform: Renesas IMR driver
Date: Wed, 03 May 2017 12:04:22 +0300 [thread overview]
Message-ID: <1692660.6KI7CDrx15@avalon> (raw)
In-Reply-To: <CAMuHMdWE+o3gsFnxqBcvrD=PfHHb0i9uK3tsfWaNxfuhK3SNKg@mail.gmail.com>
Hi Geert,
On Wednesday 03 May 2017 09:22:00 Geert Uytterhoeven wrote:
> On Tue, May 2, 2017 at 11:17 PM, Laurent Pinchart wrote:
> > On Wednesday 22 Mar 2017 10:34:16 Geert Uytterhoeven wrote:
> >> On Thu, Mar 9, 2017 at 9:08 PM, Sergei Shtylyov wrote:
> >>> --- /dev/null
> >>> +++ media_tree/Documentation/devicetree/bindings/media/rcar_imr.txt
> >>> @@ -0,0 +1,27 @@
> >>> +Renesas R-Car Image Renderer (Distortion Correction Engine)
> >>> +-----------------------------------------------------------
> >>> +
> >>> +The image renderer, or the distortion correction engine, is a drawing
> >>> processor
> >>> +with a simple instruction system capable of referencing video capture
> >>> data or
> >>> +data in an external memory as 2D texture data and performing texture
> >>> mapping
> >>> +and drawing with respect to any shape that is split into triangular
> >>> objects.
> >>> +
> >>> +Required properties:
> >>> +
> >>> +- compatible: "renesas,<soctype>-imr-lx4", "renesas,imr-lx4" as a
> >>> fallback for
> >>> + the image renderer light extended 4 (IMR-LX4) found in the R-Car
> >>> gen3 SoCs,
> >>> + where the examples with <soctype> are:
> >>> + - "renesas,r8a7795-imr-lx4" for R-Car H3,
> >>> + - "renesas,r8a7796-imr-lx4" for R-Car M3-W.
> >>
> >> Laurent: what do you think about the need for SoC-specific compatible
> >> values for the various IM* blocks?
> >
> > There's no documented IP core version register, but when dumping all
> > configuration registers on H3 and M3-W I noticed that register 0x002c, not
> > documented in the datasheet, reads 0x14060514 on all four IMR instances in
> > H3, and 0x20150505 on both instances in M3-W.
> >
> > This looks like a version register to me. If my assumption is correct, we
> > could do without any SoC-specific compatible string.
>
> I read this assumed version registers on all R-Car SoCs, after writing
> zero to 0xe6150990 (SMSTPCR8).
>
> IMR-X2 on R-Car H2: 0x12072009
> IMR-LSX2 on R-Car H2: 0x12072009
> IMR-LSX3 on R-Car V2H: 0x13052617
> IMR-LX2 on R-Car M2-W: 0x12072009
> IMR-LX2 on R-Car M2-N: 0x12072009
> IMR-LX2 on R-Car E2: 0x13091909
> IMR-LX3 on R-Car V2H: 0x13052617
>
> Note that several IDs are the same, but you know the type from the
> compatible value.
>
> It would be good to get confirmation from the hardware team that this is
> indeed a version register.
Thank you for checking.
Morimoto-san, do you think there are still people alive in the Gen2 hardware
team who could provide the information ? :-) If not, information restricted to
Gen3 would still be useful.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2017-05-03 9:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 20:08 [PATCH v5] media: platform: Renesas IMR driver Sergei Shtylyov
2017-03-16 21:18 ` Rob Herring
[not found] ` <20170309200818.786255823-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2017-03-17 14:24 ` Hans Verkuil
2017-06-24 20:56 ` Sergei Shtylyov
2017-03-22 9:34 ` Geert Uytterhoeven
[not found] ` <CAMuHMdV5-aMx4KuqShm47XtORJK8rMKzw6FUs2Hjsxia+jPfxg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-02 21:17 ` Laurent Pinchart
2017-05-03 7:22 ` Geert Uytterhoeven
2017-05-03 9:04 ` Laurent Pinchart [this message]
2017-05-08 0:47 ` Kuninori Morimoto
2017-06-07 7:26 ` Hans Verkuil
[not found] ` <87be3653-66f0-deda-f862-b52a2de23ecf-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org>
2017-06-07 12:02 ` Sergei Shtylyov
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=1692660.6KI7CDrx15@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=Konstantin.Kozhevnikov@cogentembedded.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sergei.shtylyov@cogentembedded.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