From: "Wu, Songjun" <songjun.wu@atmel.com>
To: Ludovic Desroches <ludovic.desroches@atmel.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Hans Verkuil <hverkuil@xs4all.nl>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Josh Wu <rainyfeeling@gmail.com>,
Robert Jarzmik <robert.jarzmik@free.fr>,
Fabio Estevam <fabio.estevam@freescale.com>,
Javier Martin <javier.martin@vista-silicon.com>,
Nicolas Ferre <nicolas.ferre@atmel.com>
Subject: Re: [RFC] Move some soc-camera drivers to staging in preparation for removal
Date: Tue, 23 Feb 2016 15:06:02 +0800 [thread overview]
Message-ID: <56CC04DA.3030002@atmel.com> (raw)
In-Reply-To: <20160222160857.GB2607@odux.rfo.atmel.com>
On 2/23/2016 00:08, Ludovic Desroches wrote:
> On Mon, Feb 22, 2016 at 04:23:54PM +0200, Laurent Pinchart wrote:
>> Hi Guennadi,
>>
>> (CC'ing Ludovic Desroches)
>>
>> On Monday 22 February 2016 14:39:08 Guennadi Liakhovetski wrote:
>>> Hi Laurent,
>>>
>>> On Mon, 22 Feb 2016, Laurent Pinchart wrote:
>>>
>>> [snip]
>>>
>>>> As far as I know Renesas (or at least the kernel upstream team) doesn't
>>>> care. The driver is only used on five SH boards, I'd also say it can be
>>>> removed.
>>> [snip]
>>>
>>>>>>> - atmel-isi: ATMEL Image Sensor Interface (ISI)
>>>>>>>
>>>>>>> I believe this is still actively maintained. Would someone be
>>>>>>> willing to convert this? It doesn't look like a complex driver.
>>>>
>>>> That would be nice, I would like to avoid dropping this one.
>>>
>>> Thanks for clarifying the state of the CEU driver. I did say, that I am
>>> fine with dropping soc-camera gradually, and I stay with that. But I see
>>> now, that at least two drivers want to stay active: Atmel ISI and PXA270.
>>> One possibility is of course to make them independent drivers. If people
>>> are prepared to invest work into that - sure, would be great! If we
>>> however decide to keep soc-camera, I could propose the following: IIUC,
>>> the largest problem is sensor drivers, that cannot be reused for other
>>> non-soc-camera bridge drivers. The thing is, out of all the sensor drivers
>>> currently under drivers/media/i2c/soc_camera only a couple are in use on
>>> those active PXA270 and Atmel boards. I could propose the following:
>>>
>>> 1. Remove all bridge drivers, that noone cares about.
>>> 2. If anyone ever needs to use any of soc-camera-associated sensor
>>> drivers, take them out of soc-camera and _remove_ any soc-camera
>>> dependencies
>>> 3. If any soc-camera boards will need that specific driver, which in
>>> itself is already unlikely, we'll have to fix that by teaching
>>> soc-camera to work with generic sensor drivers!
>>
>> That sounds like a good plan.
>>
>> Ludovic, any chance someone at Atmel could convert the ISI driver ?
>
> I add Songjun to the cc list. I think he has in mind to do this
> conversion.
>
> Songjun, can you confirm?
>
> Full thread here:
> http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/99290
>
Laurent, I will take the ISI driver, convert it from soc_camera to V4L2.
> Regards
>
> Ludovic
>
next prev parent reply other threads:[~2016-02-23 7:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 13:24 [RFC] Move some soc-camera drivers to staging in preparation for removal Hans Verkuil
2016-02-19 16:24 ` Mauro Carvalho Chehab
2016-02-19 16:30 ` Hans Verkuil
2016-02-19 18:01 ` Robert Jarzmik
2016-02-19 18:12 ` Hans Verkuil
2016-02-20 21:33 ` Robert Jarzmik
2016-02-21 15:06 ` Hans Verkuil
2016-02-22 7:01 ` Guennadi Liakhovetski
2016-02-22 7:11 ` Guennadi Liakhovetski
2016-02-22 13:21 ` Laurent Pinchart
2016-02-22 13:39 ` Guennadi Liakhovetski
2016-02-22 14:23 ` Laurent Pinchart
2016-02-22 16:08 ` Ludovic Desroches
2016-02-23 7:06 ` Wu, Songjun [this message]
2016-02-23 7:26 ` Hans Verkuil
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=56CC04DA.3030002@atmel.com \
--to=songjun.wu@atmel.com \
--cc=fabio.estevam@freescale.com \
--cc=g.liakhovetski@gmx.de \
--cc=hverkuil@xs4all.nl \
--cc=javier.martin@vista-silicon.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=nicolas.ferre@atmel.com \
--cc=rainyfeeling@gmail.com \
--cc=robert.jarzmik@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.