Tool/software:
Hi TI Experts,
Customer is working on AM62x SDK10.0. They just bring up their development board successfully.
On their development board, they plan to use GPIO1_17 pin. They have firstly verified that their HW design is fine, because they have been fully review by our HW expert. Secondly they have tested using the gpio-key driver to change / control the GPIO1_17 pin, the result is working successfully.
As customer's last project is based on AM335x, and they are already getting used to use the kernel user space to change / control the GPIO pin, so they do not wish to use Uboot user space or use driver to control the GPIO pin.
Customer has read our FAQ below, but that is for Uboot user space.
Customer also followed the below FAQ, they followed almost everything, but as customer did not use GPIO0_38 discussed in the below link, the same steps did not work for customer to control GPIO1_17.
Let me summarize the details customer made below to control GPIO1_17 in kernel user space below, and please help to review it.
1: The DTS modifications to enable GPIO1_17.
2: The commands and log for customer to control the GPIO1_17 from kernel user space is shown below.
As you could see that after using echo 1 > value, there is no actual change in the voltage level connecting to the GPIO1_17.
And the 385 customer used is calculated by 368+17=385.
Could you help review this for customer, and let us know what might need to debug?
Many Thanks,
Kevin
