linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Marc Zyngier" <maz@misterjones.org>
To: Daniel Mack <daniel@caiaq.de>
Cc: Jebediah Huang <jebediah.huang@gmail.com>,
	Eric Miao <eric.y.miao@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-input@vger.kernel.org
Subject: Re: Using PXA arm board with MAX7319 GPIO expander input
Date: Mon, 8 Feb 2010 12:32:38 -0000 (GMT)	[thread overview]
Message-ID: <6a1db73cb6c89001764393acd766f2ba.squirrel@www.loen.fr> (raw)
In-Reply-To: <20100208113306.GN9007@buzzloop.caiaq.de>

> I just saw that there is indeed no support for irq line handling in this
> driver. In order to use these lines as input for something like the
> gpio_keys driver, support for that should be added. I never used this
> driver and can't say whether it is under active development.

It should be rather easy to introduce something similar to what I did for
the pca953x driver (http://patchwork.kernel.org/patch/77418/)

MAX732x seems a lot saner than PCA953x, as it has at least a hardware
interrupt mask...

        M.
-- 
And if you don't know where you're going, any road will take you there...



  reply	other threads:[~2010-02-08 12:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-08  5:44 Using PXA arm board with MAX7319 GPIO expander input Jebediah Huang
2010-02-08  6:02 ` Eric Miao
2010-02-08  7:02   ` Jebediah Huang
2010-02-08  7:36     ` Daniel Mack
2010-02-08  7:56       ` Jebediah Huang
2010-02-08 11:08     ` Jebediah Huang
2010-02-08 11:33       ` Daniel Mack
2010-02-08 12:32         ` Marc Zyngier [this message]
2010-02-08 13:04           ` Daniel Mack
2010-02-09  1:05           ` Eric Miao
2010-02-09  7:39             ` Marc Zyngier
2010-02-09  8:19               ` Eric Miao
2010-02-09 10:22                 ` Marc Zyngier
2010-02-09  1:07 ` Eric Miao

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=6a1db73cb6c89001764393acd766f2ba.squirrel@www.loen.fr \
    --to=maz@misterjones.org \
    --cc=daniel@caiaq.de \
    --cc=eric.y.miao@gmail.com \
    --cc=jebediah.huang@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).