From: Loic Poulain <loic.poulain@intel.com>
To: linus.walleij@linaro.org, heikki.krogerus@linux.intel.com,
mika.westerberg@intel.com, mathias.nyman@linux.intel.com,
samuel.ortiz@intel.com
Cc: linux-kernel@vger.kernel.org, Loic Poulain <loic.poulain@intel.com>
Subject: [PATCHv2] pinctrl: baytrail: Clear DIRECT_IRQ bit
Date: Wed, 17 Sep 2014 15:47:01 +0200 [thread overview]
Message-ID: <1410961621-15231-1-git-send-email-loic.poulain@intel.com> (raw)
Direct Irq En bit can be initialized to a bad value.
This bit has to be cleared for io access mode.
Signed-off-by: Loic Poulain <loic.poulain@intel.com>
---
v2: Apply over ff998356b644ebe723127bd9eec6040b59a4a4f6 + add Warning
drivers/pinctrl/pinctrl-baytrail.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/pinctrl/pinctrl-baytrail.c b/drivers/pinctrl/pinctrl-baytrail.c
index 701a646..77db3db 100644
--- a/drivers/pinctrl/pinctrl-baytrail.c
+++ b/drivers/pinctrl/pinctrl-baytrail.c
@@ -230,10 +230,13 @@ static int byt_irq_type(struct irq_data *d, unsigned type)
spin_lock_irqsave(&vg->lock, flags);
value = readl(reg);
+ WARN(value & BYT_DIRECT_IRQ_EN, "Clearing direct_irq_en bit");
+
/* For level trigges the BYT_TRIG_POS and BYT_TRIG_NEG bits
* are used to indicate high and low level triggering
*/
- value &= ~(BYT_TRIG_POS | BYT_TRIG_NEG | BYT_TRIG_LVL);
+ value &= ~(BYT_DIRECT_IRQ_EN | BYT_TRIG_POS | BYT_TRIG_NEG |
+ BYT_TRIG_LVL);
switch (type) {
case IRQ_TYPE_LEVEL_HIGH:
--
1.8.3.2
next reply other threads:[~2014-09-17 13:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 13:47 Loic Poulain [this message]
2014-09-18 7:49 ` Mika Westerberg
2014-09-18 9:31 ` Loic Poulain
2014-09-18 9:53 ` Mika Westerberg
2014-09-18 9:41 ` Samuel Ortiz
2014-09-18 9:55 ` Mika Westerberg
2014-09-18 23:59 ` eric ernst
2014-09-23 15:44 ` Linus Walleij
2014-09-23 18:36 ` Westerberg, Mika
2014-09-24 8:44 ` Loic Poulain
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=1410961621-15231-1-git-send-email-loic.poulain@intel.com \
--to=loic.poulain@intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=mika.westerberg@intel.com \
--cc=samuel.ortiz@intel.com \
/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
all inboxes | Powered by JetHome®