This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Re: How to create a GPIO driver

From: "Morris, Richard" <Richard dot Morris at lifetech dot com>
To: EnneGi <enricogiordano1992 at gmail dot com>
Cc: "ecos-discuss at ecos dot sourceware dot org" <ecos-discuss at ecos dot sourceware dot org>
Date: Wed, 13 Mar 2013 08:35:47 -0700
Subject: Re: [ECOS] Re: How to create a GPIO driver
References: <1362939557386-224910.post@n7.nabble.com> <513CDD92.6060003@siva.com.mk> <1362956256201-224925.post@n7.nabble.com> <D40A7EF7-7D86-4943-911B-317DF67906D8@lifetech.com> <1363020733839-225026.post@n7.nabble.com> <CDD24990-A455-41A8-BA94-C9E9A8A58B94@lifetech.com> <1363126636423-225218.post@n7.nabble.com>

The pin arguments for the hal_LPC17xx_gpio_xxx() functions you describe are likely provided by a macro, of which I don't know the name.  It may be in the var_io.h file for your eCos distribution.

Once you know the value of the PIN argument, you can call the hal_LPC17XX_gpio_xxx() functions of your distribution.


--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Follow-Ups:
- Re: How to create a GPIO driver
  - From: EnneGi

References:
- How to create a GPIO driver
  - From: EnneGi
- Re: How to create a GPIO driver
  - From: Ilija Kocho
- Re: How to create a GPIO driver
  - From: EnneGi
- Re: Re: How to create a GPIO driver
  - From: Morris, Richard
- Re: How to create a GPIO driver
  - From: EnneGi
- Re: How to create a GPIO driver
  - From: Morris, Richard
- Re: How to create a GPIO driver
  - From: EnneGi

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]