mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ivor Kruger <ivor@veriline.co.za>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: GPIO setting
Date: Mon, 17 Mar 2014 13:09:56 +0100	[thread overview]
Message-ID: <20140317120956.GV24917@pengutronix.de> (raw)
In-Reply-To: <CF4C8306.DD5F%ivor@veriline.co.za>

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 12:10 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 [this message]
2014-03-17 13:43     ` Ivor Kruger
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=20140317120956.GV24917@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=ivor@veriline.co.za \
    /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