From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Jernej Škrabec" <jernej.skrabec@gmail.com>,
mchehab@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, wens@csie.org,
samuel@sholland.org
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] media: dt-bindings: allwinner: video-engine: Fix number of IOMMU channels
Date: Fri, 18 Nov 2022 09:09:01 +0100 [thread overview]
Message-ID: <b6cbbbe5-c1e9-a2fc-dd9d-9076d268a2a0@linaro.org> (raw)
In-Reply-To: <3385828.QJadu78ljV@jernej-laptop>
On 17/11/2022 21:31, Jernej Škrabec wrote:
> Dne četrtek, 17. november 2022 ob 14:13:00 CET je Krzysztof Kozlowski
> napisal(a):
>> On 17/11/2022 07:07, Jernej Skrabec wrote:
>>> Cedrus (video engine) on Allwinner H6 actually uses two IOMMU channel,
>>> not just one. However, Cedrus on SoCs like D1 only uses one channel.
>>>
>>> Allow up to 2 IOMMU channels.
>>>
>>> Fixes: 62a8ccf3a248 ("arm64: dts: allwinner: h6: Fix Cedrus IOMMU usage")
>>> Signed-off-by: Jernej Skrabec <jernej.skrabec@gmail.com>
>>> ---
>>>
>>> .../bindings/media/allwinner,sun4i-a10-video-engine.yaml | 3 ++-
>>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>>
>>> diff --git
>>> a/Documentation/devicetree/bindings/media/allwinner,sun4i-a10-video-engin
>>> e.yaml
>>> b/Documentation/devicetree/bindings/media/allwinner,sun4i-a10-video-engin
>>> e.yaml index 541325f900a1..6446004d59d9 100644
>>> ---
>>> a/Documentation/devicetree/bindings/media/allwinner,sun4i-a10-video-engin
>>> e.yaml +++
>>> b/Documentation/devicetree/bindings/media/allwinner,sun4i-a10-video-engin
>>> e.yaml>
>>> @@ -55,7 +55,8 @@ properties:
>>> description: Phandle to the device SRAM
>>>
>>> iommus:
>>> - maxItems: 1
>>> + minItems: 1
>>> + maxItems: 2
>>
>> You have several compatibles in the file, so usually this is further
>> constrained per each variant in allOf:if:then:.
>
> Usually, yes. But this whole binding would need update. It has a few optional
> properties and none of them is tied to any compatible. Additionally, if I do
> it as you suggest, then Robs automatic test will report the issue, because
> existing H6 based boards won't match this binding anymore. I would much rather
> send follow up patch which clears up all optional properties.
I don't understand last argument. It's basically like saying - I keep
bindings not really correct, because otherwise I would see warnings and
I would need to fix them.
If this can be constrained per variant, constrain it and then fix the
boards.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-11-18 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 6:07 [PATCH v2 0/2] arm64: allwinner: h6: Add second IOMMU reference to Cedrus Jernej Skrabec
2022-11-17 6:07 ` [PATCH v2 1/2] media: dt-bindings: allwinner: video-engine: Fix number of IOMMU channels Jernej Skrabec
2022-11-17 13:13 ` Krzysztof Kozlowski
2022-11-17 20:31 ` Jernej Škrabec
2022-11-18 8:09 ` Krzysztof Kozlowski [this message]
2022-11-17 6:07 ` [PATCH v2 2/2] arm64: dts: allwinner: h6: Fix Cedrus " Jernej Skrabec
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=b6cbbbe5-c1e9-a2fc-dd9d-9076d268a2a0@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--cc=wens@csie.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).