All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen Neuendorffer" <stephen.neuendorffer@xilinx.com>
To: "John Bonesio" <john.bonesio@xilinx.com>,
	"Guillaume Dargaud" <dargaud@lpsc.in2p3.fr>,
	<linuxppc-dev@ozlabs.org>
Subject: RE: Using GPIO
Date: Thu, 15 May 2008 11:56:35 -0700	[thread overview]
Message-ID: <20080515185637.587AF43004B@mail186-sin.bigfish.com> (raw)
In-Reply-To: <20080515183910.6B40A75007E@mail106-va3.bigfish.com>



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

Steve

> -----Original Message-----
> From: linuxppc-dev-bounces+stephen.neuendorffer=3Dxilinx.com@ozlabs.org
[mailto:linuxppc-dev-
> bounces+stephen.neuendorffer=3Dxilinx.com@ozlabs.org] On Behalf Of John
Bonesio
> Sent: Thursday, May 15, 2008 11:39 AM
> To: Guillaume Dargaud; linuxppc-dev@ozlabs.org
> Subject: RE: Using GPIO
>=20
>=20
> Hi Guillaume,
>=20
> 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.
>=20
> Right now I'll have to defer to others to tell you what's needed in
the
> dts file.
>=20
> If you're using arch/ppc, I believe you just need CONFIG_XILINX_GPIO
> enabled.
>=20
> When the system boots up, you see a message on the console when the
GPIO
> driver initializes.
>=20
> This is not exactly a tutorial. Hopefully this still helps,
>=20
> - John
>=20
> -----Original Message-----
> From: linuxppc-dev-bounces+john.bonesio=3Dxilinx.com@ozlabs.org
> [mailto:linuxppc-dev-bounces+john.bonesio=3Dxilinx.com@ozlabs.org] On
> Behalf Of Guillaume Dargaud
> Sent: Thursday, May 15, 2008 9:35 AM
> To: linuxppc-dev@ozlabs.org
> Subject: Using GPIO
>=20
> 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...
>=20
> 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.
>=20
> 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/
>=20
>=20
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>=20
>=20
> 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.
>=20
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@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.

  reply	other threads:[~2008-05-15 18:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15 16:35 Using GPIO Guillaume Dargaud
2008-05-15 18:39 ` John Bonesio
2008-05-15 18:56   ` Stephen Neuendorffer [this message]
2008-05-16  8:15   ` Guillaume Dargaud
2008-05-16 16:17     ` John Linn
2008-05-19 11:56       ` Guillaume Dargaud
2008-05-19 13:42         ` Josh Boyer
  -- strict thread matches above, loose matches on Subject: below --
2008-05-19 15:23 Guillaume Dargaud
2008-06-06  7:51 Ludovic Desroches
2008-06-06 16:09 ` Guillaume Dargaud

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080515185637.587AF43004B@mail186-sin.bigfish.com \
    --to=stephen.neuendorffer@xilinx.com \
    --cc=dargaud@lpsc.in2p3.fr \
    --cc=john.bonesio@xilinx.com \
    --cc=linuxppc-dev@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.