public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
To: linux-omap@vger.kernel.org
Cc: e3-hacking@earth.li
Subject: Re: [RESOLVED] Please help creating gpio-switch on ams-delta
Date: Wed, 13 May 2009 14:41:43 +0200	[thread overview]
Message-ID: <4A0AC007.4040704@tis.icnet.pl> (raw)
In-Reply-To: <4A09552F.5090402@tis.icnet.pl>

Janusz Krzysztofik napisał(a):
> I have tried two methods: gpio-switch and gpio-keys. gpio-switch device 
> is able to report the switch initial state correctly, gpio-keys device 
> just initializes without errors. However, for both methods, after first 
> switch change, the system stops responding, giving no error messages.
> 
> The code of goip-switch initialization sequence together with my 
> platform device definition (attached) does not look any different to me 
> than those for keyboard or modem (patches available from 
> http://the.earth.li/pub/e3/2.6.19/), that both also use GPIO interrupts 
> and do work for me.

Hi,

I have found that one of the patches, keyboard or modem, from 
http://the.earth.li/pub/e3/2.6.19, break gpio interrupt handling (as 
Jonathan McDowell said*, he found it conflicted with the FIQ keyboard 
patch). Without them, both gpio-switch and gpio-keys versions of a 
platform device for ams-delta hook switch do work for me. I can try to 
provide patches against omap git tree if there is any interest.

Thanks,
Janusz

* http://www.earth.li/pipermail/e3-hacking/2009-May/000868.html
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-05-13 12:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12 10:53 Please help creating gpio-switch on ams-delta Janusz Krzysztofik
2009-05-13 12:41 ` Janusz Krzysztofik [this message]
2009-05-14 18:12 ` Tony Lindgren

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=4A0AC007.4040704@tis.icnet.pl \
    --to=jkrzyszt@tis.icnet.pl \
    --cc=e3-hacking@earth.li \
    --cc=linux-omap@vger.kernel.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