Devicetree
 help / color / mirror / Atom feed
From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Alain Volmat <alain.volmat@foss.st.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>
Cc: <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 0/2] arm64: dts: st: add dcmi nodes in stm32mp231 / stm32mp251
Date: Mon, 28 Sep 2026 14:39:58 +0200	[thread overview]
Message-ID: <13a5a9ee-916d-4bfe-b067-8d5b7db6aca1@foss.st.com> (raw)
In-Reply-To: <20260914-stm32mp2x-dcmi-v1-0-c594e081d21b@foss.st.com>

Ciao Alain

On 9/14/26 09:09, Alain Volmat wrote:
> STM32MP23 and STM32MP25 embed a Digital Camera Interface (DCMI)
> block allowing to capture frames via a parallel interface.
> Add the dcmi nodes in both stm32mp231.dtsi and stm32mp251.dtsi
> describing this HW block.
> 
> Signed-off-by: Alain Volmat <alain.volmat@foss.st.com>
> ---
> Alain Volmat (2):
>        arm64: dts: st: add dcmi node on stm32mp25x
>        arm64: dts: st: add dcmi node on stm32mp23x
> 
>   arch/arm64/boot/dts/st/stm32mp231.dtsi | 14 ++++++++++++++
>   arch/arm64/boot/dts/st/stm32mp251.dtsi | 14 ++++++++++++++
>   2 files changed, 28 insertions(+)
> ---
> base-commit: 2f92d900f262a16c8ae02daf53ae2910d07185f5
> change-id: 20260914-stm32mp2x-dcmi-9fd57ababe6c
> 
> Best regards,
> --
> Alain Volmat <alain.volmat@foss.st.com>
> 

Applied on stm32-next.

Thanks!
Alex

      parent reply	other threads:[~2026-09-28 12:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14  7:09 [PATCH 0/2] arm64: dts: st: add dcmi nodes in stm32mp231 / stm32mp251 Alain Volmat
2026-09-14  7:09 ` [PATCH 1/2] arm64: dts: st: add dcmi node on stm32mp25x Alain Volmat
2026-09-14  7:09 ` [PATCH 2/2] arm64: dts: st: add dcmi node on stm32mp23x Alain Volmat
2026-09-14  7:21   ` sashiko-bot
2026-09-28 12:39 ` Alexandre TORGUE [this message]

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=13a5a9ee-916d-4bfe-b067-8d5b7db6aca1@foss.st.com \
    --to=alexandre.torgue@foss.st.com \
    --cc=alain.volmat@foss.st.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=robh@kernel.org \
    /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