From: Krzysztof Kozlowski <krzk@kernel.org>
To: Matthias Brugger <matthias.bgg@gmail.com>, Fei Shao <fshao@chromium.org>
Cc: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Bin Liu <bin.liu@mediatek.com>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>, Xia Jiang <xia.jiang@mediatek.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v2 3/8] dt-bindings: media: mediatek,jpeg: Relax IOMMU max item count
Date: Wed, 2 Oct 2024 16:00:43 +0200 [thread overview]
Message-ID: <9b4ee771-2772-46f7-b6f2-382c11934d99@kernel.org> (raw)
In-Reply-To: <dbe0927e-2d7b-4a32-a155-206566d543a8@gmail.com>
On 02/10/2024 15:12, Matthias Brugger wrote:
>
>
> On 02/10/2024 08:16, Krzysztof Kozlowski wrote:
>> On Tue, Oct 01, 2024 at 07:27:21PM +0800, Fei Shao wrote:
>>> On MediaTek platforms with Multimedia MMU (M4U), a multimedia hardware
>>> can be assigned with a local arbiter (LARB) which has a maximum of 32
>>> ports for MediaTek's IOMMU infrastructure. That means there can be at
>>> most 32 items in the iommus property in theory.
>>>
>>> Instead of relaxing the max item count every time a newly introduced
>>> device tree hits the limit, bump the number to 32 as an one-time effort.
>>>
>>> On the other hand, all existing and foreseeable JPEG decoder nodes at
>>> this point have at least 2 IOMMUs, so set minItems to 2 accordingly.
>>>
>>> Signed-off-by: Fei Shao <fshao@chromium.org>
>>> ---
>>> It's not in the upstream tree yet, but the upcoming MT8188 DT will have
>>> 6 IOMMUs in its JPEG decoder. This patch is to pave the way for that.
>>>
>>> Changes in v2:
>>> New patch.
>>>
>>
>> I do not see any user of this in this patchset.
>>
>
> I'm not sure I understand you: the binding describes the hardware. If it can
> have up to 32 ports, then this should be reflected in the binding.
Yeah, but people do not describe hardware but drivers. Looking at DTS
clarifies sometimes such cases and avoids lengthy discussions. Plus I
was not really sure if these are IOMMUs for the same device for example
(again: people do weird stuff).
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-02 14:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 11:27 [PATCH v2 0/8] MT8188 DT and binding fixes Fei Shao
2024-10-01 11:27 ` [PATCH v2 1/8] dt-bindings: power: mediatek: Add another nested power-domain layer Fei Shao
2024-12-02 16:07 ` Ulf Hansson
2024-10-01 11:27 ` [PATCH v2 2/8] dt-bindings: PCI: mediatek-gen3: Allow exact number of clocks only Fei Shao
2024-10-01 11:27 ` [PATCH v2 3/8] dt-bindings: media: mediatek,jpeg: Relax IOMMU max item count Fei Shao
2024-10-02 6:16 ` Krzysztof Kozlowski
2024-10-02 11:57 ` Fei Shao
2024-10-02 13:12 ` Matthias Brugger
2024-10-02 14:00 ` Krzysztof Kozlowski [this message]
2024-10-02 13:59 ` Krzysztof Kozlowski
2024-10-01 11:27 ` [PATCH v2 4/8] dt-bindings: media: mediatek,vcodec: Revise description Fei Shao
2024-10-02 6:16 ` Krzysztof Kozlowski
2024-10-01 11:27 ` [PATCH v2 5/8] arm64: dts: mediatek: mt8188: Add missing dma-ranges to soc node Fei Shao
2024-10-01 11:27 ` [PATCH v2 6/8] arm64: dts: mediatek: mt8188: Update vppsys node names to syscon Fei Shao
2024-10-01 11:27 ` [PATCH v2 7/8] arm64: dts: mediatek: mt8188: Move vdec1 power domain under vdec0 Fei Shao
2024-10-01 11:27 ` [PATCH v2 8/8] arm64: dts: mediatek: mt8188: Move SPI NOR *-cells properties Fei Shao
2024-10-02 9:33 ` (subset) [PATCH v2 0/8] MT8188 DT and binding fixes AngeloGioacchino Del Regno
2024-12-02 4:24 ` Chen-Yu Tsai
2024-12-02 16:07 ` Ulf Hansson
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=9b4ee771-2772-46f7-b6f2-382c11934d99@kernel.org \
--to=krzk@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bin.liu@mediatek.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fshao@chromium.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=xia.jiang@mediatek.com \
/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®