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] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 29 Apr 2008 14:28:58 -0700
From:	David Brownell <david-b@...bell.net>
To:	Ben Nizette <bn@...sdigital.com>
Cc:	lkml <linux-kernel@...r.kernel.org>,
	Trent Piepho <tpiepho@...escale.com>,
	hartleys <hartleys@...ionengravers.com>,
	Mike Frysinger <vapier.adi@...il.com>,
	Bryan Wu <cooloney@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [patch/rfc 2.6.25-git] gpio: sysfs interface

On Monday 28 April 2008, Ben Nizette wrote:
> > > > 
> > > > Sysfs attributes are supposed to be pollable.  I've not done it,
> > > > but fs/sysfs/file.c::sysfs_notify() looks relevant ...
> > > 
> > > Right, that'll work.
> > 
> > OK.  In that case, I think I should plan to rename the "direction"
> > attribute as "configuration" or something a bit broader ... so that
> > writing "irq" (or maybe "rising", "falling", "bothedges", "poll")
> > would eventually configure it as an input with an IRQ handler.
> 
> Good plan, unless you'd prefer to see "direction" and "interrupt" config
> separate.  I have no real preference but IMO
>   echo "falling" > interrupt
> makes more immediate sense than
>   echo "falling" > configuration

OK, I'll leave it be then.  Given that not all GPIOs support
interrupts, I used the "poll" example intentionally ... being
able to poll every N seconds (milliseconds?) may be important.


> > 
> > Whenever someone contributes such an async notification scheme,
> > that is.  ;)
> 
> ;)


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