From: yong.deng@magewell.com (Yong)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v12 0/2] Initial Allwinner V3s CSI Support
Date: Wed, 14 Nov 2018 16:40:05 +0800 [thread overview]
Message-ID: <20181114164005.76477b7401345e346def53d7@magewell.com> (raw)
In-Reply-To: <20181113133518.6nnh4m37s6awfw6d@flea>
Hi Maxime,
On Tue, 13 Nov 2018 14:35:18 +0100
Maxime Ripard <maxime.ripard@bootlin.com> wrote:
> Hi Yong,
>
> On Tue, Oct 30, 2018 at 04:09:48PM +0800, Yong Deng wrote:
> > I can't make v4l2-compliance always happy.
> > The V3s CSI support many pixformats. But they are not always available.
> > It's dependent on the input bus format (MEDIA_BUS_FMT_*).
> > Example:
> > V4L2_PIX_FMT_SBGGR8: MEDIA_BUS_FMT_SBGGR8_1X8
> > V4L2_PIX_FMT_YUYV: MEDIA_BUS_FMT_YUYV8_2X8
> > But I can't get the subdev's format code before starting stream as the
> > subdev may change it. So I can't know which pixformats are available.
> > So I exports all the pixformats supported by SoC.
> > The result is the app (v4l2-compliance) is likely to fail on streamon.
> >
> > This patchset add initial support for Allwinner V3s CSI.
> >
> > Allwinner V3s SoC features a CSI module with parallel interface.
> >
> > This patchset implement a v4l2 framework driver and add a binding
> > documentation for it.
>
> I've tested this version today, and I needed this patch to make it
> work on top of v4.20:
> http://code.bulix.org/9o8fw5-503690?raw
>
> Once that patch applied, my tests were working as expected.
>
> If that make sense, could you resubmit a new version with these merged
> so that we can try to target 4.21?
OK. I will check it.
Thanks,
Yong
next prev parent reply other threads:[~2018-11-14 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1540886988-27696-1-git-send-email-yong.deng@magewell.com>
2018-11-13 13:35 ` [PATCH v12 0/2] Initial Allwinner V3s CSI Support Maxime Ripard
2018-11-14 8:40 ` Yong [this message]
2018-11-14 10:54 ` Sakari Ailus
2018-12-26 10:29 ` [linux-sunxi] " Ondřej Jirman
2018-12-26 10:38 ` 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=20181114164005.76477b7401345e346def53d7@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