From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/3] mfd: lubbock_io: add lubbock_io board
Date: Wed, 21 Jan 2015 15:10:52 +0000 [thread overview]
Message-ID: <20150121151052.GD22024@x1> (raw)
In-Reply-To: <332399927.402665086.1421847419490.JavaMail.root@zimbra1-e1.priv.proxad.net>
On Wed, 21 Jan 2015, robert.jarzmik at free.fr wrote:
> > ----- Mail original -----
> > De: "Lee Jones" <lee.jones@linaro.org>
> First of all, this is my web mail interface, so please be kind with
> my mail formatting ...
I have no idea what you want me to change or do differently?
Perhaps it might be more prudent for you to switch to a quality
mailer?
> > Looking at one of the other patches in the series it appears the flag
> > you're trying to capture is IORESOURCE_IRQ_LOWEDGE. When I grep for
> > where this is being _used_ (think 'consumed, rather than passed. I
> > only see a single entry in drivers/pnp/interface.c.
> Look at this call chain :
> request_irq()
> setup_irq()
> __setup_irq()
> __irq_set_trigger()
> pxa_gpio_irq_type() (aka. chip->irq_set_type)
> => hardware register manipulation
>
> Moreover, you should be aware of the bijection existing between :
> - IORESOURCE_IRQ_LOWEDGE and IRQF_TRIGGER_RISING
> - it's HIGHEDGE twin
> - it is noted in : include/linux/interrupt.h
>
> > That's what got me thinking... are you sure you're a) making use of
> this flag
> Yes, I'm quite sure.
>
> > b) assuming the answer to 'a' is "no"
> I won't :)
>
> > I think to set an edge trigger on an IRQ, you should instead do so via
> > irq_set_irq_type(), or have a missed a line or two?
> __setup_irq(), that's the entry point.
Very well, Russell and yourself have convinced me. If you fixup the
remainder of comments, I'm happy.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2015-01-21 15:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 11:00 [PATCH v3 1/3] dt-bindings: mfd: add lubbock-io binding Robert Jarzmik
2015-01-16 11:00 ` [PATCH v3 2/3] mfd: lubbock_io: add lubbock_io board Robert Jarzmik
2015-01-19 9:17 ` Lee Jones
2015-01-19 19:09 ` Robert Jarzmik
2015-01-20 10:29 ` Lee Jones
2015-01-20 11:56 ` Russell King - ARM Linux
2015-01-21 7:46 ` Robert Jarzmik
2015-01-21 8:16 ` Lee Jones
2015-01-21 8:27 ` Robert Jarzmik
2015-01-21 12:35 ` Lee Jones
2015-01-21 13:02 ` Russell King - ARM Linux
2015-01-21 13:36 ` robert.jarzmik at free.fr
2015-01-21 15:10 ` Lee Jones [this message]
2015-01-21 19:22 ` Robert Jarzmik
2015-01-21 9:47 ` Russell King - ARM Linux
2015-01-21 9:44 ` Russell King - ARM Linux
2015-01-21 16:05 ` unclear ipv6 redirect message (was Re: [PATCH v3 2/3] mfd: lubbock_io: add lubbock_io board) Joe Perches
2015-01-21 16:11 ` Russell King - ARM Linux
2015-01-21 16:40 ` Joe Perches
2015-01-21 16:46 ` Russell King - ARM Linux
2015-01-16 11:00 ` [PATCH v3 3/3] ARM: pxa: lubbock: use new lubbock_io driver Robert Jarzmik
2015-01-19 8:35 ` [PATCH v3 1/3] dt-bindings: mfd: add lubbock-io binding Lee Jones
2015-01-19 19:29 ` Robert Jarzmik
2015-01-20 10:18 ` Lee Jones
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=20150121151052.GD22024@x1 \
--to=lee.jones@linaro.org \
--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).