Devicetree
 help / color / mirror / Atom feed
From: Alain Volmat <alain.volmat@foss.st.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Hugues Fruchet <hugues.fruchet@foss.st.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre Torgue <alexandre.torgue@foss.st.com>,
	Russell King <linux@armlinux.org.uk>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Dan Scally <dan.scally@ideasonboard.com>,
	<linux-media@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-stm32@st-md-mailman.stormreply.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 4/5] ARM: dts: stm32: add dcmipp support to stm32mp135
Date: Fri, 22 Sep 2023 18:02:27 +0200	[thread overview]
Message-ID: <20230922160227.GA608616@gnbcxd0016.gnb.st.com> (raw)
In-Reply-To: <20230905090258.GC31594@pendragon.ideasonboard.com>

Hi Laurent,

On Tue, Sep 05, 2023 at 12:02:58PM +0300, Laurent Pinchart wrote:
> Hi Alain,
> 
> Thank you for the patch.
> 
> On Fri, Sep 01, 2023 at 05:57:23PM +0200, Alain Volmat wrote:
> > From: Hugues Fruchet <hugues.fruchet@foss.st.com>
> > 
> > Add dcmipp support to STM32MP135.
> > 
> > Signed-off-by: Hugues Fruchet <hugues.fruchet@foss.st.com>
> > Signed-off-by: Alain Volmat <alain.volmat@foss.st.com>
> > ---
> >  arch/arm/boot/dts/st/stm32mp135.dtsi | 8 ++++++++
> >  1 file changed, 8 insertions(+)
> > 
> > diff --git a/arch/arm/boot/dts/st/stm32mp135.dtsi b/arch/arm/boot/dts/st/stm32mp135.dtsi
> > index abf2acd37b4e..beee9ec7ed0d 100644
> > --- a/arch/arm/boot/dts/st/stm32mp135.dtsi
> > +++ b/arch/arm/boot/dts/st/stm32mp135.dtsi
> > @@ -8,5 +8,13 @@
> >  
> >  / {
> >  	soc {
> > +		dcmipp: dcmipp@5a000000 {
> > +			compatible = "st,stm32mp13-dcmipp";
> > +			reg = <0x5a000000 0x400>;
> > +			interrupts = <GIC_SPI 79 IRQ_TYPE_LEVEL_HIGH>;
> > +			resets = <&rcc DCMIPP_R>;
> > +			clocks = <&rcc DCMIPP_K>;
> > +			status = "disabled";
> 
> This needs a port, as it's marked as required in the bindings. You can
> leave the endpoint out.

I first agreed with your comment but, having done the check (make
CHECK_DTBS=y  ...) this doesn't seem to be required because the dcmipp
node is kept disabled within our dtsi.
(it is later on only enabled in dts file which as well have the port
property).
Indeed, to check this I changed it to okay and DTC_CHK complained about
missing port property.

Hence, I'd think that port doesn't have to be added in this dtsi file.
Would you agree with that ?

Regards,
Alain

> 
> With this fixed,
> 
> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> 
> > +		};
> >  	};
> >  };
> 
> -- 
> Regards,
> 
> Laurent Pinchart

  reply	other threads:[~2023-09-22 16:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-01 15:57 [PATCH v3 0/5] Add support for DCMIPP camera interface of STMicroelectronics STM32 SoC series Alain Volmat
2023-09-01 15:57 ` [PATCH v3 1/5] dt-bindings: media: add bindings for stm32 dcmipp Alain Volmat
2023-09-02 10:53   ` Conor Dooley
2023-09-05  8:58   ` Laurent Pinchart
2023-09-01 15:57 ` [PATCH v3 2/5] media: MAINTAINERS: add entry for STM32 DCMIPP driver Alain Volmat
2023-09-05  8:59   ` Laurent Pinchart
2023-09-01 15:57 ` [PATCH v3 3/5] media: stm32-dcmipp: STM32 DCMIPP camera interface driver Alain Volmat
2023-09-05  9:38   ` Laurent Pinchart
2023-09-01 15:57 ` [PATCH v3 4/5] ARM: dts: stm32: add dcmipp support to stm32mp135 Alain Volmat
2023-09-05  9:02   ` Laurent Pinchart
2023-09-22 16:02     ` Alain Volmat [this message]
2023-09-22 16:08       ` Laurent Pinchart
2023-09-25 11:35         ` Alain Volmat
2023-09-25 11:43           ` Laurent Pinchart
2023-09-27 11:03             ` Alain Volmat
2023-09-01 15:57 ` [PATCH v3 5/5] ARM: multi_v7_defconfig: enable STM32 DCMIPP media support Alain Volmat

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=20230922160227.GA608616@gnbcxd0016.gnb.st.com \
    --to=alain.volmat@foss.st.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=conor+dt@kernel.org \
    --cc=dan.scally@ideasonboard.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hugues.fruchet@foss.st.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=linux@armlinux.org.uk \
    --cc=mchehab@kernel.org \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=p.zabel@pengutronix.de \
    --cc=robh+dt@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