mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ivor Kruger <ivor@veriline.co.za>
To: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: GPIO setting
Date: Mon, 17 Mar 2014 15:43:36 +0200	[thread overview]
Message-ID: <CF4CC78F.DDE2%ivor@veriline.co.za> (raw)
In-Reply-To: <20140317120956.GV24917@pengutronix.de>

Thanks for the reply. So I take it I need to edit the mux.c file in the
PCM049(which is the one I use) board directory. I changed the lines as
below:

{I2C4_SDA, (PTU | IEN | M0)},					/* i2c4_sda */
	{MCSPI1_CLK, (M3)},					/* gpio134 */
	{MCSPI1_SOMI, (M3)},					/* gpio135 */
	{MCSPI1_SIMO, (M3)},					/* gpio136 */
	{MCSPI1_CS0, (M3)},					/* gpio137 */
	{MCSPI1_CS1, (M3)},					/* gpio138 */
	{MCSPI1_CS2, (M3)},				/* gpio139 */
	{MCSPI1_CS3, (M3)},					/* gpio140 */
	{UART3_CTS_RCTX, (PTU | IEN | M0)},				/* uart3_tx */

This still did not allow me to change pin conditions. So in the board.c
file for the PCM049, I also added these lines to force the config of the
pins:

 omap_add_display(&pcm049_fb_data);
	gpio_direction_output(135, 1);
	gpio_direction_output(136, 1);
	gpio_direction_output(137, 1);
	gpio_direction_output(138, 1);
	gpio_direction_output(139, 1);
	gpio_direction_output(140, 1);


If I then do the gpiolib command inbarebox, the pins are indicated as gpio
as below:

gpio  133:     false
gpio  134:     false
gpio  135:      true  gpio
gpio  136:      true  gpio
gpio  137:      true  gpio
gpio  138:      true  gpio
gpio  139:      true  gpio
gpio  140:      true  gpio
gpio  141:     false
gpio  142:     false
gpio  143:     false

BUT using the commands:

gpio_direction_output 135 0

And 

gpio_direction_output 135 1

Still does not change the pin condition.

Is there something else I still need to do?

Thanks
Ivor







On 2014/03/17, 2:09 PM, "Sascha Hauer" <s.hauer@pengutronix.de> wrote:

>On Mon, Mar 17, 2014 at 10:47:06AM +0200, Ivor Kruger wrote:
>> Hi, sure this is a quick and easy question for the group?
>> 
>> On the OMAP4430, using the command from within barebox prompt to
>>configure
>> a GPIO for testing hardware:
>> 
>> gpio_direction_output 140 0
>> 
>> Should this be sufficient to set the gpio pin low, or is it required to
>> still do some pin muxing as well?
>
>The gpio functions only configure the gpio controller. If this pin is
>not gpio by default, you have to configure the pinmux controller aswell.
>There is no way to do that on the barebox commandline other than direct
>register
>writes to the pinmux controller.
>
>Sascha
>
>-- 
>Pengutronix e.K.                           |                             |
>Industrial Linux Solutions                 | http://www.pengutronix.de/  |
>Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
>Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2014-03-17 13:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CF4C8000.DD58%ivor@veriline.co.za>
2014-03-17  8:47 ` Ivor Kruger
2014-03-17 12:09   ` Sascha Hauer
2014-03-17 13:43     ` Ivor Kruger [this message]
2014-03-18 16:18       ` Sascha Hauer
2014-03-18  9:21     ` Ivor Kruger
2014-03-18  9:40       ` Ivor Kruger

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=CF4CC78F.DDE2%ivor@veriline.co.za \
    --to=ivor@veriline.co.za \
    --cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox