From: mika.westerberg@linux.intel.com (Mika Westerberg)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] pinctrl: baytrail: lock IRQs when starting them
Date: Wed, 4 Dec 2013 12:57:18 +0200 [thread overview]
Message-ID: <20131204105718.GV2281@intel.com> (raw)
In-Reply-To: <529E008A.6030704@linux.intel.com>
On Tue, Dec 03, 2013 at 06:02:18PM +0200, Mathias Nyman wrote:
> On 12/03/2013 05:00 PM, Linus Walleij wrote:
> >This uses the new API for tagging GPIO lines as in use by
> >IRQs. This enforces a few semantic checks on how the underlying
> >GPIO line is used.
> >
> >Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> >Cc: Mika Westerberg <mika.westerberg@linux.intel.com>
> >Cc: Mathias Nyman <mathias.nyman@linux.intel.com>
> >Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> >---
> >ChangeLog v1->v2:
> >- Actually make the change compile, doh.
> >---
> > drivers/pinctrl/pinctrl-baytrail.c | 22 ++++++++++++++++++++++
> > 1 file changed, 22 insertions(+)
> >
> >diff --git a/drivers/pinctrl/pinctrl-baytrail.c b/drivers/pinctrl/pinctrl-baytrail.c
> >index 1174ea86b6e9..998dbb0c4c93 100644
> >--- a/drivers/pinctrl/pinctrl-baytrail.c
> >+++ b/drivers/pinctrl/pinctrl-baytrail.c
> >@@ -372,11 +372,33 @@ static void byt_irq_mask(struct irq_data *d)
> > {
> > }
> >
> >+static unsigned int byt_irq_startup(struct irq_data *d)
> >+{
> >+ struct byt_gpio *vg = irq_data_get_irq_handler_data(d);
>
> This should probably be:
>
> struct byt_gpio *vg = irq_data_get_irq_chip_data(d);
>
> As chip methods use irq_data->chip_data, not irq_data->handler_data
> (Mika tested that it works on baytrail)
Yes, if it uses irq_data_get_irq_handler_data() I get NULL vg pointer and
the kernel crashes. Using irq_data_get_irq_chip_data() makes it work.
next prev parent reply other threads:[~2013-12-04 10:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 15:00 [PATCH v2] pinctrl: baytrail: lock IRQs when starting them Linus Walleij
2013-12-03 16:02 ` Mathias Nyman
2013-12-04 10:57 ` Mika Westerberg [this message]
2013-12-04 13:26 ` Gerhard Sittig
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=20131204105718.GV2281@intel.com \
--to=mika.westerberg@linux.intel.com \
--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).