linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <Eugen.Hristev@microchip.com>
To: <KSloat@aampglobal.com>
Cc: <mchehab@kernel.org>, <Nicolas.Ferre@microchip.com>,
	<alexandre.belloni@bootlin.com>,
	<Ludovic.Desroches@microchip.com>, <linux-media@vger.kernel.org>
Subject: Re: [PATCH v1 1/2] media: atmel-isc: Add support for BT656 with CRC decoding
Date: Mon, 7 Jan 2019 11:10:06 +0000	[thread overview]
Message-ID: <79d76502-4fa6-d4fe-7922-9ea946edb6d9@microchip.com> (raw)
In-Reply-To: <20181228165934.36393-1-ksloat@aampglobal.com>



On 28.12.2018 18:59, Ken Sloat wrote:
> From: Ken Sloat <ksloat@aampglobal.com>
> 
> The ISC driver currently supports ITU-R 601 encoding which
> utilizes the external hysync and vsync signals. ITU-R 656
> format removes the need for these pins by embedding the
> sync pulses within the data packet.
> 
> To support this feature, enable necessary register bits
> when this feature is enabled via device tree.
> 
> Signed-off-by: Ken Sloat <ksloat@aampglobal.com>
Acked-by: Eugen Hristev <eugen.hristev@microchip.com>

Also for my reference, which board and which sensor did you test this with ?

Thanks

> ---
>   drivers/media/platform/atmel/atmel-isc-regs.h | 2 ++
>   drivers/media/platform/atmel/atmel-isc.c      | 7 ++++++-
>   2 files changed, 8 insertions(+), 1 deletion(-)
> 

  parent reply	other threads:[~2019-01-07 11:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-28 16:59 [PATCH v1 1/2] media: atmel-isc: Add support for BT656 with CRC decoding Ken Sloat
2018-12-28 16:59 ` [PATCH v1 2/2] media: atmel-isc: Update device tree binding documentation Ken Sloat
2019-01-07 11:10   ` Eugen.Hristev
2019-01-08 13:44   ` Hans Verkuil
2019-01-08 13:45     ` Hans Verkuil
2019-01-14 20:31       ` Ken Sloat
2019-01-07 11:10 ` Eugen.Hristev [this message]
2019-01-14 20:27   ` [PATCH v1 1/2] media: atmel-isc: Add support for BT656 with CRC decoding Ken Sloat

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=79d76502-4fa6-d4fe-7922-9ea946edb6d9@microchip.com \
    --to=eugen.hristev@microchip.com \
    --cc=KSloat@aampglobal.com \
    --cc=Ludovic.Desroches@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@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;
as well as URLs for NNTP newsgroup(s).