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: omap gpio help
Date: Wed, 3 Mar 2010 10:24:40 +0200	[thread overview]
Message-ID: <010601cabaaa$fa08d550$ee1a7ff0$@com> (raw)
In-Reply-To: <1267599614-9257-1-git-send-email-chripell@fsfe.org>

Hi all
My System is :Kernel 2.6.22.18 omap mistral
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

  reply	other threads:[~2010-03-03  8:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-02 16:05 [PATCH] This patch adds support for GPIO bank J present on S3C244X CPUs. It Christian Pellegrin
2010-03-02 16:11 ` christian pellegrin
2010-03-02 16:11   ` [PATCH resend v2.6.33] Fix support for banks H and J on S3C244X CPUs Christian Pellegrin
2010-03-02 21:54 ` [PATCH] This patch adds support for GPIO bank J present on S3C244X CPUs. It Ben Dooks
2010-03-03  6:58   ` christian pellegrin
2010-03-03  7:00     ` [PATCH] Adds support for banks H and J on S3C244X CPUs Christian Pellegrin
2010-03-03  8:24       ` doron [this message]
2010-03-03  7:00     ` [PATCH] Fix GPIOs bank H and J not being preserved during suspend Christian Pellegrin
2010-03-04 23:21       ` Ben Dooks
2010-03-08 11:17         ` christian pellegrin
2010-03-08 11:21           ` [PATCH v2] " Christian Pellegrin
2010-03-08 15:55             ` Ben Dooks
2010-03-08 16:14               ` christian pellegrin
2010-03-08 16:16                 ` Ben Dooks
2010-03-12  7:25                   ` christian pellegrin
2010-03-12  7:28                     ` [PATCH v2] Fix GPIOs banks " Christian Pellegrin
2010-03-12  7:29                     ` [PATCH v2] Fix one-too-much bug when building list of regs to be preserved on PM Christian Pellegrin

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='010601cabaaa$fa08d550$ee1a7ff0$@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).