linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Hugues Fruchet <hugues.fruchet@st.com>
Cc: Alexandre Torgue <alexandre.torgue@st.com>,
	linux-kernel@vger.kernel.org, Alain Volmat <alain.volmat@st.com>,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-media@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Yannick Fertre <yannick.fertre@st.com>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	Philippe CORNU <philippe.cornu@st.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>
Subject: Re: [PATCH v5 2/4] media: dt-bindings: media: st, stm32-dcmi: add support of BT656 bus
Date: Thu, 5 Nov 2020 16:28:13 -0600	[thread overview]
Message-ID: <20201105222813.GA1915114@bogus> (raw)
In-Reply-To: <1604511132-4014-3-git-send-email-hugues.fruchet@st.com>

On Wed, 04 Nov 2020 18:32:10 +0100, Hugues Fruchet wrote:
> Add support of BT656 embedded synchronization bus mode in DCMI driver.
> 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).
> BT656 mode allows to save hardware synchro lines hsync & vsync by replacing
> them with synchro codes embedded in data stream, hence hsync-active &
> vsync-active properties are useless in this mode.
> With DCMI, BT656 bus mode is only compatible with 8 bits width data bus.
> 
> Signed-off-by: Hugues Fruchet <hugues.fruchet@st.com>
> ---
>  .../devicetree/bindings/media/st,stm32-dcmi.yaml   | 38 ++++++++++++++++++++++
>  1 file changed, 38 insertions(+)
> 

Reviewed-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2020-11-05 22:28 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   ` Rob Herring [this message]
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
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=20201105222813.GA1915114@bogus \
    --to=robh@kernel.org \
    --cc=alain.volmat@st.com \
    --cc=alexandre.torgue@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).