tuxd3v has quit [Remote host closed the connection]
userx_ has quit [Ping timeout: 240 seconds]
userx_ has joined #linux-sunxi
andy25225 has quit [Ping timeout: 256 seconds]
gaston1980 has quit [Quit: Konversation terminated!]
andy25225 has joined #linux-sunxi
sunshavi has joined #linux-sunxi
[7] has quit [Ping timeout: 260 seconds]
TheSeven has joined #linux-sunxi
_whitelogger has joined #linux-sunxi
lurchi__ has joined #linux-sunxi
lurchi_ has quit [Ping timeout: 256 seconds]
daregap has joined #linux-sunxi
kaspter has quit [Ping timeout: 260 seconds]
kaspter has joined #linux-sunxi
hipboi_ has quit [Quit: Leaving]
netlynx has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
camus1 has joined #linux-sunxi
lurchi__ is now known as lurchi_
kaspter has quit [Ping timeout: 265 seconds]
camus1 is now known as kaspter
camus1 has joined #linux-sunxi
kaspter has quit [Ping timeout: 256 seconds]
camus1 is now known as kaspter
camus1 has joined #linux-sunxi
kaspter has quit [Ping timeout: 256 seconds]
camus1 is now known as kaspter
reinforce has joined #linux-sunxi
cmeerw has joined #linux-sunxi
lurchi_ is now known as lurchi__
night199uk has quit [Ping timeout: 260 seconds]
night199uk has joined #linux-sunxi
matthias_bgg has joined #linux-sunxi
putti_ has joined #linux-sunxi
Putti has quit [Ping timeout: 246 seconds]
daregap has quit [Quit: daregap]
lurchi__ is now known as lurchi_
<mru>
why not use an external RC debouncer?
TheSeven has quit [Disconnected by services]
[7] has joined #linux-sunxi
<suprothunderbolt>
mru I'd like to see if I could do it in code. Mostly because the board is already soldered... :)
<mru>
doesn't the kernel have some debouncing code?
<mru>
in the gpio-keys driver
<suprothunderbolt>
there's input-debounce on the pinctrl, but I'm a little confused how it work
<suprothunderbolt>
or at least it doesn't appear to help but I'm not sure I'm setting the right IRQ bank etc
<suprothunderbolt>
mru, the gpio-keys driver does but it's very basic delay based debounce
<mru>
well, does it work?
<suprothunderbolt>
I'm using it at the moment and no. Otherwise I would have probably mentioned it...
<suprothunderbolt>
I'm unsure how to combine it with the pincntrl debounce and how that fit into the picture
<suprothunderbolt>
I suspect that's probably the way forward or I can modify the gpio-keys module to add a better debouncing algo for my needs.
<mru>
the gpio-keys driver tries to configure debounce at the gpio level
<mru>
which on sunxi means the pinctrl driver
<suprothunderbolt>
ahh okay so you only need to specify it in one place
<mru>
maybe you need a longer debounce interval
<mru>
some buttons are quite nasty
<suprothunderbolt>
that's interesting... because the debouncing is per IRQ bank not per pin.
<suprothunderbolt>
luckily I only have switches on the that bank
<suprothunderbolt>
the issue is if I crank up the debounce interval I miss short presses, if I tap the button impatiently, unless I'm making a mistake elsewhere
<mru>
depends on how the debouncing logic works, which I don't know
<suprothunderbolt>
bounce is usually around 5ms on the scope
[Notice] has joined #linux-sunxi
<suprothunderbolt>
mmm. I'm looking through the code and I'll be interested to see because of the bank vs pin debounce differences with sunxi if the gpio-keys function is actually changing it
<suprothunderbolt>
I've got it set to input-debounce 0 0 0 0 80 0 0 but I'm not sure if that is bank a, b, c, etc
<bantu>
Hello. Is anyone working on support for the NanoPi R1S-H3 device?
<mru>
does it need anything beyond some devicetree tweaks?
<bantu>
mru: I don't know. It isn't in the list of devices at least, hence the question. I can probably tell you more when the device is shipped to me.