All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Sofus Forstreuter" <sofus.c@icloud.com>
Cc: media-ci@linuxtv.org, robh@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 03/14] arm64: dts: apple: t8103: add avd nodes
Date: Fri, 18 Sep 2026 13:25:34 +0000	[thread overview]
Message-ID: <20260918132534.CD2A21F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260918-avd-v1-3-49977931f455@icloud.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dts: apple: t8103: avd nodes are not sorted by unit-address
--

commit 7d170c5397d0b0258ee0909282aba065f8ee4b9e
Author: Sofus Forstreuter <sofus.c@icloud.com>

arm64: dts: apple: t8103: add avd nodes
    
This commit adds the AVD (Apple Video Decoder) and its associated DART
IOMMU nodes to the t8103 device tree.

> --- a/arch/arm64/boot/dts/apple/t8103.dtsi
> +++ b/arch/arm64/boot/dts/apple/t8103.dtsi
[ ... ]
> +		avd: avd@269080000 {
> +			compatible = "apple,t8103-avd";
> +			reg = <0x2 0x69080000 0x0 0xc000>,
> +			      <0x2 0x6908c000 0x0 0xc000>,
> +			      <0x2 0x69098000 0x0 0x4000>,
> +			      <0x2 0x69100000 0x0 0x10000>;
> +			reg-names = "code", "sram", "mbox", "ctrl";
> +			interrupt-parent = <&aic>;
> +			interrupts = <AIC_IRQ 540 IRQ_TYPE_LEVEL_HIGH>,
> +				     <AIC_IRQ 541 IRQ_TYPE_LEVEL_HIGH>;
> +			power-domains = <&ps_avd_sys>;
> +			resets = <&ps_avd_sys>;
> +			iommus = <&avd_dart 0>;
> +		};
> +
> +		avd_dart: iommu@269010000 {
> +			compatible = "apple,t8103-dart";

[Severity: Low]
This isn't a functional bug, but are these nodes sorted correctly by their
unit-address? 

Device tree nodes are typically sorted in ascending order by unit-address
to maintain readability. Should the avd_dart (iommu@269010000) node be
placed before the avd (avd@269080000) node in t8103.dtsi?

> +			reg = <0x2 0x69010000 0x0 0x4000>;
> +			#iommu-cells = <1>;
> +			interrupt-parent = <&aic>;
> +			interrupts = <AIC_IRQ 547 IRQ_TYPE_LEVEL_HIGH>;
> +			power-domains = <&ps_avd_sys>;
> +		};
> +

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260918-avd-v1-0-49977931f455@icloud.com?part=3

  reply	other threads:[~2026-09-18 13:25 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-18 13:15 [PATCH 00/14] media: apple: add avd driver Sofus Forstreuter
2026-09-18 13:15 ` Sofus Forstreuter
2026-09-18 13:15 ` [PATCH 01/14] media: v4l2: Add P210 pixel format Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:26   ` sashiko-bot
2026-09-18 13:15 ` [PATCH 02/14] dt-bindings: media: add apple,avd Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:22   ` sashiko-bot
2026-09-19  6:46   ` Krzysztof Kozlowski
2026-09-19  6:46     ` Krzysztof Kozlowski
2026-09-20  7:53     ` Sofus Forstreuter
2026-09-20  7:53       ` Sofus Forstreuter
2026-09-20 10:08       ` Krzysztof Kozlowski
2026-09-20 10:08         ` Krzysztof Kozlowski
2026-09-20 11:08         ` Sofus Forstreuter
2026-09-20 11:08           ` Sofus Forstreuter
2026-09-20  8:10   ` Andy Yan
2026-09-20  8:10     ` Andy Yan
2026-09-20 10:50     ` [PATCH " Sofus Forstreuter
2026-09-20 10:50       ` Sofus Forstreuter
2026-09-18 13:15 ` [PATCH 03/14] arm64: dts: apple: t8103: add avd nodes Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:25   ` sashiko-bot [this message]
2026-09-18 13:15 ` [PATCH 04/14] arm64: dts: apple: t8112: " Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:25   ` sashiko-bot
2026-09-18 13:15 ` [PATCH 05/14] arm64: dts: apple: t8122: " Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:24   ` sashiko-bot
2026-09-18 13:15 ` [PATCH 06/14] arm64: dts: apple: t600x: " Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:15 ` [PATCH 07/14] arm64: dts: apple: t602x: " Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:15 ` [PATCH 08/14] arm64: dts: apple: t6030: " Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:28   ` sashiko-bot
2026-09-18 13:15 ` [PATCH 09/14] arm64: dts: apple: t6031: " Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:15 ` [PATCH 10/14] media: apple: add avd driver Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:36   ` sashiko-bot
2026-09-19  6:49   ` Krzysztof Kozlowski
2026-09-19  6:49     ` Krzysztof Kozlowski
2026-09-19 10:49     ` Sofus Forstreuter
2026-09-19 10:49       ` Sofus Forstreuter
2026-09-18 13:15 ` [PATCH 11/14] media: apple: avd: add h264 support Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:40   ` sashiko-bot
2026-09-18 13:15 ` [PATCH 12/14] media: apple: avd: add vp9 support Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:42   ` sashiko-bot
2026-09-18 13:15 ` [PATCH 13/14] media: apple: avd: add hevc support Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:46   ` sashiko-bot
2026-09-18 13:15 ` [PATCH 14/14] media: apple: avd: add av1 support Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:43   ` 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=20260918132534.CD2A21F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=media-ci@linuxtv.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=sofus.c@icloud.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.