Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Paul Elder" <paul.elder@ideasonboard.com>
Cc: conor+dt@kernel.org, media-ci@linuxtv.org, robh@kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v3 4/5] dt-bindings: media: Add rockchip rkisp2
Date: Thu, 27 Aug 2026 10:57:22 +0000	[thread overview]
Message-ID: <20260827105722.B9AA71F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260827-rkisp2-v3-4-e91ff0a604d6@ideasonboard.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Missing `interrupt-names` property in the `required` list allows incomplete device trees to pass schema validation but fail driver probing.
--

commit 6781ced6c9930c8c3220edc52b5934581e2961ae
Author: Paul Elder <paul.elder@ideasonboard.com>

dt-bindings: media: Add rockchip rkisp2

This commit adds device tree binding documentation for the Rockchip ISP2,
specifically introducing support for the rk3588 compatible string. It
defines the required properties, clocks, interrupts, and ports for the
image signal processing unit.

> diff --git a/Documentation/devicetree/bindings/media/rockchip-isp2.yaml b/Documentation/devicetree/bindings/media/rockchip-isp2.yaml
> new file mode 100644
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/rockchip-isp2.yaml
[ ... ]
> +    required:
> +      - port@0
> +
> +required:
> +  - compatible
> +  - reg
> +  - interrupts
> +  - clocks
> +  - clock-names
> +  - power-domains

[Severity: Medium]
Should interrupt-names be included in this required list to ensure incomplete
device trees do not pass schema validation?

The Rockchip ISP2 driver in drivers/media/platform/rockchip/rkisp2/rkisp2-dev.c
iterates over its statically defined rk3588_isp_isrs array, which sets the name
field for both interrupts (isp_irq and mi_irq). The driver then unconditionally
executes:

info->isrs[i].name ? platform_get_irq_byname(...) : ...

This will fail and return less than 0 if interrupt-names is absent in the
device tree, aborting the probe. Adding interrupt-names to the required
properties would enforce an accurate hardware description that matches the
strict probing requirements of the driver.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260827-rkisp2-v3-0-e91ff0a604d6@ideasonboard.com?part=4

  reply	other threads:[~2026-08-27 10:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27 10:48 [PATCH v3 0/5] media: rockchip: rkisp2: Add driver for ISP on Rk3588 Paul Elder
2026-08-27 10:48 ` [PATCH v3 1/5] media: rockchip: rkisp2: Add rkisp2 driver Paul Elder
2026-08-27 10:48 ` [PATCH v3 2/5] media: rkisp2: Add parameters output video node Paul Elder
2026-08-27 11:05   ` sashiko-bot
2026-08-27 10:48 ` [PATCH v3 3/5] media: rkisp2: Add statistics capture " Paul Elder
2026-08-27 11:08   ` sashiko-bot
2026-08-27 10:48 ` [PATCH v3 4/5] dt-bindings: media: Add rockchip rkisp2 Paul Elder
2026-08-27 10:57   ` sashiko-bot [this message]
2026-08-27 16:43   ` Conor Dooley
2026-08-27 10:48 ` [PATCH v3 5/5] arm64: dts: rockchip: add ISP nodes to rk3588 Paul Elder
2026-08-27 10:57   ` 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=20260827105722.B9AA71F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=media-ci@linuxtv.org \
    --cc=paul.elder@ideasonboard.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