From: Alexandre Torgue <alexandre.torgue@st.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Hugues Fruchet <hugues.fruchet@st.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Rob Herring <robh+dt@kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-media@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
Alain Volmat <alain.volmat@st.com>,
Yannick Fertre <yannick.fertre@st.com>,
Philippe CORNU <philippe.cornu@st.com>
Subject: Re: [PATCH v5 0/4] DCMI BT656 parallel bus mode support
Date: Mon, 9 Nov 2020 09:37:51 +0100 [thread overview]
Message-ID: <027a0bb1-788e-dc73-a941-4d55c8ec5481@st.com> (raw)
In-Reply-To: <20201106115308.GO26150@paasikivi.fi.intel.com>
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.
Regards
alex
next prev parent reply other threads:[~2020-11-09 8:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 17:32 [PATCH v5 0/4] DCMI BT656 parallel bus mode support Hugues Fruchet
2020-11-04 17:32 ` [PATCH v5 1/4] media: stm32-dcmi: add support of BT656 bus Hugues Fruchet
2020-11-04 17:32 ` [PATCH v5 2/4] media: dt-bindings: media: st,stm32-dcmi: " Hugues Fruchet
2020-11-05 22:28 ` [PATCH v5 2/4] media: dt-bindings: media: st, stm32-dcmi: " Rob Herring
2020-11-04 17:32 ` [PATCH v5 3/4] ARM: dts: stm32: set bus-type in DCMI endpoint for stm32mp157c-ev1 board Hugues Fruchet
2020-11-04 17:32 ` [PATCH v5 4/4] ARM: dts: stm32: set bus-type in DCMI endpoint for stm32429i-eval board Hugues Fruchet
2020-11-05 8:29 ` [PATCH v5 0/4] DCMI BT656 parallel bus mode support Sakari Ailus
2020-11-05 9:26 ` Alexandre Torgue
2020-11-06 11:53 ` Sakari Ailus
2020-11-09 8:37 ` Alexandre Torgue [this message]
2020-11-09 23:46 ` Sakari Ailus
2020-11-09 11:16 ` Alexandre Torgue
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=027a0bb1-788e-dc73-a941-4d55c8ec5481@st.com \
--to=alexandre.torgue@st.com \
--cc=alain.volmat@st.com \
--cc=devicetree@vger.kernel.org \
--cc=hugues.fruchet@st.com \
--cc=hverkuil@xs4all.nl \
--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=philippe.cornu@st.com \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=yannick.fertre@st.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;
as well as URLs for NNTP newsgroup(s).