On Mon, Dec 10, 2012 at 11:37:35AM -0800, anish singh wrote:
> On Mon, Dec 10, 2012 at 10:48 AM, Guenter Roeck
> wrote:
> > On Mon, Dec 10, 2012 at 11:04:09AM +0100, Linus Walleij wrote:
> >> On Fri, Dec 7, 2012 at 5:49 PM, Alan Cox wrote:
> >>
> >> >> I could imagine declaring the activity reque
On Mon, Dec 10, 2012 at 10:48 AM, Guenter Roeck
wrote:
> On Mon, Dec 10, 2012 at 11:04:09AM +0100, Linus Walleij wrote:
>> On Fri, Dec 7, 2012 at 5:49 PM, Alan Cox wrote:
>>
>> >> I could imagine declaring the activity request buttons to be "input", but
>> >> for
>> >> presence detects it is a b
On Mon, Dec 10, 2012 at 11:04:09AM +0100, Linus Walleij wrote:
> On Fri, Dec 7, 2012 at 5:49 PM, Alan Cox wrote:
>
> >> I could imagine declaring the activity request buttons to be "input", but
> >> for
> >> presence detects it is a bit far fetched and would add too much complexity.
> >
> > Andr
On Sun, Dec 9, 2012 at 6:07 PM, Guenter Roeck wrote:
> The gpio pins I am dealing with are provided by an FPGA which is used on
> various
> boards. While the gpio access registers are always the same, the actual usage
> is
> board specific. This means I either need to write ugly code, or use th
On Fri, Dec 7, 2012 at 5:49 PM, Alan Cox wrote:
>> I could imagine declaring the activity request buttons to be "input", but for
>> presence detects it is a bit far fetched and would add too much complexity.
>
> Android tries to address this with its switch class driver, but I'm not
> sure its ac
On Sun, Dec 9, 2012 at 5:07 PM, Guenter Roeck wrote:
> On Sun, Dec 09, 2012 at 11:03:19AM +, Alan Cox wrote:
>> On Sun, 09 Dec 2012 01:58:19 -0800
>> anish kumar wrote:
>>
>> > On Fri, 2012-12-07 at 16:49 +, Alan Cox wrote:
>> > > > I could imagine declaring the activity request buttons t
On Sun, Dec 09, 2012 at 11:03:19AM +, Alan Cox wrote:
> On Sun, 09 Dec 2012 01:58:19 -0800
> anish kumar wrote:
>
> > On Fri, 2012-12-07 at 16:49 +, Alan Cox wrote:
> > > > I could imagine declaring the activity request buttons to be "input",
> > > > but for
> > > > presence detects it i
On Sun, 09 Dec 2012 01:58:19 -0800
anish kumar wrote:
> On Fri, 2012-12-07 at 16:49 +, Alan Cox wrote:
> > > I could imagine declaring the activity request buttons to be "input", but
> > > for
> > > presence detects it is a bit far fetched and would add too much
> > > complexity.
> >
> > A
On Fri, 2012-12-07 at 16:49 +, Alan Cox wrote:
> > I could imagine declaring the activity request buttons to be "input", but
> > for
> > presence detects it is a bit far fetched and would add too much complexity.
>
> Android tries to address this with its switch class driver, but I'm not
> su
> I could imagine declaring the activity request buttons to be "input", but for
> presence detects it is a bit far fetched and would add too much complexity.
Android tries to address this with its switch class driver, but I'm not
sure its actually got anything over making them input devices.
Alan
On Fri, Dec 07, 2012 at 06:59:55AM -0800, Guenter Roeck wrote:
> On Fri, Dec 07, 2012 at 09:07:28AM +0100, Linus Walleij wrote:
> > On Thu, Dec 6, 2012 at 7:32 AM, Guenter Roeck wrote:
> >
> > > Create a 'debounce' attribute if debounce is supported by the gpio
> > > chip and a gpio pin is export
On Fri, Dec 07, 2012 at 09:07:28AM +0100, Linus Walleij wrote:
> On Thu, Dec 6, 2012 at 7:32 AM, Guenter Roeck wrote:
>
> > Create a 'debounce' attribute if debounce is supported by the gpio
> > chip and a gpio pin is exported.
> >
> > Signed-off-by: Guenter Roeck
>
> Can you describe the useca
On Thu, Dec 6, 2012 at 7:32 AM, Guenter Roeck wrote:
> Create a 'debounce' attribute if debounce is supported by the gpio
> chip and a gpio pin is exported.
>
> Signed-off-by: Guenter Roeck
Can you describe the usecase for this?
I have this problem when working as a back-up GPIO maintainer tha
13 matches
Mail list logo
