Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Jernej Skrabec" <jernej.skrabec@gmail.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org,
	krzk+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 5/8] dt-bindings: display: allwinner: Add DE33 planes
Date: Sat, 09 May 2026 21:12:41 +0000	[thread overview]
Message-ID: <20260509211241.E9D02C2BCB2@smtp.kernel.org> (raw)
In-Reply-To: <20260509190015.79086-6-jernej.skrabec@siol.net>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] The binding specifies an independent memory-mapped region (`reg`) but completely omits required hardware dependencies like `clocks` and `resets`.
--

commit c4cb2c3df2e7559ecf6e92deffc259a4516494c5
Author: Jernej Skrabec <jernej.skrabec@gmail.com>

dt-bindings: display: allwinner: Add DE33 planes

This commit adds a new device tree binding for the Allwinner Display Engine
3.3 planes. These planes act as shared resources between mixers and are
assigned using registers within the display clocks MMIO space.

> diff --git a/Documentation/devicetree/bindings/display/allwinner,sun50i-h616-de33-planes.yaml b/Documentation/devicetree/bindings/display/allwinner,sun50i-h616-de33-planes.yaml
> new file mode 100644
> index 0000000000000..0a07cb8a5f798
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/allwinner,sun50i-h616-de33-planes.yaml
[ ... ]
> +properties:
> +  compatible:
> +    enum:
> +      - allwinner,sun50i-h616-de33-planes
> +
> +  reg:
> +    maxItems: 1
> +
> +  allwinner,plane-mapping:
> +    $ref: /schemas/types.yaml#/definitions/phandle
> +    description:
> +      Phandle of the device responsible for assigning (mapping) planes
> +      between mixers.
> +
> +required:
> +  - compatible
> +  - reg
> +  - allwinner,plane-mapping

Does this binding also need to specify clocks and resets as required
properties?

Since this node represents an independent MMIO hardware block, omitting its
hardware dependencies relies on the sibling mixer driver to implicitly power
the bus.

If the sun8i-mixer driver is unbound or fails to probe, the shared display
bus clock is left disabled. Would a subsequent read of the planes regmap
exposed to userspace via debugfs perform an MMIO read on an unclocked bus
and result in a fatal external abort (SError)?

Should clocks and resets be added to the binding so the planes driver can
manage its own bus access safely (for example, by using
regmap_mmio_attach_clk())?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260509190015.79086-1-jernej.skrabec@siol.net?part=5

  reply	other threads:[~2026-05-09 21:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-09 19:00 [PATCH v2 0/8] drm/sun4i: update DE33 support Jernej Skrabec
2026-05-09 19:00 ` [PATCH v2 1/8] clk: sunxi-ng: de2: Fix Display Engine 3.3 definitions Jernej Skrabec
2026-05-09 19:44   ` sashiko-bot
2026-05-10 19:11     ` Jernej Škrabec
2026-05-09 19:00 ` [PATCH v2 2/8] clk: sunxi-ng: de2: Export register regmap for DE33 Jernej Skrabec
2026-05-09 20:05   ` sashiko-bot
2026-05-09 19:00 ` [PATCH v2 3/8] drm/sun4i: Add support for DE33 CSC Jernej Skrabec
2026-05-09 19:00 ` [PATCH v2 4/8] drm/sun4i: vi_layer: Limit formats for DE33 Jernej Skrabec
2026-05-09 20:58   ` sashiko-bot
2026-05-09 19:00 ` [PATCH v2 5/8] dt-bindings: display: allwinner: Add DE33 planes Jernej Skrabec
2026-05-09 21:12   ` sashiko-bot [this message]
2026-05-09 19:00 ` [PATCH v2 6/8] drm/sun4i: Add planes driver Jernej Skrabec
2026-05-09 21:31   ` sashiko-bot
2026-05-09 19:00 ` [PATCH v2 7/8] dt-bindings: display: allwinner: Split H616 DE33 layer reg space Jernej Skrabec
2026-05-09 19:00 ` [PATCH v2 8/8] drm/sun4i: switch DE33 to new bindings Jernej Skrabec
2026-05-09 22:00   ` 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=20260509211241.E9D02C2BCB2@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko@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