From: Paul Cercueil <paul@crapouillou.net>
To: Rob Herring <robh@kernel.org>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
od@zcrc.me, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/5] dt-bindings: Document JZ47xx VPU auxiliary processor
Date: Fri, 13 Dec 2019 22:27:38 +0100 [thread overview]
Message-ID: <1576272458.3.4@crapouillou.net> (raw)
In-Reply-To: <20191213190200.GA11267@bogus>
Hi Rob,
Le ven., déc. 13, 2019 at 13:02, Rob Herring <robh@kernel.org> a
écrit :
> On Tue, Dec 10, 2019 at 05:40:10PM +0100, Paul Cercueil wrote:
>> Inside the Video Processing Unit (VPU) of the recent JZ47xx SoCs
>> from
>> Ingenic is a second Xburst MIPS CPU very similar to the main core.
>> This document describes the devicetree bindings for this auxiliary
>> processor.
>>
>> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
>> ---
>>
>> Notes:
>> v2: Update TCSM0 address in example
>> v3: Change node name to 'video-decoder'
>> v4: Convert to YAML. I didn't add Rob's Ack on v3 because of
>> that (sorry Rob)
>>
>> .../bindings/remoteproc/ingenic,vpu.yaml | 76
>> +++++++++++++++++++
>> 1 file changed, 76 insertions(+)
>> create mode 100644
>> Documentation/devicetree/bindings/remoteproc/ingenic,vpu.yaml
>>
>> diff --git
>> a/Documentation/devicetree/bindings/remoteproc/ingenic,vpu.yaml
>> b/Documentation/devicetree/bindings/remoteproc/ingenic,vpu.yaml
>> new file mode 100644
>> index 000000000000..9f876d16a5a6
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/remoteproc/ingenic,vpu.yaml
>> @@ -0,0 +1,76 @@
>> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: "http://devicetree.org/schemas/remoteproc/ingenic,vpu.yaml#"
>> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
>> +
>> +title: Ingenic Video Processing Unit bindings
>> +
>> +description:
>> + Inside the Video Processing Unit (VPU) of the recent JZ47xx SoCs
>> from
>> + Ingenic is a second Xburst MIPS CPU very similar to the main
>> core.
>> + This document describes the devicetree bindings for this
>> auxiliary
>> + processor.
>> +
>> +maintainers:
>> + - Paul Cercueil <paul@crapouillou.net>
>> +
>> +properties:
>> + compatible:
>> + const: ingenic,jz4770-vpu-rproc
>> +
>> + reg:
>> + items:
>> + - description: aux registers
>> + - description: tcsm0 registers
>> + - description: tcsm1 registers
>> + - description: sram registers
>> +
>> + reg-names:
>> + items:
>> + - const: aux
>> + - const: tcsm0
>> + - const: tcsm1
>> + - const: sram
>> +
>> + clocks:
>> + items:
>> + - description: aux clock
>> + - description: vpu clock
>> +
>> + clock-names:
>> + items:
>> + - const: aux
>> + - const: vpu
>> +
>> + interrupts:
>> + description: VPU hardware interrupt
>> +
>> +required:
>> + - compatible
>> + - reg
>> + - reg-names
>> + - clocks
>> + - clock-names
>> + - interrupts
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> + - |
>> + vpu: video-decoder@132a0000 {
>> + compatible = "ingenic,jz4770-vpu-rproc";
>> +
>> + reg = <0x132a0000 0x20 /* AUX */
>> + 0x132b0000 0x4000 /* TCSM0 */
>> + 0x132c0000 0xc000 /* TCSM1 */
>> + 0x132f0000 0x7000 /* SRAM */
>> + >;
>> + reg-names = "aux", "tcsm0", "tcsm1", "sram";
>> +
>> + clocks = <&cgu JZ4770_CLK_AUX>, <&cgu JZ4770_CLK_VPU>;
>
> Examples are built now by 'make dt_binding_check' and this fails. You
> need to add the include for these defines.
Strange, "make dt_binding_check" does not complain here about this file
with your latest dt-schema tool and Linux 5.5-rc1.
>
> Also, the schema should complain after that on 'reg'. You need to <>
> each entry (addr and size).
Ok.
-Paul
>
>> + clock-names = "aux", "vpu";
>> +
>> + interrupt-parent = <&cpuintc>;
>> + interrupts = <3>;
>> + };
>> --
>> 2.24.0
>>
prev parent reply other threads:[~2019-12-13 21:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 16:40 [PATCH v4 1/5] dt-bindings: Document JZ47xx VPU auxiliary processor Paul Cercueil
2019-12-10 16:40 ` [PATCH v4 2/5] remoteproc: Add device-managed variants of rproc_alloc/rproc_add Paul Cercueil
2019-12-12 9:43 ` Fabien DESSENNE
2019-12-14 22:27 ` Paul Cercueil
2020-01-20 19:45 ` Bjorn Andersson
2019-12-16 10:46 ` Clément Leger
2019-12-16 13:41 ` Paul Cercueil
2020-01-20 20:07 ` Bjorn Andersson
2019-12-10 16:40 ` [PATCH v4 3/5] remoteproc: Add prepare/unprepare callbacks Paul Cercueil
2019-12-12 10:03 ` Fabien DESSENNE
2019-12-14 22:30 ` Paul Cercueil
2019-12-16 8:42 ` Clément Leger
2019-12-16 16:16 ` Clément Leger
2019-12-17 10:21 ` Fabien DESSENNE
2019-12-21 20:20 ` Bjorn Andersson
2020-01-15 21:15 ` Paul Cercueil
2020-01-20 20:19 ` Bjorn Andersson
2020-01-21 10:24 ` Arnaud POULIQUEN
2019-12-10 16:40 ` [PATCH v4 4/5] remoteproc: ingenic: Added remoteproc driver Paul Cercueil
2019-12-10 16:40 ` [PATCH v4 5/5] MAINTAINERS: Add myself as reviewer for Ingenic rproc driver Paul Cercueil
2019-12-13 19:02 ` [PATCH v4 1/5] dt-bindings: Document JZ47xx VPU auxiliary processor Rob Herring
2019-12-13 21:27 ` Paul Cercueil [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=1576272458.3.4@crapouillou.net \
--to=paul@crapouillou.net \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=od@zcrc.me \
--cc=ohad@wizery.com \
--cc=robh@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).