From: Greg KH <greg@kroah.com>
To: Hemanth V <hemanthv@ti.com>
Cc: Jonathan Cameron <jic23@cam.ac.uk>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-iio@vger.kernel.org, linux-input@vger.kernel.org,
Manuel Stahl <manuel.stahl@iis.fraunhofer.de>,
Jean Delvare <khali@linux-fr.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
drivers@analog.com, achew@nvidia.com,
Donggeun Kim <dg77.kim@samsung.com>,
Dmitry Torokhov <dtor@mail.ru>
Subject: Re: Sensor event related attribute naming.
Date: Fri, 12 Nov 2010 07:03:16 -0800 [thread overview]
Message-ID: <20101112150316.GB18096@kroah.com> (raw)
In-Reply-To: <7BC12C510D794F198DFA5A5C104CD7B6@wipblrx0099946>
On Fri, Nov 12, 2010 at 03:34:36PM +0530, Hemanth V wrote:
> ----- Original Message ----- From: "Hemanth V" <hemanthv@ti.com>
> To: "Jonathan Cameron" <jic23@cam.ac.uk>; "Dmitry Torokhov" <dtor@mail.ru>
>
>
>> ----- Original Message ----- From: "Jonathan Cameron" <jic23@cam.ac.uk>
>> To: "Jonathan Cameron" <jic23@cam.ac.uk>
>> Sent: Thursday, September 30, 2010 3:36 PM
>> Subject: Re: Sensor event related attribute naming.
>>
>>
>>> Given the lack of further comment, I went ahead and implemented the above
>>> naming
>>> scheme for IIO. As the above discussion with Hemanth shows, there are
>>> some corner cases
>>> that will need futher thought in the future.
>>>
>>
>> Jonathan, haven't seen many comments on this. Do u think the reason
>> might be that these interfaces are hidden behind a HAL layer like in
>> android and
>> might not be a burning issue for many people.
>>
>
> Dmitry, could you let us know your thoughts on this too.
> Would using a HAL layer be better compared to creating a standard
> sysfs interface, as it seems to be the popular approach.
What "HAL layer"? HAL the userspace project is now dead, so you should
standardize on a common sysfs or some other user/kernel api that the
kernel exports for the same type of devices to make it so that
everything works the same way.
thanks,
greg k-h
next prev parent reply other threads:[~2010-11-12 15:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 10:04 Sensor event related attribute naming Hemanth V
2010-11-12 15:03 ` Greg KH [this message]
2010-11-12 17:32 ` Dmitry Torokhov
2010-11-15 6:40 ` Hemanth V
-- strict thread matches above, loose matches on Subject: below --
2010-09-21 14:58 RFC: " Jonathan Cameron
2010-09-24 10:34 ` Hemanth V
2010-09-24 11:58 ` Jonathan Cameron
2010-09-27 9:42 ` Jonathan Cameron
2010-09-30 10:06 ` Jonathan Cameron
2010-11-08 14:07 ` 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=20101112150316.GB18096@kroah.com \
--to=greg@kroah.com \
--cc=achew@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dg77.kim@samsung.com \
--cc=dmitry.torokhov@gmail.com \
--cc=drivers@analog.com \
--cc=dtor@mail.ru \
--cc=hemanthv@ti.com \
--cc=jic23@cam.ac.uk \
--cc=khali@linux-fr.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manuel.stahl@iis.fraunhofer.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