Using GPIO

[Stephen Neuendorffer]

I don't think the GPIO driver has device tree bindings yet in the driver
for ARCH=powerpc.

Steve

> -----Original Message-----
> From: linuxppc-dev-bounces+stephen.neuendorffer=xilinx.com at ozlabs.org
[mailto:linuxppc-dev-
> bounces+stephen.neuendorffer=xilinx.com at ozlabs.org] On Behalf Of John
Bonesio
> Sent: Thursday, May 15, 2008 11:39 AM
> To: Guillaume Dargaud; linuxppc-dev at ozlabs.org
> Subject: RE: Using GPIO
> 
> 
> Hi Guillaume,
> 
> If you're using arch/powerpc, my understanding is that
> CONFIG_XILINX_GPIO needs to be enabled as well as having the right
info
> in the dts file.
> 
> Right now I'll have to defer to others to tell you what's needed in
the
> dts file.
> 
> If you're using arch/ppc, I believe you just need CONFIG_XILINX_GPIO
> enabled.
> 
> When the system boots up, you see a message on the console when the
GPIO
> driver initializes.
> 
> This is not exactly a tutorial. Hopefully this still helps,
> 
> - John
> 
> -----Original Message-----
> From: linuxppc-dev-bounces+john.bonesio=xilinx.com at ozlabs.org
> [mailto:linuxppc-dev-bounces+john.bonesio=xilinx.com at ozlabs.org] On
> Behalf Of Guillaume Dargaud
> Sent: Thursday, May 15, 2008 9:35 AM
> To: linuxppc-dev at ozlabs.org
> Subject: Using GPIO
> 
> Hello all,
> I'm trying to use the Xilinx GPIO from a user program.
> Since I haven't managed to compile their example (simon.c is given
> without a
> makefile), I wanted to try using /dev/gpio...
> 
> So I added
> /dev/gpio0  c  666  0  0  10  185 -  -  -
> to device_table.txt when I generated my root filesystem with
buildroot,
> but
> apparently this leads nowhere as it's not visible in /proc/devices.
> 
> Is there some example or tutorial on how to use CONFIG_XILINX_GPIO ?
> Either
> as a device or as API calls...
> --
> Guillaume Dargaud
> http://www.gdargaud.net/
> 
> 
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev at ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
> 
> 
> This email and any attachments are intended for the sole use of the
named recipient(s) and contain(s)
> confidential information that may be proprietary, privileged or
copyrighted under applicable law. If
> you are not the intended recipient, do not read, copy, or forward this
email message or any
> attachments. Delete this email message and any attachments
immediately.
> 
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev at ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev


This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.