From: Sakari Ailus <sakari.ailus@iki.fi>
To: Luca Ceresoli <luca@lucaceresoli.net>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org, Leon Luo <leonl@leopardimaging.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] media: imx274: don't declare events, they are not implemented
Date: Tue, 27 Nov 2018 11:19:14 +0200 [thread overview]
Message-ID: <20181127091914.zai73kgmam7oi33m@valkosipuli.retiisi.org.uk> (raw)
In-Reply-To: <dcd7ded2-7876-c017-0d8c-1f3d159e5d2f@lucaceresoli.net>
On Tue, Nov 27, 2018 at 10:09:08AM +0100, Luca Ceresoli wrote:
> Hi Sakari,
>
> On 27/11/18 09:38, Sakari Ailus wrote:
> > Hi Luca,
> >
> > On Tue, Nov 27, 2018 at 09:34:43AM +0100, Luca Ceresoli wrote:
> >> The V4L2_SUBDEV_FL_HAS_EVENTS flag should not be set, event are just
> >> not implemented.
> >>
> >> Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
> >
> > The driver supports controls, and so control events can be subscribed and
> > received by the user. Therefore I don't see a reason to remove the flag.
I further missed the driver does not set the event (un)subscription
callbacks; the event support is actually not functional as a result. :-\
It's trivial to do that, see e.g. the imx319 driver.
>
> Thanks, good to know.
>
> Would it be worth adding a note where V4L2_SUBDEV_FL_HAS_EVENTS is
> #defined, to make this clear?
Could you send a patch? A few words should be enough, no need for a too
elaborate description I guess.
--
Regards,
Sakari Ailus
e-mail: sakari.ailus@iki.fi
prev parent reply other threads:[~2018-11-27 20:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 8:34 [PATCH 1/3] media: imx274: don't declare events, they are not implemented Luca Ceresoli
2018-11-27 8:34 ` [PATCH 2/3] media: imx274: declare the correct number of controls Luca Ceresoli
2018-11-27 8:34 ` [PATCH 3/3] media: imx274: select REGMAP_I2C Luca Ceresoli
2018-11-27 8:38 ` [PATCH 1/3] media: imx274: don't declare events, they are not implemented Sakari Ailus
2018-11-27 9:09 ` Luca Ceresoli
2018-11-27 9:19 ` Sakari Ailus [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=20181127091914.zai73kgmam7oi33m@valkosipuli.retiisi.org.uk \
--to=sakari.ailus@iki.fi \
--cc=leonl@leopardimaging.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=luca@lucaceresoli.net \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.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;
as well as URLs for NNTP newsgroup(s).