I think you can just add a config file in user space program to achieve this.
2014-10-24 21:37 GMT+08:00 <[email protected]>: > Hi, > > I am just a user space developer:-) working with syfs gpio in C/Python/shell. > Using a generic gpio, the followed procedure is: > > 1) I check the chip manual for an appropriate gpio, eg.: PH02 > 2) I must guess the gpio kernel number to be exported to have > the gpio sysfs name, and fix this number in the program. > > As the gpio kernel numbers can change in the next Linux distro > in the fex file, the program will unusable. > Examining the fex file or the script.bin is not a good solution > because there can be more script.bin in the /boot with different names > or even the boot partition may be not mounted initially. > > I think the gpio kernel number has no meaning in the user space. > I propose to put a cross table into the /proc with 3 columns: > > kernel_gpio_number gpio_sysfs_name can_be_irq_source > 20 gpio20_ph2 1 > > Thanks for read it, > kantal > > -- > You received this message because you are subscribed to the Google Groups > "linux-sunxi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
