From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 1/3] dt: palmas: support IRQ inversion at the board level
Date: Tue, 4 Mar 2014 11:50:19 +0800 [thread overview]
Message-ID: <20140304035019.GZ2411@sirena.org.uk> (raw)
In-Reply-To: <5314B0C0.4040008@wwwdotorg.org>
On Mon, Mar 03, 2014 at 09:41:36AM -0700, Stephen Warren wrote:
> 2) We can go through every single interrupt controller's DT binding and
> driver, and implement (document and parse) the new IRQ specifier flag
> there, and pass it throgh the Linux IRQ stack, yet we still need code in
> every IC driver to actually read the flag, so we haven't removed any
> code. It seems /much/ simpler, and no more of a maintenance or
> consistency burden, to just have the IC driver read the flag directly
> from their own DT.
Why does this have to be handled by the chip drivers? Can't the
interrupt controller configured in a way that the chip drivers never
need to see it at all, for example by adding a "override the mode for
this input" flag inside the device?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140304/f6e579d3/attachment.sig>
prev parent reply other threads:[~2014-03-04 3:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 20:51 [PATCH V2 1/3] dt: palmas: support IRQ inversion at the board level Stephen Warren
2014-02-27 20:51 ` [PATCH V2 2/3] mfd: " Stephen Warren
2014-02-27 20:51 ` [PATCH V2 3/3] ARM: tegra: fix Dalmore PMIC IRQ polarity Stephen Warren
2014-02-27 21:02 ` [PATCH V2 1/3] dt: palmas: support IRQ inversion at the board level Graeme Gregory
2014-02-27 21:35 ` Stephen Warren
2014-02-28 5:58 ` Mark Brown
2014-02-28 16:34 ` Stephen Warren
2014-03-01 3:13 ` Mark Brown
2014-03-03 0:52 ` Graeme Gregory
2014-03-03 16:41 ` Stephen Warren
2014-03-04 3:50 ` Mark Brown [this message]
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=20140304035019.GZ2411@sirena.org.uk \
--to=broonie@kernel.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).