touch pad, not using all the available gpio as touch, is it a problem?
Posted: Mon Sep 11, 2017 6:47 pm
i have come to this situation, while trying to implement the peripheral touch_pad, you have to use int to set it up:
touch_pad_init();
and then in the example there is a loop that reads everything. The problem is that you are not given the option to set what gpio you want to actually use, and apparently sets all available touch_gpio's as touchable?
my question is, what happens if im not using all the gpios as touch, there are 9 touch available but im only using 4, the other are being implemented as input and outputs.
is it an issue? or should i just call the touchpad init before i set the other gpio as outputs?
thanks in advance
touch_pad_init();
and then in the example there is a loop that reads everything. The problem is that you are not given the option to set what gpio you want to actually use, and apparently sets all available touch_gpio's as touchable?
my question is, what happens if im not using all the gpios as touch, there are 9 touch available but im only using 4, the other are being implemented as input and outputs.
is it an issue? or should i just call the touchpad init before i set the other gpio as outputs?
thanks in advance