From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [RFC 0/5] [media] rcar-vin: skeleton driver not depending on soc_camera
Date: Sun, 24 Jan 2016 22:58:51 +0000 [thread overview]
Message-ID: <1555265.Nfj4OXtCrr@avalon> (raw)
In-Reply-To: <1452778216-31978-1-git-send-email-niklas.soderlund+renesas@ragnatech.se>
Hi Niklas,
Thank you for the patches.
On Thursday 14 January 2016 14:30:11 Niklas Söderlund wrote:
> Hi,
>
> This is a RFC for the initial work of a rcar-vin driver that do not depend
> on the soc_camera framework. What is presented here is a WIP, lots of stuff
> is missing:
>
> - Setting format handling together with the v4l2_subdev.
> - DMA engine integration.
> - Power management
> - ...
>
> I saw some recent patches on linux-se where the soc_camera rcar_vin driver
> is extended so I though it best to make others aware of what I'm working
> on. But since this in such a incomplete state I do not wish to generate
> noise on linux-media so I just post it here.
>
> Niklas Söderlund (5):
> [media] rcar-vin: add skeleton
> [media] rcar-vin: hookup a vb2queue
> [media] rcar-vin: add array of supported formats
> [media] rcar-vin: add video_device
> [media] rcar-vin: hookup subdeivce using v4l2-async
Could you please resend the five patches squashed together ? It's difficult to
review a new driver split across several patches.
> drivers/media/platform/rcar-vin.c | 697 +++++++++++++++++++++++++++++++++++
> 1 file changed, 697 insertions(+)
> create mode 100644 drivers/media/platform/rcar-vin.c
>
> --
> 2.7.0
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2016-01-24 22:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 13:30 [RFC 0/5] [media] rcar-vin: skeleton driver not depending on soc_camera Niklas Söderlund
2016-01-24 22:58 ` Laurent Pinchart [this message]
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=1555265.Nfj4OXtCrr@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@vger.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).