lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20100913011302.GV14056@atomos.longlandclan.yi.org>
Date:	Mon, 13 Sep 2010 11:13:02 +1000
From:	Stuart Longland <redhatter@...too.org>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Jonathan Cameron <kernel@...23.retrosnub.co.uk>
Cc:	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: Voltage/current/sensor monitoring interface and Wiegand

On Thu, Sep 09, 2010 at 11:32:54PM -0700, Dmitry Torokhov wrote:
> On Thu, Sep 09, 2010 at 01:43:20PM +0100, Jonathan Cameron wrote:
> > ....
> > > 
> > > Likewise with the PIR sensor, I notice there's a "gesture" input
> > > (MSC_GESTURE)... seems appropriate?  Or am I barking up the wrong tree?
> > Does it look like a button (e.g. is it a straight on off device with
> > no control parameters etc)?

Had a discussion with a few of the people involved on Friday.  For all
intents and purposes, it will look like a "button".  Apparently with the
PIR sensor, nominally the value I get (which is a raw 10-bit reading
from an ADC) will be some high but mostly constant value.  When movement
is detected, it'll shoot up, then down, then settle back to where it
was.

At this point, the sensor controller will send an interrupt.  I can
consider this a "button press"... I suppose I can consider a button
release as being some time after the movement has ceased.  There is a
register that controls sensitivity.  I could make that a
sysfs-adjustable parameter, but ideally if there's a standard interface
for things like trigger sensitivity, I'd like to use that too.

> > Dmitry, what would you put this as and would
> > this be acceptable in input?  
> 
> Phone guys made me add SW_FRONT_PROXIMITY at some point which is
> supposed to be reported when someone covers phone screen with something
> (puts into pocket or talks holding against the cheek). Could be used
> here as well...

I'll have a hunt around for this SW_FRONT_PROXIMITY (it wasn't in kernel
2.6.28) and see if I can bring it in.  The idea here is that when
someone passes this entrance station, it can trigger the LCD/keypad to
light up, turn on security lights...etc.

Thanks for the advice.
Regards,
-- 
Stuart Longland (aka Redhatter, VK4MSL)      .'''.
Gentoo Linux/MIPS Cobalt and Docs Developer  '.'` :
. . . . . . . . . . . . . . . . . . . . . .   .'.'
http://dev.gentoo.org/~redhatter             :.'

I haven't lost my mind...
  ...it's backed up on a tape somewhere.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ