DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=date:from:to:cc:subject:message-id:references:mime-version
         :content-type:content-disposition:in-reply-to:user-agent;
        b=oe5PzTKWfjX+fE+mhOhUtxbq3TkZO+pJE9WpWmNvv9IwfWvU6xXNurv+mEc62cP6ZV
         S9AuLjr4jCO0GQMZzvFMy7wlkLw+2l2VynCsSGu2wn2wIjIZm80uYuOK57CGpN7x1Cc8
         kzssd4ghiYxLzh2+XTFxzhHfrMdbhY0lZNg34=
Date: Fri, 12 Nov 2010 09:32:28 -0800
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Hemanth V <hemanthv@ti.com>
Cc: Jonathan Cameron <jic23@cam.ac.uk>, 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>, Greg KH <greg@kroah.com>,
        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>
Subject: Re: Sensor event related attribute naming.
Message-ID: <20101112173227.GB1224@core.coreip.homeip.net>
References: <7BC12C510D794F198DFA5A5C104CD7B6@wipblrx0099946>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7BC12C510D794F198DFA5A5C104CD7B6@wipblrx0099946>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1902
Lines: 52

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.
> 

Hemanth,

I do not really see the difference between sysfs interface and HAL
interface. They both abstract hardware details and bring them to common
denominator. If you guys can agree on HAL interface I trust sysfs should
be possible too ;)

BTW, the reason I do not comment on sysfs accelerometer infrastructure
is because it is not topic I am vested in, my time budget barely covers
pure input matters. So as long as there is something that is common and
shared between drivers I would be good with it; you guys need to decide
on details, please.

Thanks.

-- 
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/