Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: yong.deng@magewell.com (Yong)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] [PATCH v9 0/2] Initial Allwinner V3s CSI Support
Date: Thu, 29 Mar 2018 09:02:56 +0800	[thread overview]
Message-ID: <20180329090256.e9621262cf069c475a706087@magewell.com> (raw)
In-Reply-To: <9b60dee0-2504-6ae3-fda3-64c4458025c3@xevo.com>

Hi,

On Wed, 28 Mar 2018 16:29:47 -0700
Martin Kelly <mkelly@xevo.com> wrote:

> On 03/05/2018 05:51 PM, Yong Deng wrote:
> > This patchset add initial support for Allwinner V3s CSI.
> > 
> > Allwinner V3s SoC features two CSI module. CSI0 is used for MIPI CSI-2
> > interface and CSI1 is used for parallel interface. This is not
> > documented in datasheet but by test and guess.
> > 
> > This patchset implement a v4l2 framework driver and add a binding
> > documentation for it.
> > 
> > Currently, the driver only support the parallel interface. And has been
> > tested with a BT1120 signal which generating from FPGA. The following
> > fetures are not support with this patchset:
> >    - ISP
> >    - MIPI-CSI2
> >    - Master clock for camera sensor
> >    - Power regulator for the front end IC
> > 
> 
> Hi Yong,
> 
> Thanks so much, this driver is a great contribution!
> 
> Unfortunately the board I'm working with (nanopi neo air) uses the MIPI 
> CSI-2 CSI0 interface rather than CSI1. Do you have any plans to support 
> the MIPI CSI-2 interface at some point? If not, do you know the scope of 
> what would be involved?

AFAIK, there is no document about MIPI CSI-2. You can take a look at the
source code in BSP:
https://github.com/friendlyarm/h3_lichee/tree/master/linux-3.4/drivers/media/video/sunxi-vfe/mipi_csi
And try to port it to mainline.

Thanks,
Yong

  reply	other threads:[~2018-03-29  1:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-06  1:51 [PATCH v9 0/2] Initial Allwinner V3s CSI Support Yong Deng
2018-03-28 23:29 ` [linux-sunxi] " Martin Kelly
2018-03-29  1:02   ` Yong [this message]
2018-03-29 17:28     ` Martin Kelly
2018-05-03 17:14 ` Maxime Ripard
2018-05-04  1:19   ` Yong

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=20180329090256.e9621262cf069c475a706087@magewell.com \
    --to=yong.deng@magewell.com \
    --cc=linux-arm-kernel@lists.infradead.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