Re: [PATCH v5 0/4] DCMI BT656 parallel bus mode support

From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Alexandre Torgue <alexandre.torgue@st.com>
Cc: devicetree@vger.kernel.org,
	Yannick Fertre <yannick.fertre@st.com>,
	linux-kernel@vger.kernel.org,
	Philippe CORNU <philippe.cornu@st.com>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	Alain Volmat <alain.volmat@st.com>,
	Rob Herring <robh+dt@kernel.org>,
	Hugues Fruchet <hugues.fruchet@st.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org
Subject: Re: [PATCH v5 0/4] DCMI BT656 parallel bus mode support
Date: Tue, 10 Nov 2020 01:46:38 +0200	[thread overview]
Message-ID: <20201109234638.GQ26150@paasikivi.fi.intel.com> (raw)
In-Reply-To: <027a0bb1-788e-dc73-a941-4d55c8ec5481@st.com>

On Mon, Nov 09, 2020 at 09:37:51AM +0100, Alexandre Torgue wrote:
> Hi Sakari
> 
> On 11/6/20 12:53 PM, Sakari Ailus wrote:
> > Hi Alexandre,
> > 
> > On Thu, Nov 05, 2020 at 10:26:37AM +0100, Alexandre Torgue wrote:
> > > Hi Huges
> > > 
> > > On 11/4/20 6:32 PM, Hugues Fruchet wrote:
> > > > Add support of BT656 embedded synchronization bus.
> > > > This mode allows to save hardware synchro lines hsync & vsync
> > > > by replacing them with synchro codes embedded in data stream.
> > > > Add "bus-type" property and make it required so that there is no
> > > > ambiguity between parallel mode (bus-type=5) and BT656 mode (bus-type=6).
> > > > 
> > > > ===========
> > > > = history =
> > > > ===========
> > > > version 5:
> > > >     - Add revisited bindings and devicetree with explicit use of "bus-type"
> > > > 
> > > > version 4:
> > > >     - Fix typo in commit message
> > > > 
> > > > version 3:
> > > >     - Fix bus_width print to %u as per Sakari comment
> > > > 
> > > > version 2:
> > > >     - As per Sakari remark, revisit commit message and document
> > > >       BT656 parallel bus mode in bindings
> > > > 
> > > > version 1:
> > > >     - Initial submission
> > > > 
> > > > Hugues Fruchet (4):
> > > >     media: stm32-dcmi: add support of BT656 bus
> > > >     media: dt-bindings: media: st,stm32-dcmi: add support of BT656 bus
> > > >     ARM: dts: stm32: set bus-type in DCMI endpoint for stm32mp157c-ev1
> > > >       board
> > > >     ARM: dts: stm32: set bus-type in DCMI endpoint for stm32429i-eval
> > > >       board
> > > > 
> > > >    .../devicetree/bindings/media/st,stm32-dcmi.yaml   | 38 ++++++++++++++++++++++
> > > >    arch/arm/boot/dts/stm32429i-eval.dts               |  1 +
> > > >    arch/arm/boot/dts/stm32mp157c-ev1.dts              |  1 +
> > > >    drivers/media/platform/stm32/stm32-dcmi.c          | 37 +++++++++++++++++++--
> > > >    4 files changed, 75 insertions(+), 2 deletions(-)
> > > > 
> > > 
> > > I'll take DT patches on stm32-next tree.
> > 
> > Just checking: that is only the two last patches in the set, or also the
> > binding patch?
> 
> Usually I let drivers/subsystem maintainer taking dt-bindings patches with
> drivers patches.
> (If binding changes come only with dts(i) patches I take them in my tree)
> 
> -->So yes I'll take only the last two patches.

Ack, thanks!

-- 
Sakari Ailus

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel