All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: lamikr@cc.jyu.fi
Cc: Linux-omap-open-source@linux.omap.com
Subject: Re: gpio Interrupt handling for omap5912
Date: Mon, 14 Aug 2006 09:17:41 +0200	[thread overview]
Message-ID: <44E02395.304@gmail.com> (raw)
In-Reply-To: <44DFA617.3030505@cc.jyu.fi>

lamikr wrote:
> Dirk Behme wrote:
>>to avoid that things like HowTo below are lost, what do you think is
>>the best place to store them?
>>
>>I can imagine
>>
>>- Documentation/arm/OMAP/GPIO
> 
> I would prefer this even it might be even too obvious place to search
> this kind of docs :-) But of course OSK wiki is also good location.

Okay, let us put it into Documentation/arm/OMAP (see patch I
sent). If it is there, I will add a link to

http://tree.celinuxforum.org/CelfPubWiki/OSK#head-0bda81ff448870f0aa282eb95524f2c157ca3e83

Then, we have it at both places ;)

> Maybe there could also be something from the just added GPIO switch
> framework usage and omap platforms it should support. (OMAP1, OMAP2?)
> 
> Another area from which I would be interested in would be ARMIOs, as I
> have only found my self couple of references to them without good
> explanation what they really are. They seems to be something that
> remains GPIO's and I would be interested in to know whether GPIO
> functions are supposed to handle also them by just using certain high
> enought ID numbers, or should they be treated diffrerently?

Anybody who is familiar with this can add this info to GPIO
howto?

Thanks

Dirk

  reply	other threads:[~2006-08-14  7:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <44D1C3AF.5010004@gmail.com>
2006-08-04  2:49 ` gpio Interrupt handling for omap5912 Arnold
2006-08-13 14:15   ` Dirk Behme
2006-08-13 22:22     ` lamikr
2006-08-14  7:17       ` Dirk Behme [this message]
2006-07-30 16:47 Reg: OMAP Debugging karthik karthik
2006-07-31  8:52 ` gpio Interrupt handling for omap5912 Arnold
2006-07-31  9:22   ` Dirk Behme
2006-08-01  9:18     ` Arnold

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=44E02395.304@gmail.com \
    --to=dirk.behme@googlemail.com \
    --cc=Linux-omap-open-source@linux.omap.com \
    --cc=lamikr@cc.jyu.fi \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.