[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <465e00ff-835e-2455-8225-d779583de726@xs4all.nl>
Date: Mon, 1 Mar 2021 13:52:02 +0100
From: Hans Verkuil <hverkuil@...all.nl>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
Sakari Ailus <sakari.ailus@....fi>
Cc: Linux Media Mailing List <linux-media@...r.kernel.org>,
linuxarm@...wei.com, mauro.chehab@...wei.com,
Jonathan Corbet <corbet@....net>,
Lukas Bulwahn <lukas.bulwahn@...il.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Randy Dunlap <rdunlap@...radead.org>,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] media: add a subsystem profile documentation
On 01/03/2021 13:42, Mauro Carvalho Chehab wrote:
> Em Mon, 1 Mar 2021 12:31:34 +0200
> Sakari Ailus <sakari.ailus@....fi> escreveu:
>
>>> +Sensor drivers:
>>> + Sakari Ailus <sakari.ailus@...ux.intel.com>
>>
>> Could you add me:
>>
>> v4l2-async, v4l2-fwnode, v4l2-flash-led-class.
>
> Adding in v5:
>
> v4l2-async, v4l2-fwnode, v4l2-flash-led-class and Sensor drivers:
> Sakari Ailus <sakari.ailus@...ux.intel.com>
>
>
>>
>> ISP drivers are generally complicated; I wonder if it should be me, Laurent
>> and Hans. It'd be nice to add ISPs, too.
>
> Not sure how to add ISP. I mean, we're actually splitting the drivers
> per API usage. Probably the main part of mapping an ISP into V4L would
> be as codec drivers, but other drivers could be doing something else.
Not sure what you mean with "as codec drivers".
ISP drivers tend to need reviews of multiple sub-maintainers, each with a
focus on their own expert area. Probably Laurent and Sakari are the primary
reviewers, while I focus more on e.g. the control framework and vb2 usage.
Regards,
Hans
>
> Suggestions?
>
>
>>
>
>> If the order is reversed, that could be expressed fairly neatly.
>
>
> Thanks,
> Mauro
>
Powered by blists - more mailing lists