| Message ID | 1408452653-14067-7-git-send-email-mikhail.ulyanov@cogentembedded.com (mailing list archive) |
|---|---|
| State | Not Applicable, archived |
| Headers |
Received: from mail.tu-berlin.de ([130.149.7.33]) by www.linuxtv.org with esmtp (Exim 4.72) (envelope-from <linux-media-owner@vger.kernel.org>) id 1XJiuq-0000M5-GN; Tue, 19 Aug 2014 14:53:32 +0200 X-tubIT-Incoming-IP: 209.132.180.67 Received: from vger.kernel.org ([209.132.180.67]) by mail.tu-berlin.de (exim-4.72/mailfrontend-7) with esmtp id 1XJiuo-0006aU-1t; Tue, 19 Aug 2014 14:53:32 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753094AbaHSMx0 (ORCPT <rfc822;mkrufky@linuxtv.org> + 1 other); Tue, 19 Aug 2014 08:53:26 -0400 Received: from mail-lb0-f180.google.com ([209.85.217.180]:64934 "EHLO mail-lb0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753012AbaHSMxK (ORCPT <rfc822;linux-media@vger.kernel.org>); Tue, 19 Aug 2014 08:53:10 -0400 Received: by mail-lb0-f180.google.com with SMTP id v6so5359641lbi.39 for <linux-media@vger.kernel.org>; Tue, 19 Aug 2014 05:53:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references; bh=6LKCxR/nVZ5iYfSUYDi+tE1dUD/kwsAaOIoVxv6Fnrk=; b=k6ABzZT3qPBAr25znET5uDn9eVf5ADTHMduq0+bhgBR1MS9D5VejNOj/fBQsnwGAp2 aJKr55BNsnDmjcMM7MNjkSYS/Ie9cIr8bTq5pJGHRkrDyIV9QO9poAW98r61r/0Fqnfo osytcjm3g/ek3YFsEWPyoggjIGCkcRT4hg2wbYbEhu9gK1cev8Ix8ZYk9WzuQuLnxmde E8GKJt5hhObwbuUYG3RvtHkqfNyL8heFjWNH0o2kbzJQbg/jqnX/RfM05ZskPg+ae84O QzAL3bepnpW3LzaUoKhTG6Y/LpRbf1Z8zGJPZtrzV+ERGCHRAbtyJcOCmuzIdEfebRx8 r7cA== X-Gm-Message-State: ALoCoQmgwziFxABUfwu83dCgRSATuOU2BVOWexUF7zGmbAx1nFLiTjKVTDcBtzy6hE4pukl7zWpz X-Received: by 10.152.3.199 with SMTP id e7mr36388541lae.35.1408452789170; Tue, 19 Aug 2014 05:53:09 -0700 (PDT) Received: from localhost.localdomain (178-16-155-142.obit.ru. [178.16.155.142]) by mx.google.com with ESMTPSA id m9sm32023870lbd.28.2014.08.19.05.53.08 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 19 Aug 2014 05:53:08 -0700 (PDT) From: Mikhail Ulyanov <mikhail.ulyanov@cogentembedded.com> To: m.chehab@samsung.com, horms@verge.net.au, magnus.damm@gmail.com, robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com Cc: laurent.pinchart@ideasonboard.com, linux-sh@vger.kernel.org, linux-media@vger.kernel.org, devicetree@vger.kernel.org, Mikhail Ulyanov <mikhail.ulyanov@cogentembedded.com> Subject: [PATCH 6/6] devicetree: bindings: Document Renesas JPEG Processing Unit. Date: Tue, 19 Aug 2014 16:50:53 +0400 Message-Id: <1408452653-14067-7-git-send-email-mikhail.ulyanov@cogentembedded.com> X-Mailer: git-send-email 2.1.0.rc1 In-Reply-To: <1408452653-14067-1-git-send-email-mikhail.ulyanov@cogentembedded.com> References: <1408452653-14067-1-git-send-email-mikhail.ulyanov@cogentembedded.com> Sender: linux-media-owner@vger.kernel.org Precedence: bulk List-ID: <linux-media.vger.kernel.org> X-Mailing-List: linux-media@vger.kernel.org X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.8.19.124517 X-PMX-Spam: Gauge=IIIIIIII, Probability=8%, Report=' MULTIPLE_RCPTS 0.1, HTML_00_01 0.05, HTML_00_10 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_1600_1699 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, URI_ENDS_IN_HTML 0, __ANY_URI 0, __CP_MEDIA_BODY 0, __CP_URI_IN_BODY 0, __DATE_TZ_RU 0, __HAS_FROM 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __HAS_X_MAILING_LIST 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MULTIPLE_RCPTS_CC_X2 0, __MULTIPLE_RCPTS_TO_X5 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __TO_NO_NAME 0, __URI_NO_WWW 0, __URI_NS , __YOUTUBE_RCVD 0' |
Commit Message
Mikhail Ulyanov
Aug. 19, 2014, 12:50 p.m. UTC
Signed-off-by: Mikhail Ulyanov <mikhail.ulyanov@cogentembedded.com>
---
.../devicetree/bindings/media/renesas,jpu.txt | 23 ++++++++++++++++++++++
1 file changed, 23 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/renesas,jpu.txt
Comments
Hi Mikhail, Thank you for the patch. On Tuesday 19 August 2014 16:50:53 Mikhail Ulyanov wrote: > Signed-off-by: Mikhail Ulyanov <mikhail.ulyanov@cogentembedded.com> > --- > .../devicetree/bindings/media/renesas,jpu.txt | 23 +++++++++++++++++++ > 1 file changed, 23 insertions(+) > create mode 100644 Documentation/devicetree/bindings/media/renesas,jpu.txt > > diff --git a/Documentation/devicetree/bindings/media/renesas,jpu.txt > b/Documentation/devicetree/bindings/media/renesas,jpu.txt new file mode > 100644 > index 0000000..44b07df > --- /dev/null > +++ b/Documentation/devicetree/bindings/media/renesas,jpu.txt > @@ -0,0 +1,23 @@ > +* Renesas VSP1 Video Processing Engine Copy & paste ? :-) > + > +The JPEG processing unit (JPU) incorporates the JPEG codec with an encoding > +and decoding function conforming to the JPEG baseline process, so that the > JPU > +can encode image data and decode JPEG data quickly. > +It can be found in the Renesas R-Car first and second generation SoCs. Is there a difference between the first and second generation JPUs ? > + > +Required properties: > + - compatible: should containg one of the following: > + - "renesas,jpu-r8a7790" for R-Car H2 > + - "renesas,jpu-r8a7791" for R-Car M2 How about adding a "renesas,jpu" generic compatible, and listing both the SoC- specific and the generic values (in that order) in the compatible property ? > + - reg: Base address and length of the registers block for the JPU. > + - interrupts: JPU interrupt specifier. > + - clocks: A phandle + clock-specifier pair for the JPU functional clock. > + > +Example: R8A7790 (R-Car H2) JPU node > + jpeg-codec@fe980000 { > + compatible = "renesas,jpu-r8a7790"; > + reg = <0 0xfe980000 0 0x10300>; > + interrupts = <0 272 IRQ_TYPE_LEVEL_HIGH>; > + clocks = <&mstp1_clks R8A7790_CLK_JPU>; > + };
Hi Laurent, Thanks for your comments. On Thu, 21 Aug 2014 01:01:43 +0200 Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote: > Hi Mikhail, > > Thank you for the patch. > > On Tuesday 19 August 2014 16:50:53 Mikhail Ulyanov wrote: > > Signed-off-by: Mikhail Ulyanov <mikhail.ulyanov@cogentembedded.com> > > --- > > .../devicetree/bindings/media/renesas,jpu.txt | 23 > > +++++++++++++++++++ 1 file changed, 23 insertions(+) > > create mode 100644 > > Documentation/devicetree/bindings/media/renesas,jpu.txt > > > > diff --git a/Documentation/devicetree/bindings/media/renesas,jpu.txt > > b/Documentation/devicetree/bindings/media/renesas,jpu.txt new file > > mode 100644 > > index 0000000..44b07df > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/media/renesas,jpu.txt > > @@ -0,0 +1,23 @@ > > +* Renesas VSP1 Video Processing Engine > > Copy & paste ? :-) > Yeah. Will fix it. > > + > > +The JPEG processing unit (JPU) incorporates the JPEG codec with an > > encoding +and decoding function conforming to the JPEG baseline > > process, so that the JPU > > +can encode image data and decode JPEG data quickly. > > +It can be found in the Renesas R-Car first and second generation > > SoCs. > > Is there a difference between the first and second generation JPUs ? > There should be no difference because in practice maximum supported resolution for Gen2 is 4096x4096 (not 8000x8000 as in overview section of documentation). And in Gen1 documentation(overview section) maximum supported resolution is also 4096x4096. > > + > > +Required properties: > > + - compatible: should containg one of the following: > > + - "renesas,jpu-r8a7790" for R-Car H2 > > + - "renesas,jpu-r8a7791" for R-Car M2 > > How about adding a "renesas,jpu" generic compatible, and listing both > the SoC- specific and the generic values (in that order) in the > compatible property ? > Could be a good idea, but there is no JPU in some R-Car Gen1 SoCs e.g. E1. Plus we don't have full documentation on JPU in Gen1 SoCs. So for now Gen1 is not supported. Or this doesn't matter in that case? > > + - reg: Base address and length of the registers block for the > > JPU. > > + - interrupts: JPU interrupt specifier. > > + - clocks: A phandle + clock-specifier pair for the JPU > > functional clock. + > > +Example: R8A7790 (R-Car H2) JPU node > > + jpeg-codec@fe980000 { > > + compatible = "renesas,jpu-r8a7790"; > > + reg = <0 0xfe980000 0 0x10300>; > > + interrupts = <0 272 IRQ_TYPE_LEVEL_HIGH>; > > + clocks = <&mstp1_clks R8A7790_CLK_JPU>; > > + }; > -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Mikhail, On Friday 22 August 2014 18:20:53 Mikhail Ulianov wrote: > On Thu, 21 Aug 2014 01:01:43 +0200 Laurent Pinchart wrote: > > On Tuesday 19 August 2014 16:50:53 Mikhail Ulyanov wrote: > > > Signed-off-by: Mikhail Ulyanov <mikhail.ulyanov@cogentembedded.com> > > > --- > > > > > > .../devicetree/bindings/media/renesas,jpu.txt | 23 +++++++++++++++ > > > 1 file changed, 23 insertions(+) > > > create mode 100644 > > > Documentation/devicetree/bindings/media/renesas,jpu.txt > > > > > > diff --git a/Documentation/devicetree/bindings/media/renesas,jpu.txt > > > b/Documentation/devicetree/bindings/media/renesas,jpu.txt new file > > > mode 100644 > > > index 0000000..44b07df > > > --- /dev/null > > > +++ b/Documentation/devicetree/bindings/media/renesas,jpu.txt > > > @@ -0,0 +1,23 @@ > > > +* Renesas VSP1 Video Processing Engine > > > > Copy & paste ? :-) > > Yeah. Will fix it. > > > > + > > > +The JPEG processing unit (JPU) incorporates the JPEG codec with an > > > encoding +and decoding function conforming to the JPEG baseline > > > process, so that the JPU > > > +can encode image data and decode JPEG data quickly. > > > +It can be found in the Renesas R-Car first and second generation > > > SoCs. > > > > Is there a difference between the first and second generation JPUs ? > > There should be no difference because in practice maximum supported > resolution for Gen2 is 4096x4096 (not 8000x8000 as in overview section > of documentation). And in Gen1 documentation(overview section) maximum > supported resolution is also 4096x4096. > > > > + > > > +Required properties: > > > + - compatible: should containg one of the following: > > > + - "renesas,jpu-r8a7790" for R-Car H2 > > > + - "renesas,jpu-r8a7791" for R-Car M2 > > > > How about adding a "renesas,jpu" generic compatible, and listing both > > the SoC- specific and the generic values (in that order) in the > > compatible property ? > > Could be a good idea, but there is no JPU in some R-Car Gen1 SoCs > e.g. E1. Plus we don't have full documentation on JPU in Gen1 SoCs. > So for now Gen1 is not supported. Or this doesn't matter in that case? The lack of JPU in some chips isn't an issue, but the lack of documentation for Gen1 is a problem. Let's not add a too generic compatible string in that case. I would still like to add a "renesas,jpu-gen2" compatible in addition to the SoC-specific values, but that might be frowned upon. > > > + - reg: Base address and length of the registers block for the > > > JPU. > > > + - interrupts: JPU interrupt specifier. > > > + - clocks: A phandle + clock-specifier pair for the JPU > > > functional clock. + > > > +Example: R8A7790 (R-Car H2) JPU node > > > + jpeg-codec@fe980000 { > > > + compatible = "renesas,jpu-r8a7790"; > > > + reg = <0 0xfe980000 0 0x10300>; > > > + interrupts = <0 272 IRQ_TYPE_LEVEL_HIGH>; > > > + clocks = <&mstp1_clks R8A7790_CLK_JPU>; > > > + };
diff --git a/Documentation/devicetree/bindings/media/renesas,jpu.txt b/Documentation/devicetree/bindings/media/renesas,jpu.txt new file mode 100644 index 0000000..44b07df --- /dev/null +++ b/Documentation/devicetree/bindings/media/renesas,jpu.txt @@ -0,0 +1,23 @@ +* Renesas VSP1 Video Processing Engine + +The JPEG processing unit (JPU) incorporates the JPEG codec with an encoding +and decoding function conforming to the JPEG baseline process, so that the JPU +can encode image data and decode JPEG data quickly. +It can be found in the Renesas R-Car first and second generation SoCs. + +Required properties: + - compatible: should containg one of the following: + - "renesas,jpu-r8a7790" for R-Car H2 + - "renesas,jpu-r8a7791" for R-Car M2 + + - reg: Base address and length of the registers block for the JPU. + - interrupts: JPU interrupt specifier. + - clocks: A phandle + clock-specifier pair for the JPU functional clock. + +Example: R8A7790 (R-Car H2) JPU node + jpeg-codec@fe980000 { + compatible = "renesas,jpu-r8a7790"; + reg = <0 0xfe980000 0 0x10300>; + interrupts = <0 272 IRQ_TYPE_LEVEL_HIGH>; + clocks = <&mstp1_clks R8A7790_CLK_JPU>; + };