linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Miao <eric.y.miao@gmail.com>
To: Marc Zyngier <maz@misterjones.org>
Cc: Jebediah Huang <jebediah.huang@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	Daniel Mack <daniel@caiaq.de>,
	linux-input@vger.kernel.org
Subject: Re: Using PXA arm board with MAX7319 GPIO expander input
Date: Tue, 9 Feb 2010 16:19:18 +0800	[thread overview]
Message-ID: <f17812d71002090019n1facdbfw54f87da726333fa3@mail.gmail.com> (raw)
In-Reply-To: <20100209073903.4d8a00e4@taxman.wild-wind.fr.eu.org>

On Tue, Feb 9, 2010 at 3:39 PM, Marc Zyngier <maz@misterjones.org> wrote:
> On Tue, 9 Feb 2010 09:05:22 +0800
> Eric Miao <eric.y.miao@gmail.com> wrote:
>
>> On Mon, Feb 8, 2010 at 8:32 PM, Marc Zyngier <maz@misterjones.org> wrote:
>> >> 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...
>>
>> Well, I'd say max732x is a chip of heavy simplification, input/output direction
>> of each pin is normally hardcoded, depending on the chip model used, there
>> seems no such interrupt mask registers for SW use really.
>
> I'm currently staring at the max7319 datasheet, and it really looks
> like there is such a register:
>
> "All input ports are continuously monitored for state changes
> (transition detection). Transitions are latched, allowing detection of
> transient changes. Any combination of inputs can be selected using the
> interrupt mask to assert the INT output. When the MAX7319 is
> subsequently accessed through the serial interface, any pending
> interrupt is cleared."
>
> So it would seems (although I agree with you that max732x as a GPIO
> expander is grossly simplified) that the feature is at least advertised.
>

That sounds like a good news. I'm seeing your previous implementation
of interrupt support on pca953x as a good one, so probably would be
good to follow that, and not sure Jebediah Huang can have this tested :-)

  reply	other threads:[~2010-02-09  8:19 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
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 [this message]
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=f17812d71002090019n1facdbfw54f87da726333fa3@mail.gmail.com \
    --to=eric.y.miao@gmail.com \
    --cc=daniel@caiaq.de \
    --cc=jebediah.huang@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-input@vger.kernel.org \
    --cc=maz@misterjones.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).