Re: [meta-xilinx] gpio export from device tree

pin number. So for example MUX_ENABLE is on GPIO 989 (960 + 29). -Original Message- From: Jean-Francois Dagenais [mailto:jeff.dagen...@gmail.com] Sent: 02 March 2017 15:19 To: Alan Levy Cc: Mike Looijmans; meta-xilinx@yoctoproject.org Subject: Re: [meta-xilinx] gpio export from device tree H

Re: [meta-xilinx] gpio export from device tree

Hi Alan, Thanks for this insight. > On Mar 1, 2017, at 05:16, Alan Levy wrote: > > In order to give userspace GPIOs sane names I use devicetree aliases which > application code can access from /proc/device-tree/aliases. Each GPIO has an > alias with a sensible name and

Re: [meta-xilinx] gpio export from device tree

@yoctoproject.org Subject: Re: [meta-xilinx] gpio export from device tree On 27-02-17 22:52, Jean-Francois Dagenais wrote: ... > So my questions are: > * which clause, if any, is proper in dts to export the GPIOs > preferably with names (like /sys/class/gpio/my_gpio_name_here). Do I > need to d

Re: [meta-xilinx] gpio export from device tree

On 27-02-17 22:52, Jean-Francois Dagenais wrote: ... So my questions are: * which clause, if any, is proper in dts to export the GPIOs preferably with names (like /sys/class/gpio/my_gpio_name_here). Do I need to declare a new node which doesn’t bind to a diver for example… There have been a

[meta-xilinx] gpio export from device tree

Hi guys, In a previous design on x86, in the kernel, I was exporting a bunch of system gpios to sysfs/userspace with direction and names using gpio_request_one() from platform init code. I’m now trying to achieve something similar on zynq/zynqmp but hopefully without having to write a driver,