Re: [PATCH 01/19] bh1770glc: added input device interface

2013-06-17 Thread Greg KH
On Tue, Jun 18, 2013 at 01:54:26AM +0200, Andi Shyti wrote: > > > > > The driver generates an event in /dev/input/ under the name > > > > > 'bh1770'. It's a switch event where is reported '0' or '1' > > > > > whenever the sensor detects something crossing the threshold. > > > > > > > > > Doesn't

Re: [PATCH 01/19] bh1770glc: added input device interface

2013-06-17 Thread Andi Shyti
> > > > The driver generates an event in /dev/input/ under the name > > > > 'bh1770'. It's a switch event where is reported '0' or '1' > > > > whenever the sensor detects something crossing the threshold. > > > > > > > Doesn't this mean that this driver is now an "input" driver, so it > > >

Re: [PATCH 01/19] bh1770glc: added input device interface

2013-06-17 Thread Greg KH
On Tue, Jun 18, 2013 at 01:27:39AM +0200, Andi Shyti wrote: > Hi Greg, > > > > The driver generates an event in /dev/input/ under the name > > > 'bh1770'. It's a switch event where is reported '0' or '1' > > > whenever the sensor detects something crossing the threshold. > > > > > >

Re: [PATCH 01/19] bh1770glc: added input device interface

2013-06-17 Thread Andi Shyti
Hi Greg, > > The driver generates an event in /dev/input/ under the name > > 'bh1770'. It's a switch event where is reported '0' or '1' > > whenever the sensor detects something crossing the threshold. > > > > Signed-off-by: Onur Atilla > > Signed-off-by: Phil Carmody > > Signed-off-by: Andi

Re: [PATCH 01/19] bh1770glc: added input device interface

2013-06-17 Thread Greg KH
On Thu, Jun 13, 2013 at 08:20:35PM +0200, Andi Shyti wrote: > The driver generates an event in /dev/input/ under the name > 'bh1770'. It's a switch event where is reported '0' or '1' > whenever the sensor detects something crossing the threshold. > > Signed-off-by: Onur Atilla > Signed-off-by:

Re: [PATCH 01/19] bh1770glc: added input device interface

2013-06-17 Thread Greg KH
On Thu, Jun 13, 2013 at 08:20:35PM +0200, Andi Shyti wrote: The driver generates an event in /dev/input/ under the name 'bh1770'. It's a switch event where is reported '0' or '1' whenever the sensor detects something crossing the threshold. Signed-off-by: Onur Atilla oati...@gmail.com

Re: [PATCH 01/19] bh1770glc: added input device interface

2013-06-17 Thread Andi Shyti
Hi Greg, The driver generates an event in /dev/input/ under the name 'bh1770'. It's a switch event where is reported '0' or '1' whenever the sensor detects something crossing the threshold. Signed-off-by: Onur Atilla oati...@gmail.com Signed-off-by: Phil Carmody p...@asdf.org

Re: [PATCH 01/19] bh1770glc: added input device interface

2013-06-17 Thread Greg KH
On Tue, Jun 18, 2013 at 01:27:39AM +0200, Andi Shyti wrote: Hi Greg, The driver generates an event in /dev/input/ under the name 'bh1770'. It's a switch event where is reported '0' or '1' whenever the sensor detects something crossing the threshold. Signed-off-by: Onur Atilla

Re: [PATCH 01/19] bh1770glc: added input device interface

2013-06-17 Thread Andi Shyti
The driver generates an event in /dev/input/ under the name 'bh1770'. It's a switch event where is reported '0' or '1' whenever the sensor detects something crossing the threshold. Doesn't this mean that this driver is now an input driver, so it shouldn't be using the odd

Re: [PATCH 01/19] bh1770glc: added input device interface

2013-06-17 Thread Greg KH
On Tue, Jun 18, 2013 at 01:54:26AM +0200, Andi Shyti wrote: The driver generates an event in /dev/input/ under the name 'bh1770'. It's a switch event where is reported '0' or '1' whenever the sensor detects something crossing the threshold. Doesn't this mean that this