From: Krzysztof Kozlowski <krzk@kernel.org>
To: Aakarsh Jain <aakarsh.jain@samsung.com>, 'Rob Herring' <robh@kernel.org>
Cc: linux-fsd@tesla.com, linux-media@vger.kernel.org,
pankaj.dubey@samsung.com, linux-arm-kernel@lists.infradead.org,
dillon.minfei@gmail.com, devicetree@vger.kernel.org,
krzk+dt@kernel.org, smitha.t@samsung.com,
benjamin.gaignard@collabora.com, stanimir.varbanov@linaro.org,
jernej.skrabec@gmail.com, robh+dt@kernel.org,
aswani.reddy@samsung.com, mchehab@kernel.org,
hverkuil-cisco@xs4all.nl, mark.rutland@arm.com,
m.szyprowski@samsung.com, linux-kernel@vger.kernel.org,
alim.akhtar@samsung.com, andi@etezian.org,
andrzej.hajda@intel.com, ezequiel@vanguardiasur.com.ar,
david.plowman@raspberrypi.com
Subject: Re: [Patch v3 01/15] dt-bindings: media: s5p-mfc: Add new DT schema for MFC
Date: Tue, 18 Oct 2022 09:10:23 -0400 [thread overview]
Message-ID: <1b079ee2-d406-507c-77f9-a228d337ad71@kernel.org> (raw)
In-Reply-To: <000501d8e2df$3d209700$b761c500$@samsung.com>
On 18/10/2022 06:48, Aakarsh Jain wrote:
>>
>> codec@f1700000: clock-names:1: 'sclk_mfc' was expected
>> arch/arm/boot/dts/s5pv210-aquila.dtb
>> arch/arm/boot/dts/s5pv210-fascinate4g.dtb
>> arch/arm/boot/dts/s5pv210-galaxys.dtb
>> arch/arm/boot/dts/s5pv210-goni.dtb
>> arch/arm/boot/dts/s5pv210-smdkc110.dtb
>> arch/arm/boot/dts/s5pv210-smdkv210.dtb
>> arch/arm/boot/dts/s5pv210-torbreck.dtb
>>
>> codec@f1700000: memory-region: [[51], [52]] is too long
>> arch/arm/boot/dts/s5pv210-fascinate4g.dtb
>>
>> codec@f1700000: memory-region: [[55], [56]] is too long
>> arch/arm/boot/dts/s5pv210-galaxys.dtb
>
>
>
> Hi Rob,
>
> We tried reproducing warnings as reported above, but I am not able to see
> these warnings after running make dtbs_check & make DT_CHECKER_FLAGS=-m
> dt_binding_check.
> Packages used-
> yamllint 1.10.0
> $ dt-mk-schema --version
> 2022.9
Are you sure you are running these commands on proper config and arch?
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-10-18 13:10 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20221011125138epcas5p21b0a93e3bde26c3377e3fa7f34d86933@epcas5p2.samsung.com>
2022-10-11 12:25 ` [Patch v3 00/15] Add MFC v12 support aakarsh jain
2022-10-11 12:25 ` [Patch v3 01/15] dt-bindings: media: s5p-mfc: Add new DT schema for MFC aakarsh jain
2022-10-12 12:57 ` Krzysztof Kozlowski
2022-10-17 14:16 ` Aakarsh Jain
2022-10-18 13:09 ` Krzysztof Kozlowski
2022-10-12 13:19 ` Rob Herring
2022-10-12 13:41 ` Krzysztof Kozlowski
2022-10-18 10:48 ` Aakarsh Jain
2022-10-18 13:10 ` Krzysztof Kozlowski [this message]
2022-10-18 13:21 ` Aakarsh Jain
2022-10-18 14:07 ` Krzysztof Kozlowski
2022-10-27 10:39 ` Alim Akhtar
2022-10-28 4:37 ` Aakarsh Jain
2023-02-21 16:25 ` Krzysztof Kozlowski
2023-02-22 9:12 ` Aakarsh Jain
2022-10-11 12:25 ` [Patch v3 02/15] dt-bindings: media: s5p-mfc: Add mfcv12 variant aakarsh jain
2022-10-12 12:58 ` Krzysztof Kozlowski
2022-10-11 12:25 ` [Patch v3 03/15] media: s5p-mfc: Rename IS_MFCV10 macro aakarsh jain
2022-10-11 12:25 ` [Patch v3 04/15] media: s5p-mfc: Add initial support for MFCv12 aakarsh jain
2022-10-11 12:25 ` [Patch v3 05/15] Documention: v4l: Documentation for VP9 CIDs aakarsh jain
2022-10-18 15:05 ` Nicolas Dufresne
2022-10-21 5:26 ` Aakarsh Jain
2022-11-24 11:23 ` Hans Verkuil
2022-12-09 6:49 ` Aakarsh Jain
2022-12-14 10:22 ` Aakarsh Jain
2022-12-16 17:21 ` Nicolas Dufresne
2022-12-21 9:56 ` Aakarsh Jain
2022-12-22 19:23 ` Nicolas Dufresne
2022-10-11 12:25 ` [Patch v3 06/15] media: v4l2: Add v4l2 control IDs for VP9 encoder aakarsh jain
2022-10-11 12:25 ` [Patch v3 07/15] media: s5p-mfc: Add support " aakarsh jain
2022-10-12 9:31 ` kernel test robot
2022-10-12 16:08 ` kernel test robot
2022-10-11 12:25 ` [Patch v3 08/15] media: s5p-mfc: Add YV12 and I420 multiplanar format support aakarsh jain
2022-10-11 12:25 ` [Patch v3 09/15] media: s5p-mfc: Add support for rate controls in MFCv12 aakarsh jain
2022-10-11 12:25 ` [Patch v3 10/15] media: s5p-mfc: Add support for UHD encoding aakarsh jain
2022-10-11 12:25 ` [Patch v3 11/15] media: s5p-mfc: Add support for DMABUF for encoder aakarsh jain
2022-10-11 12:25 ` [Patch v3 12/15] media: s5p-mfc: Set context for valid case before calling try_run aakarsh jain
2022-10-11 12:25 ` [Patch v3 13/15] media: s5p-mfc: Load firmware for each run in MFCv12 aakarsh jain
2022-10-11 12:25 ` [Patch v3 14/15] media: s5p-mfc: DPB Count Independent of VIDIOC_REQBUF aakarsh jain
2022-10-11 12:25 ` [Patch v3 15/15] arm64: dts: fsd: Add MFC related DT enteries aakarsh jain
2022-10-12 4:01 ` [Patch v3 00/15] Add MFC v12 support Aakarsh Jain
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=1b079ee2-d406-507c-77f9-a228d337ad71@kernel.org \
--to=krzk@kernel.org \
--cc=aakarsh.jain@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=andi@etezian.org \
--cc=andrzej.hajda@intel.com \
--cc=aswani.reddy@samsung.com \
--cc=benjamin.gaignard@collabora.com \
--cc=david.plowman@raspberrypi.com \
--cc=devicetree@vger.kernel.org \
--cc=dillon.minfei@gmail.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jernej.skrabec@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fsd@tesla.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=pankaj.dubey@samsung.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=smitha.t@samsung.com \
--cc=stanimir.varbanov@linaro.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