From: Francesco Dolcini <francesco@dolcini.it>
To: Antoine Bouyer <antoine.bouyer@nxp.com>
Cc: Francesco Dolcini <francesco@dolcini.it>,
julien.vuillaumier@nxp.com, alexi.birlinger@nxp.com,
daniel.baluta@nxp.com, peng.fan@nxp.com, frank.li@nxp.com,
jacopo.mondi@ideasonboard.com, laurent.pinchart@ideasonboard.com,
mchehab@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, michael.riesch@collabora.com,
anthony.mcgivern@arm.com, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, ai.luthra@ideasonboard.com,
paul.elder@ideasonboard.com, geert@linux-m68k.org,
sakari.ailus@linux.intel.com, hverkuil+cisco@kernel.org
Subject: Re: [PATCH v3 8/8] arm64: dts: freescale: imx95: Add NXP neoisp device tree node
Date: Mon, 15 Jun 2026 13:25:49 +0200 [thread overview]
Message-ID: <20260615112549.GA137559@francesco-nb> (raw)
In-Reply-To: <761f284a-1660-41d5-9625-9b25bf18aca5@nxp.com>
On Mon, Jun 15, 2026 at 11:56:15AM +0200, Antoine Bouyer wrote:
> On 6/14/26 11:05 AM, Francesco Dolcini wrote:
> > On Fri, Jun 12, 2026 at 03:20:39PM +0200, Antoine Bouyer wrote:
> > > Add neoisp device tree node to imx95.dtsi and enable it by default in
> > > 19x19 evk board.
> > >
> > > Signed-off-by: Antoine Bouyer <antoine.bouyer@nxp.com>
> >
> > ...
> >
> > > diff --git a/arch/arm64/boot/dts/freescale/imx95.dtsi b/arch/arm64/boot/dts/freescale/imx95.dtsi
> > > index d6c549c16047..5543a6cb1250 100644
> > > --- a/arch/arm64/boot/dts/freescale/imx95.dtsi
> > > +++ b/arch/arm64/boot/dts/freescale/imx95.dtsi
> > > @@ -1867,6 +1867,17 @@ pmu@49252000 {
> > > };
> > > };
> > >
> > > + neoisp0: isp@4ae00000 {
> > > + compatible = "nxp,imx95-neoisp";
> > > + reg = <0x0 0x4ae00000 0x0 0x8000>,
> > > + <0x0 0x4afe0000 0x0 0x10000>;
> > > + interrupts = <GIC_SPI 222 IRQ_TYPE_LEVEL_HIGH>;
> > > + clocks = <&scmi_clk IMX95_CLK_CAMCM0>;
> > > + clock-names = "camcm0";
> > > + power-domains = <&scmi_devpd IMX95_PD_CAMERA>;
> > > + status = "disabled";
> > > + };
> >
> > Why the node is disabled? If the node is wholly described in
> > imx95.dtsi, it should be enabled.
>
> Actually, all nodes are disabled in the SoC dtsi, and enabled on the board
> dts file, even if fully described on the dtsi. So I used same approach for
> neoisp.
This is not correct. Please check what we do for the GPU/VPU[1] and NPU [2],
for example. Is there a reason to do it differently for the ISP?
Francesco
[1] arch/arm64/boot/dts/freescale/imx8mm.dtsi
[2] arch/arm64/boot/dts/freescale/imx93.dtsi
next prev parent reply other threads:[~2026-06-15 11:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 13:20 [PATCH v3 0/8] media: Add iMX95 neoisp driver Antoine Bouyer
2026-06-12 13:20 ` [PATCH v3 1/8] dt-bindings: media: Add nxp neoisp support Antoine Bouyer
2026-06-12 15:39 ` Frank Li
2026-06-12 13:20 ` [PATCH v3 2/8] media: v4l2-ctrls: Add user control base for NXP neoisp controls Antoine Bouyer
2026-06-12 16:52 ` Frank Li
2026-06-12 13:20 ` [PATCH v3 3/8] media: Add meta formats supported by NXP neoisp driver Antoine Bouyer
2026-06-12 16:55 ` Frank Li
2026-06-12 13:20 ` [PATCH v3 4/8] media: uapi: Add NXP NEOISP user interface header file Antoine Bouyer
2026-06-12 13:34 ` sashiko-bot
2026-06-12 18:31 ` Frank Li
2026-06-12 13:20 ` [PATCH v3 5/8] media: Documentation: Add NXP neoisp driver documentation Antoine Bouyer
2026-06-12 13:20 ` [PATCH v3 6/8] media: platform: Add NXP Neoisp Image Signal Processor Antoine Bouyer
2026-06-12 13:41 ` sashiko-bot
2026-06-12 19:25 ` Frank Li
2026-06-12 13:20 ` [PATCH v3 7/8] media: platform: neoisp: Add debugfs support Antoine Bouyer
2026-06-12 13:34 ` sashiko-bot
2026-06-12 16:49 ` Frank Li
2026-06-12 13:20 ` [PATCH v3 8/8] arm64: dts: freescale: imx95: Add NXP neoisp device tree node Antoine Bouyer
2026-06-14 9:05 ` Francesco Dolcini
2026-06-15 9:56 ` Antoine Bouyer
2026-06-15 11:25 ` Francesco Dolcini [this message]
2026-06-15 13:46 ` Frank Li
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=20260615112549.GA137559@francesco-nb \
--to=francesco@dolcini.it \
--cc=ai.luthra@ideasonboard.com \
--cc=alexi.birlinger@nxp.com \
--cc=anthony.mcgivern@arm.com \
--cc=antoine.bouyer@nxp.com \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=frank.li@nxp.com \
--cc=geert@linux-m68k.org \
--cc=hverkuil+cisco@kernel.org \
--cc=imx@lists.linux.dev \
--cc=jacopo.mondi@ideasonboard.com \
--cc=julien.vuillaumier@nxp.com \
--cc=krzk+dt@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=michael.riesch@collabora.com \
--cc=paul.elder@ideasonboard.com \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox