Message ID | 20231227130812.148914-1-eugen.hristev@collabora.com (mailing list archive) |
---|---|
State | Superseded |
Headers |
Received: from sy.mirrors.kernel.org ([147.75.48.161]) by www.linuxtv.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <linux-media+bounces-3030-patchwork=linuxtv.org@vger.kernel.org>) id 1rITeP-00GeBr-GY for patchwork@linuxtv.org; Wed, 27 Dec 2023 13:08:46 +0000 Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sy.mirrors.kernel.org (Postfix) with ESMTPS id 3EA6BB215B2 for <patchwork@linuxtv.org>; Wed, 27 Dec 2023 13:08:34 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 1136444C89; Wed, 27 Dec 2023 13:08:25 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=collabora.com header.i=@collabora.com header.b="LE8nW6o9" X-Original-To: linux-media@vger.kernel.org Received: from madrid.collaboradmins.com (madrid.collaboradmins.com [46.235.227.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 493EC44C62; Wed, 27 Dec 2023 13:08:23 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=collabora.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=collabora.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1703682501; bh=jvUeOk62psQZsbMdkKVZNNNG5A+qB2Z6aEW45S/4p1Q=; h=From:To:Cc:Subject:Date:From; b=LE8nW6o9iLpxjsx2UDxC4w8bFvUiqBCbUaSLGN2QHFcV7Wvo3xQgjPQXLOdfJxYC1 e9razMUHVWO2kNDJZJA8djvpDFNJdNPgGKJ15oohl2rupU12EPGneHtvm2rwuFT8Un iRw1ay/k+rjsCP6nc0VtHVpc3LA3yA+IKVdVMGvRSTKboJqy4FuEs/LqjTZ0WgV3zG l2x3agZGwT7bEJ2muGWT+J2QP8ykOAGZqxQbQqLnL9ACZKfiHIEl72DcudVTqXklKV ck7km5lP3naUFlSAOTHnnKSgHLKfGHnzOS6YAfbVP0Elw9NUjOydzd6cDkRgJXWC4E MdXJdsUQdV6Tg== Received: from eugen-station.. (cola.collaboradmins.com [195.201.22.229]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: ehristev) by madrid.collaboradmins.com (Postfix) with ESMTPSA id C56A237801C1; Wed, 27 Dec 2023 13:08:20 +0000 (UTC) From: Eugen Hristev <eugen.hristev@collabora.com> To: bin.liu@mediatek.com, matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com, linux-media@vger.kernel.org, devicetree@vger.kernel.org Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, Eugen Hristev <eugen.hristev@collabora.com> Subject: [PATCH 1/2] dt-bindings: media: mediatek-jpeg-encoder: change max ioomus count Date: Wed, 27 Dec 2023 15:08:11 +0200 Message-Id: <20231227130812.148914-1-eugen.hristev@collabora.com> X-Mailer: git-send-email 2.34.1 Precedence: bulk X-Mailing-List: linux-media@vger.kernel.org List-Id: <linux-media.vger.kernel.org> List-Subscribe: <mailto:linux-media+subscribe@vger.kernel.org> List-Unsubscribe: <mailto:linux-media+unsubscribe@vger.kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-LSpam-Score: -4.8 (----) X-LSpam-Report: No, score=-4.8 required=5.0 tests=BAYES_00=-1.9,DKIM_SIGNED=0.1,DKIM_VALID=-0.1,DKIM_VALID_AU=-0.1,HEADER_FROM_DIFFERENT_DOMAINS=0.5,MAILING_LIST_MULTI=-1,RCVD_IN_DNSWL_MED=-2.3 autolearn=unavailable autolearn_force=no |
Series |
[1/2] dt-bindings: media: mediatek-jpeg-encoder: change max ioomus count
|
|
Commit Message
Eugen Hristev
Dec. 27, 2023, 1:08 p.m. UTC
MT8186 has 4 iommus in the list, to cope with this situation, adjust
the maxItems to 4 (instead of previous 2).
Add also minItems as 1 since iommus are mandatory, to avoid warning
on the example.
Signed-off-by: Eugen Hristev <eugen.hristev@collabora.com>
---
.../devicetree/bindings/media/mediatek-jpeg-encoder.yaml | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Comments
Il 27/12/23 14:08, Eugen Hristev ha scritto: > MT8186 has 4 iommus in the list, to cope with this situation, adjust > the maxItems to 4 (instead of previous 2). > Add also minItems as 1 since iommus are mandatory, to avoid warning > on the example. > > Signed-off-by: Eugen Hristev <eugen.hristev@collabora.com> > --- > .../devicetree/bindings/media/mediatek-jpeg-encoder.yaml | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.yaml b/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.yaml > index 37800e1908cc..60c75b9312e8 100644 > --- a/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.yaml > +++ b/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.yaml > @@ -38,7 +38,8 @@ properties: > maxItems: 1 > > iommus: > - maxItems: 2 > + minItems: 1 > + maxItems: 4 > description: | > Points to the respective IOMMU block with master port as argument, see > Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml for details. (commit title) `ioomus` is something I've never heard of before... :-P Please fix the typo, after which: Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
On Wed, Dec 27, 2023 at 03:08:11PM +0200, Eugen Hristev wrote: > MT8186 has 4 iommus in the list, to cope with this situation, adjust > the maxItems to 4 (instead of previous 2). > Add also minItems as 1 since iommus are mandatory, to avoid warning > on the example. maxItems alone means minItems is the same size. If IOMMU is required, then 'required' is where that is defined. Is there a case where 1 IOMMU is valid? If so, what h/w has this case. Rob
On 1/9/24 05:27, Rob Herring wrote: > On Wed, Dec 27, 2023 at 03:08:11PM +0200, Eugen Hristev wrote: >> MT8186 has 4 iommus in the list, to cope with this situation, adjust >> the maxItems to 4 (instead of previous 2). >> Add also minItems as 1 since iommus are mandatory, to avoid warning >> on the example. > > maxItems alone means minItems is the same size. If IOMMU is required, > then 'required' is where that is defined. Is there a case where 1 IOMMU > is valid? If so, what h/w has this case. > > Rob > > Hello Rob, Without setting a minItems , the example in the binding fails, because it has just 2 items, while the maxItems is now 4. I set minItems as 1 to avoid restricting any kind of hardware to have at least 2 items, but if you claim that previously, maxItems=minItems=2 , I will change this to 2. Is that fine with you ? Eugen
On 15/01/2024 04:57, Eugen Hristev wrote: > On 1/9/24 05:27, Rob Herring wrote: >> On Wed, Dec 27, 2023 at 03:08:11PM +0200, Eugen Hristev wrote: >>> MT8186 has 4 iommus in the list, to cope with this situation, adjust >>> the maxItems to 4 (instead of previous 2). >>> Add also minItems as 1 since iommus are mandatory, to avoid warning >>> on the example. >> >> maxItems alone means minItems is the same size. If IOMMU is required, >> then 'required' is where that is defined. Is there a case where 1 IOMMU >> is valid? If so, what h/w has this case. >> >> Rob >> >> > > Hello Rob, > > Without setting a minItems , the example in the binding fails, because it has just > 2 items, while the maxItems is now 4. > I set minItems as 1 to avoid restricting any kind of hardware to have at least 2 > items, but if you claim that previously, maxItems=minItems=2 , I will change this to 2. > Is that fine with you ? > I think that's what you should do yes. If in the future there shows up a platform with just one iommu, then we can fix that. Regards, Matthias
diff --git a/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.yaml b/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.yaml index 37800e1908cc..60c75b9312e8 100644 --- a/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.yaml +++ b/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.yaml @@ -38,7 +38,8 @@ properties: maxItems: 1 iommus: - maxItems: 2 + minItems: 1 + maxItems: 4 description: | Points to the respective IOMMU block with master port as argument, see Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml for details.