linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: doronsa@gmail.com (doron)
To: linux-arm-kernel@lists.infradead.org
Subject: kernel 2.6.22.18 omap qpio
Date: Tue, 2 Mar 2010 22:25:05 +0200	[thread overview]
Message-ID: <00c601caba46$73b79a90$5b26cfb0$@com> (raw)

Hi all

 

I wrote an driver  to the activation of " GPIO " according to the kernel
instructions (gpio.txt) and when I request to free the GPIO I receive always
that the GPIO is reserved .

What the required steps in order to toggle the GPIO MUXED and not MUXED

 

Regards  Doron Sandroy

 

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100302/83642865/attachment-0001.htm>

             reply	other threads:[~2010-03-02 20:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-02 20:25 doron [this message]
     [not found] ` <5f4a33681003072245h37d9c78ekb4f67b23840d20a7@mail.gmail.com>
2010-03-08  8:42   ` kernel 2.6.22.18 omap qpio doron
2010-03-08  9:14     ` TAO HU
2010-03-08  9:32       ` doron

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='00c601caba46$73b79a90$5b26cfb0$@com' \
    --to=doronsa@gmail.com \
    --cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).