Age | Commit message (Collapse) | Author |
|
into a gunzip, so testing this
|
|
were pull-up, this means that the issue lies with the device tree overlay not working as intended. two properties have been added to hopefully make this overlay load as intended. the compatible field has been uncommented as the driver is stable enough to be loaded automatically.
|
|
update it for git.
|
|
|
|
|
|
i have added lines at the end of init_skey() that explictly set those two pins as input, this is to help debug the issue]
|
|
active_low/active_high, but an incomplete transition to using column pins for input and row pins for output. everything works except for columns 7 and 9(pins 15 and 4)
which are always held detected as hgih. testing with the /sysfs interface has shown that pin 4 is electrically sound so it must be an issue with the driver# Please enter the commit message for your changes. Lines starting
|
|
|
|
|
|
|
|
the issue of the iutput pins not working
|
|
|
|
legacy gpio interfacd
|
|
|
|
equivalents
|
|
|
|
|
|
prototype board.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
only used during init
|
|
|
|
|
|
|
|
|
|
have been caused by excessive use of printk.
|
|
|
|
my main computer
|
|
it can sleep. it may be because of the fact that it couldn't sleep that it was causing kenel panics
|
|
panics when trying to use gpio_set_value()
|
|
|
|
|