From: Ezequiel Garcia <ezequiel@collabora.com>
To: Johan Jonker <jbx6244@gmail.com>, heiko@sntech.de
Cc: devicetree@vger.kernel.org, hverkuil@xs4all.nl,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-rockchip@lists.infradead.org, mark.rutland@arm.com,
robh@kernel.org
Subject: Re: [PATCH v4] dt-bindings: rockchip-vpu: Convert bindings to json-schema
Date: Mon, 20 Apr 2020 23:59:33 -0300 [thread overview]
Message-ID: <2d1da0b9d857c5607c989be85a04c9d7d9d19b38.camel@collabora.com> (raw)
In-Reply-To: <12f6d7cf-6af6-4f54-3188-65e73b703a72@gmail.com>
Hey Johan,
On Mon, 2020-04-20 at 15:33 +0200, Johan Jonker wrote:
> Hi Heiko,
>
> This patch was applied by the media people Hans and Ezequil without note
> and test I think.
>
I did test it, but I guess something felt thru the cracks.
If you'd be kind enough to submit a patch, that would be lovely.
Thanks!
Ezequiel
> make ARCH=arm64 dtbs_check
> DT_SCHEMA_FILES=Documentation/devicetree/bindings/media/rockchip-vpu.yaml
>
> Errors for example:
>
> DTC arch/arm64/boot/dts/rockchip/rk3328-evb.dt.yaml
> CHECK arch/arm64/boot/dts/rockchip/rk3328-evb.dt.yaml
> arch/arm64/boot/dts/rockchip/rk3328-evb.dt.yaml: video-codec@ff350000:
> interrupts: [[0, 9, 4]] is too short
> arch/arm64/boot/dts/rockchip/rk3328-evb.dt.yaml: video-codec@ff350000:
> interrupt-names: ['vdpu'] is too short
> arch/arm64/boot/dts/rockchip/rk3328-evb.dt.yaml: video-codec@ff350000:
> interrupt-names:0: 'vepu' was expected
>
> See:
> https://lore.kernel.org/lkml/20200403124316.5445-1-jbx6244@gmail.com/
>
> + interrupts:
> + minItems: 1
> + maxItems: 2
> +
> + interrupt-names:
> + oneOf:
> + - const: vdpu
> + - items:
> + - const: vepu
> + - const: vdpu
>
> Vs.:
>
>
> + interrupts:
> + maxItems: 2
> +
> + interrupt-names:
> + items:
> + - const: vepu
> + - const: vdpu
next prev parent reply other threads:[~2020-04-21 2:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 21:34 [PATCH v3 0/7] hantro: set of small cleanups and fixes Ezequiel Garcia
2020-03-25 21:34 ` [PATCH v3 1/7] v4l2-mem2mem: return CAPTURE buffer first Ezequiel Garcia
2020-03-25 21:34 ` [PATCH v3 2/7] hantro: Set buffers' zeroth plane payload in .buf_prepare Ezequiel Garcia
2020-03-25 21:34 ` [PATCH v3 3/7] hantro: Use v4l2_m2m_buf_done_and_job_finish Ezequiel Garcia
2020-03-25 21:34 ` [PATCH v3 4/7] hantro: Remove unneeded hantro_dec_buf_finish Ezequiel Garcia
2020-03-25 21:34 ` [PATCH v3 5/7] hantro: Move H264 motion vector calculation to a helper Ezequiel Garcia
2020-03-25 21:34 ` [PATCH v3 6/7] hantro: Refactor for V4L2 API spec compliancy Ezequiel Garcia
2020-03-25 21:34 ` [PATCH v3 7/7] dt-bindings: rockchip-vpu: Convert bindings to json-schema Ezequiel Garcia
2020-03-26 16:55 ` Rob Herring
2020-03-26 19:08 ` Ezequiel Garcia
2020-03-26 16:59 ` Rob Herring
2020-03-26 19:09 ` Ezequiel Garcia
2020-03-26 19:13 ` [PATCH v4] " Ezequiel Garcia
2020-03-27 3:05 ` Rob Herring
2020-04-20 13:33 ` Johan Jonker
2020-04-21 2:59 ` Ezequiel Garcia [this message]
2020-04-21 13:19 ` Johan Jonker
2020-04-21 13:36 ` Johan Jonker
2020-04-21 13:44 ` Hans Verkuil
2020-04-21 13:52 ` Ezequiel Garcia
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=2d1da0b9d857c5607c989be85a04c9d7d9d19b38.camel@collabora.com \
--to=ezequiel@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=hverkuil@xs4all.nl \
--cc=jbx6244@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.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
all inboxes | Powered by JetHome®