From: sashiko-bot@kernel.org
To: "Jianhua Lin" <jianhua.lin@mediatek.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v9 1/3] dt-bindings: media: mediatek-jpeg-decoder: add MT8189 compatible string
Date: Thu, 09 Jul 2026 03:34:57 +0000 [thread overview]
Message-ID: <20260709033458.308191F00A3D@smtp.kernel.org> (raw)
In-Reply-To: <20260709032657.25730-2-jianhua.lin@mediatek.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The commit introduces a new mandatory property `mediatek,larb` for the MT8189 JPEG decoder, but this addition is completely undocumented in the commit message.
--
--- Patch [1]: [PATCH v9 1/3] dt-bindings: media: mediatek-jpeg-decoder: add MT8189 compatible string ---
commit e0e1e554d3c1d037a7084628a317111dade87379
Author: Jianhua Lin <jianhua.lin@mediatek.com>
dt-bindings: media: mediatek-jpeg-decoder: add MT8189 compatible string
This commit adds the compatible string for the JPEG decoder found in the
MediaTek MT8189 SoC. It updates the schema to enforce a single clock
requirement for the new SoC while maintaining the two-clock requirement for
older SoCs.
> diff --git a/Documentation/devicetree/bindings/media/mediatek-jpeg-decoder.yaml b/Documentation/devicetree/bindings/media/mediatek-jpeg-decoder.yaml
> index a4aacd3eb189b..13fb4fb61f2bc 100644
> --- a/Documentation/devicetree/bindings/media/mediatek-jpeg-decoder.yaml
> +++ b/Documentation/devicetree/bindings/media/mediatek-jpeg-decoder.yaml
[ ... ]
> @@ -51,6 +54,15 @@ properties:
> Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml for details.
> Ports are according to the HW.
>
> + mediatek,larb:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description: |
> + A phandle to the local arbiter (SMI LARB) node. This explicitly
> + describes the hardware topology where the JPEG block is connected
> + to a dedicated SMI LARB for memory bandwidth arbitration. It is
> + required to accurately represent the hardware connection independently
> + of the IOMMU.
> +
[Severity: Medium]
The schema introduces mediatek,larb as a new property, but this addition
is completely undocumented in the commit message.
The commit message explicitly details the 34-bit IOVA address space and the
single clock requirement, but fails to mention this local arbiter phandle.
Could the commit message be updated to explain this hardware topology change
and why it is mandatory for the MT8189?
> required:
> - compatible
> - reg
[ ... ]
> + required:
> + - mediatek,larb
> + else:
> + properties:
> + clocks:
> + minItems: 2
> + clock-names:
> + minItems: 2
> +
> additionalProperties: false
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260709032657.25730-1-jianhua.lin@mediatek.com?part=1
next prev parent reply other threads:[~2026-07-09 3:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 3:26 [PATCH v9 0/3] Mediatek MT8189 JPEG support Jianhua Lin
2026-07-09 3:26 ` [PATCH v9 1/3] dt-bindings: media: mediatek-jpeg-decoder: add MT8189 compatible string Jianhua Lin
2026-07-09 3:34 ` sashiko-bot [this message]
2026-07-09 17:57 ` Conor Dooley
2026-07-09 3:26 ` [PATCH v9 2/3] dt-bindings: media: mediatek-jpeg-encoder: " Jianhua Lin
2026-07-09 3:26 ` [PATCH v9 3/3] media: mediatek: jpeg: add compatible for MT8189 SoC Jianhua Lin
2026-07-09 3:38 ` sashiko-bot
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=20260709033458.308191F00A3D@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jianhua.lin@mediatek.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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