From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
linuxarm@huawei.com, mauro.chehab@huawei.com,
Jonathan Corbet <corbet@lwn.net>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] media: add a subsystem profile documentation
Date: Mon, 1 Mar 2021 13:42:52 +0100 [thread overview]
Message-ID: <20210301134252.3d165cce@coco.lan> (raw)
In-Reply-To: <20210301103133.GK3@valkosipuli.retiisi.eu>
Em Mon, 1 Mar 2021 12:31:34 +0200
Sakari Ailus <sakari.ailus@iki.fi> escreveu:
> > +Sensor drivers:
> > + Sakari Ailus <sakari.ailus@linux.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@linux.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.
Suggestions?
>
> If the order is reversed, that could be expressed fairly neatly.
Thanks,
Mauro
next prev parent reply other threads:[~2021-03-01 12:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 9:35 [PATCH v3] media: add a subsystem profile documentation Mauro Carvalho Chehab
2021-03-01 10:05 ` Laurent Pinchart
2021-03-01 11:01 ` Mauro Carvalho Chehab
2021-03-01 10:31 ` Sakari Ailus
2021-03-01 12:42 ` Mauro Carvalho Chehab [this message]
2021-03-01 12:52 ` 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=20210301134252.3d165cce@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lukas.bulwahn@gmail.com \
--cc=mauro.chehab@huawei.com \
--cc=mchehab@kernel.org \
--cc=rdunlap@infradead.org \
--cc=sakari.ailus@iki.fi \
/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).