From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Loic Poulain <loic.poulain@intel.com>,
heikki.krogerus@linux.intel.com, mika.westerberg@intel.com,
samuel.ortiz@intel.com
Cc: linux-kernel@vger.kernel.org, Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH] pinctrl: baytrail: Clear DIRECT_IRQ bit
Date: Wed, 17 Sep 2014 16:18:37 +0300 [thread overview]
Message-ID: <54198A2D.30908@linux.intel.com> (raw)
In-Reply-To: <1410957035-13965-1-git-send-email-loic.poulain@intel.com>
On 09/17/2014 03:30 PM, Loic Poulain wrote:
> 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>
> ---
> drivers/pinctrl/pinctrl-baytrail.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/pinctrl/pinctrl-baytrail.c b/drivers/pinctrl/pinctrl-baytrail.c
> index 975572e..94902f7 100644
> --- a/drivers/pinctrl/pinctrl-baytrail.c
> +++ b/drivers/pinctrl/pinctrl-baytrail.c
> @@ -44,6 +44,7 @@
>
> /* BYT_CONF0_REG register bits */
> #define BYT_IODEN BIT(31)
> +#define BYT_DIRECT_IRQ BIT(27)
> #define BYT_TRIG_NEG BIT(26)
> #define BYT_TRIG_POS BIT(25)
> #define BYT_TRIG_LVL BIT(24)
> @@ -232,7 +233,7 @@ static int byt_irq_type(struct irq_data *d, unsigned type)
> /* 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 | BYT_TRIG_POS | BYT_TRIG_NEG | BYT_TRIG_LVL);
>
> switch (type) {
> case IRQ_TYPE_LEVEL_HIGH:
>
Just checked that there is a patch already upstream that warns if this bit is set.
It defines BYT_DIRECT_IRQ_EN already, but doesn't clear the bit.
commit ff998356b644ebe723127bd9eec6040b59a4a4f6
Author: Eric Ernst <eric.ernst@linux.intel.com>
Date: Thu Jun 12 11:06:20 2014 -0700
pinctrl: baytrail: Warn if direct IRQ GPIO set to output
Maybe adding a patch clearing the bit on top of that patch?
And send that patch to Linus Walleij as well (added to cc)
Thanks
-Mathias
next prev parent reply other threads:[~2014-09-17 13:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 12:30 [PATCH] pinctrl: baytrail: Clear DIRECT_IRQ bit Loic Poulain
2014-09-17 13:18 ` Mathias Nyman [this message]
2014-09-17 13:53 ` 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=54198A2D.30908@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.