From: Esben Haabendal <esben@geanix.com>
To: <sashiko-bot@kernel.org>
Cc: <sashiko-reviews@lists.linux.dev>, <conor+dt@kernel.org>,
<Frank.Li@kernel.org>, <devicetree@vger.kernel.org>,
<robh@kernel.org>, <imx@lists.linux.dev>
Subject: Re: [PATCH] arm64: dts: imx8mq: Add dcss node
Date: Sat, 11 Jul 2026 12:31:37 +0200 [thread overview]
Message-ID: <87o6gdes1i.fsf@geanix.com> (raw)
In-Reply-To: <20260710095211.6BE9D1F000E9@smtp.kernel.org> (sashiko-bot@kernel.org's message of "Fri, 10 Jul 2026 09:52:10 +0000")
<sashiko-bot@kernel.org> writes:
>> + compatible = "nxp,imx8mq-dcss";
>> + reg = <0x32e00000 0x2d000>, <0x32e2f000 0x1000>;
>> + interrupts = <6>, <8>, <9>;
>
> [Severity: High]
> If power-domains = <&pgc_disp>; is omitted, the generic PM domain framework
> won't track the dependency between this device and the DISP domain.
>
> If no other active devices claim pgc_disp, the PM core may disable the
> domain during late_initcall.
>
> If a board enables this node and the driver subsequently tries to access the
> memory-mapped registers of the unpowered peripheral, it will trigger a
> synchronous external abort and panic the kernel.
>
> Is this node missing the power-domains property?
As the bindings for it does not include a power-domains property, I
don't think it is missing.
/Esben
next prev parent reply other threads:[~2026-07-11 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 9:34 [PATCH] arm64: dts: imx8mq: Add dcss node Esben Haabendal
2026-07-10 9:52 ` sashiko-bot
2026-07-10 21:13 ` Frank Li
2026-07-11 10:31 ` Esben Haabendal [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-25 10:39 [PATCH] arm64: dts: imx8mq: add DCSS node Laurentiu Palcu
2020-11-26 9:43 ` Lucas Stach
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=87o6gdes1i.fsf@geanix.com \
--to=esben@geanix.com \
--cc=Frank.Li@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=robh@kernel.org \
--cc=sashiko-bot@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