From: Alain Volmat <alain.volmat@foss.st.com>
To: Conor Dooley <conor@kernel.org>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
Hugues Fruchet <hugues.fruchet@foss.st.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Hans Verkuil <hverkuil@xs4all.nl>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, <linux-media@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH 2/9] dt-bindings: media: clarify stm32 csi & simplify example
Date: Wed, 8 Jan 2025 13:42:06 +0100 [thread overview]
Message-ID: <20250108124206.GA153605@gnbcxd0016.gnb.st.com> (raw)
In-Reply-To: <20241218-yelling-palm-da676b67afb9@spud>
Hi Conor,
On Wed, Dec 18, 2024 at 06:25:11PM +0000, Conor Dooley wrote:
> On Tue, Dec 17, 2024 at 09:12:55PM +0000, Sakari Ailus wrote:
> > Hi Conor,
> >
> > On Tue, Dec 17, 2024 at 06:24:42PM +0000, Conor Dooley wrote:
> > > On Tue, Dec 17, 2024 at 06:39:19PM +0100, Alain Volmat wrote:
> > > > Clarify the description of the stm32 csi by mentioning CSI-2 and
> > > > D-PHY.
> > >
> > > > Remove the bus-type property from the example.
> > >
> > > Why? What's there to gain from the example being (seemingly?) less
> > > comprehensive?
> >
> > As the device has D-PHY, other options are excluded. I.e. that property is
> > redundant for this device.
>
> That should be mentioned in the commit message.
Ok, I'll push a v2 with that commit message fixed.
Alain
next prev parent reply other threads:[~2025-01-08 13:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 17:39 [PATCH 0/9] media: stm32: csi / dcmipp corrections Alain Volmat
2024-12-17 17:39 ` [PATCH 1/9] media: stm32: dcmipp: correct ret type in dcmipp_graph_notify_bound Alain Volmat
2024-12-17 17:39 ` [PATCH 2/9] dt-bindings: media: clarify stm32 csi & simplify example Alain Volmat
2024-12-17 18:24 ` Conor Dooley
2024-12-17 21:12 ` Sakari Ailus
2024-12-18 18:25 ` Conor Dooley
2025-01-08 12:42 ` Alain Volmat [this message]
2024-12-17 17:39 ` [PATCH 3/9] media: stm32: csi: add missing pm_runtime_put on error Alain Volmat
2024-12-17 17:39 ` [PATCH 4/9] media: stm32: csi: register subdev only at end of probe Alain Volmat
2024-12-17 17:39 ` [PATCH 5/9] media: stm32: csi: use ARRAY_SIZE to search D-PHY table Alain Volmat
2024-12-17 17:39 ` [PATCH 6/9] media: stm32: csi: simplify enable_streams error handling Alain Volmat
2024-12-17 17:39 ` [PATCH 7/9] media: stm32: csi: remove useless fwnode_graph_get_endpoint call Alain Volmat
2024-12-17 17:39 ` [PATCH 8/9] media: stm32: csi: correct unsigned or useless variable settings Alain Volmat
2024-12-17 17:39 ` [PATCH 9/9] media: stm32: dcmipp: add has_csi2 & needs_mclk in match data 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=20250108124206.GA153605@gnbcxd0016.gnb.st.com \
--to=alain.volmat@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hugues.fruchet@foss.st.com \
--cc=hverkuil@xs4all.nl \
--cc=krzk+dt@kernel.org \
--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=mchehab@kernel.org \
--cc=mcoquelin.stm32@gmail.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