From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 4/5] ARM: mediatek: Add EINT support to MTK pinctrl driver.
Date: Mon, 19 Jan 2015 11:35:47 +0100 [thread overview]
Message-ID: <CACRpkda4dqY4uMmCz_uFB_n50A3OpSBr4p1g0sZ8Kty5Ou+gkg@mail.gmail.com> (raw)
In-Reply-To: <1421376639.31355.169.camel@mtksdaap41>
On Fri, Jan 16, 2015 at 3:50 AM, Yingjoe Chen <yingjoe.chen@mediatek.com> wrote:
> On Thu, 2015-01-15 at 18:30 +0100, Linus Walleij wrote:
>> But the EINT is not a hardware number is it?
>
> It is a hardware number. eg, to mask irq for the gpio 0 above, we have
> to set bit49 in EINT mask_set register. When this irq triggered, it is
> reported using EINT status register bit49.
OK I get it (finally) then you should indeed use the irqdomain for it...
It's just a bit confusing that it begins at offset 49...
Yours,
Linus Walleij
next prev parent reply other threads:[~2015-01-19 10:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 23:34 [PATCH v4 0/5] Add Mediatek SoC Pinctrl/GPIO/EINT driver for MT8135 Hongzhou Yang
2014-12-16 23:34 ` [PATCH v4 1/5] ARM: mediatek: Add config options for mediatek SoCs Hongzhou Yang
2015-01-13 9:43 ` Linus Walleij
2015-01-14 2:33 ` Yingjoe Chen
2014-12-16 23:34 ` [PATCH v4 2/5] dt-bindings: Add pinctrl bindings for mt65xx/mt81xx Hongzhou Yang
2015-01-13 10:11 ` Linus Walleij
2015-01-20 15:46 ` Matthias Brugger
2014-12-16 23:34 ` [PATCH v4 3/5] ARM: mediatek: Add Pinctrl/GPIO driver for mt8135 Hongzhou Yang
2014-12-16 23:34 ` [PATCH v4 4/5] ARM: mediatek: Add EINT support to MTK pinctrl driver Hongzhou Yang
2014-12-17 9:09 ` Yingjoe Chen
2015-01-06 9:16 ` Yingjoe Chen
2015-01-13 13:24 ` Linus Walleij
2015-01-14 2:32 ` Yingjoe Chen
2015-01-15 17:30 ` Linus Walleij
2015-01-16 2:50 ` Yingjoe Chen
2015-01-19 10:35 ` Linus Walleij [this message]
2014-12-16 23:34 ` [PATCH v4 5/5] ARM: dts: mt8135: Add pinctrl/GPIO/EINT node for mt8135 Hongzhou Yang
2015-01-20 15:53 ` Matthias Brugger
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=CACRpkda4dqY4uMmCz_uFB_n50A3OpSBr4p1g0sZ8Kty5Ou+gkg@mail.gmail.com \
--to=linus.walleij@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).