From: Hans Verkuil <hverkuil@xs4all.nl>
To: Simon Horman <horms+renesas@verge.net.au>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Magnus Damm <magnus.damm@gmail.com>,
linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] v4l2: remove MIPI CSI-2 driver for SH-Mobile platforms
Date: Sat, 27 Feb 2016 18:34:42 +0100 [thread overview]
Message-ID: <56D1DE32.1030604@xs4all.nl> (raw)
In-Reply-To: <56CD5A19.4000906@xs4all.nl>
On 02/24/2016 08:22 AM, Hans Verkuil wrote:
> On 02/24/2016 03:07 AM, Simon Horman wrote:
>> This driver does not appear to have ever been used by any SoC's defconfig
>> and does not appear to support DT. In sort it seems unused an unlikely
>> to be used.
>
> I prefer to move it to staging/media first for 1-2 kernel cycles. Just in case
> someone does need this.
Now that I looked more closely how it is used I think plain removal is best.
There are two options:
1) If I can manage to make a replacement ceu driver (although without cropping
support), then the old ceu and csi drivers can both go to staging and removed
later.
2) If the ceu driver has to stay longer, then the csi part has to be stripped.
Moving just the csi part to staging is not feasible given how ceu and csi work
together. It would make sense that I do this job since I can test on this board,
at least with the composite input.
Regards,
Hans
next prev parent reply other threads:[~2016-02-27 17:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 2:07 [PATCH] v4l2: remove MIPI CSI-2 driver for SH-Mobile platforms Simon Horman
2016-02-24 5:59 ` Laurent Pinchart
2016-02-24 6:17 ` Simon Horman
2016-02-24 7:20 ` Hans Verkuil
2016-02-24 8:39 ` Geert Uytterhoeven
2016-02-24 8:46 ` Hans Verkuil
2016-02-27 17:17 ` Hans Verkuil
2016-02-24 7:22 ` Hans Verkuil
2016-02-27 17:34 ` Hans Verkuil [this message]
2016-02-24 7:51 ` Geert Uytterhoeven
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=56D1DE32.1030604@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=g.liakhovetski@gmx.de \
--cc=horms+renesas@verge.net.au \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.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