hardware hardware irq debouncing support - FireBoard

	FireBoard	Forum Threaded View Rules Help

Welcome, Guest
Please Login or Register. Lost Password?

FireBoard

General talk

Computers and software

hardware hardware irq debouncing support (1 viewing) (1) Guests

Favoured: 0

Page:

<< Start < Prev 1 2 3 Next > End >>

TOPIC: hardware hardware irq debouncing support

Forum Tools

#25309

David Brownell (Visitor)

hardware hardware irq debouncing support
How is this going to work with shared interrupt lines? If one handler wants debouncing and second handler does not, you'll loose interrupts for second handler? That'd be as hardware dependent as the bad decision to mix such signals on one line in the first place! As a rule, nothing gets lost

Report to moderator Logged

Logged

The administrator has disabled public write access.

#25310

David Brownell (Visitor)

hardware hardware irq debouncing support
Hardware IRQ debouncing is common for IRQ controllers which are part of GPIO modules ... they often deal with mechanical switches, buttons, and so forth. This patch: - Provides simple support for that in genirq - Includes sample implementations for some Linux systems which already include non-generic support for this: * Atmel SOCs (AT91, AT32

Report to moderator Logged

Logged

The administrator has disabled public write access.

#25311

Haavard Skinnemoen (Visitor)

hardware hardware irq debouncing support
Hardware IRQ debouncing is common for IRQ controllers which are part of GPIO modules ... they often deal with mechanical switches, buttons, and so forth. This patch: - Provides simple support for that in genirq - Includes sample implementations for some Linux systems which already include non-generic support for this: * Atmel SOCs (AT91, AT32

Report to moderator Logged

Logged

The administrator has disabled public write access.

#25312

David Brownell (Visitor)

hardware hardware irq debouncing support

Report to moderator Logged

Logged

The administrator has disabled public write access.

#25313

Haavard Skinnemoen (Visitor)

hardware hardware irq debouncing support

Maybe we should let drivers provide a range of acceptable delays so that the irq chip driver won't have to guess at how long it is acceptable to deviate from the specified delay. I can't see it working otherwise. Of course, maybe there should just be generic ranges rather than expecting drivers to understand how springy contacts might be on a given board, or how dirty they may be to cause other kinds of chatter. Maybe. I'd prefer real numbers to generic-sounding names like low/medium/high, but if someone can come up with a good way to express this, I guess that could work. And I don't really expect drivers to understand this, but drivers can get help from the platform or board code. Haavard

Report to moderator Logged

Logged

The administrator has disabled public write access.

#25314

Pavel Machek (Visitor)

hardware hardware irq debouncing support
Why require software debouncing if perhaps the hardware could do it all for you? Because of the perhaps part of your sentence. I'm not sure which sentence you refer too, but the first perhaps above is yours! I mean that it's difficult to rely on hardware that perhaps can do debouncing for you. I think many drivers need to know for sure. Why? You write code as if no debouncing exist...

Report to moderator Logged

Logged

The administrator has disabled public write access.

Page:
<< Start < Prev 1 2 3 Next > End >>

Forum List

General talk

Computers and software