From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Hemanth V" <hemanthv@ti.com>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
Daniel Mack <daniel@caiaq.de>, Jonathan Cameron <jic23@cam.ac.uk>,
Wolfram Sang <w.sang@pengutronix.de>
Subject: Re: [PATCH V2] misc : ROHM BH1780GLI Ambient light sensor Driver
Date: Wed, 2 Jun 2010 14:05:28 +0100 [thread overview]
Message-ID: <20100602140528.06013fee@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20100601131244.7164b43c.akpm@linux-foundation.org>
> Is there any standardisation of the ABIs whcih these drivers offer? If
> so, does this new driver comply with that?
There was an attempt to sort this out but Linux vetoed it because he is
under the delusion that light sensors are input devices. That doesn't
work in many use cases as you have to go ask them the light level and the
polling needed for input events keeps wrecks your idle behaviour when you
need to sample them when required instead. Instead therefore the API is
random and the devices appear in random ways and classes.
We have some intel drivers to submit as well as and when sanity prevails.
Alan
next prev parent reply other threads:[~2010-06-02 12:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 11:04 [PATCH V2] misc : ROHM BH1780GLI Ambient light sensor Driver Hemanth V
2010-06-01 20:12 ` Andrew Morton
2010-06-01 20:27 ` Daniel Mack
2010-06-01 20:38 ` Andrew Morton
2010-06-01 20:45 ` Jonathan Cameron
2010-06-01 20:39 ` Jonathan Cameron
2010-06-01 20:54 ` Andrew Morton
2010-06-01 21:39 ` Jonathan Cameron
2010-06-02 8:59 ` Hemanth V
2010-06-02 13:05 ` Alan Cox [this message]
[not found] <39216.10.24.255.17.1274699066.squirrel@dbdmail.itg.ti.com>
2010-05-26 8:30 ` Hemanth V
2010-05-26 9:39 ` Jonathan Cameron
2010-05-26 11:12 ` Hemanth V
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=20100602140528.06013fee@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@linux-foundation.org \
--cc=daniel@caiaq.de \
--cc=hemanthv@ti.com \
--cc=jic23@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=w.sang@pengutronix.de \
/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