linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jin, Yao" <yao.jin@linux.intel.com>
To: linus.walleij@linaro.org, linux-kernel@vger.kernel.org
Subject: [PATCH] pinctrl-baytrail: workaround for irq descriptor conflict on ASUS T100TA
Date: Mon, 14 Apr 2014 10:48:13 +0800	[thread overview]
Message-ID: <534B4C6D.5070003@linux.intel.com> (raw)
In-Reply-To: <1397443272-31467-1-git-send-email-yao.jin@linux.intel.com>

A crash is triggered on the ASUS T100TA Baytrail-T because of a IRQ
descriptor conflict. There are two gpio triggered acpi events in this
device, GPIO 6 and 18. These gpios are translated to irqs by calling
gpio_to_irq which in turn will call irq_create_mapping(vg->domain, offset).
irq_create_mapping will take care of allocating the irq descriptor, taking
the first available number starting from the given value (6 in our case).
The 0-15 are already reserved by legacy ISA code, so it gets the first
free irq descriptor which is number 16. The i915 driver also uses irq 16,
it loads later than gpio and crashes in probe.

The bug is reported here:
https://bugzilla.kernel.org/show_bug.cgi?id=68291

The rootcause we know now is a low level irq issue. It needs a long term
solution to fix the issue in irq system.

This patch is a workaround which changes the Baytrail GPIO driver to avoid
the IRQ conflict. It still uses the irq domain to allocate irq descriptor
but start from a predefined irq base number (256).

Signed-off-by: Jin Yao <yao.jin@linux.intel.com>
---
  drivers/pinctrl/pinctrl-baytrail.c | 37 
+++++++++++++++++++++++++++++--------
  1 file changed, 29 insertions(+), 8 deletions(-)

diff --git a/drivers/pinctrl/pinctrl-baytrail.c 
b/drivers/pinctrl/pinctrl-baytrail.c
index 6e8301f..45b2d81 100644
--- a/drivers/pinctrl/pinctrl-baytrail.c
+++ b/drivers/pinctrl/pinctrl-baytrail.c
@@ -124,6 +124,18 @@ static struct pinctrl_gpio_range byt_ranges[] = {
  	},
  };

+/*
+ * Start from an irq base number above x86 ioapic range to work around some
+ * nasty, which is still in 3.14 unresolved irq descriptor conflicts.
+ */
+#define BYT_GPIO_PIN_IRQBASE	256
+
+static int byt_pin_irqbase[] = {
+	BYT_GPIO_PIN_IRQBASE,
+	BYT_GPIO_PIN_IRQBASE + BYT_NGPIO_SCORE,
+	BYT_GPIO_PIN_IRQBASE + BYT_NGPIO_SCORE + BYT_NGPIO_NCORE,
+};
+
  struct byt_gpio {
  	struct gpio_chip		chip;
  	struct irq_domain		*domain;
@@ -131,6 +143,7 @@ struct byt_gpio {
  	spinlock_t			lock;
  	void __iomem			*reg_base;
  	struct pinctrl_gpio_range	*range;
+	int				pin_irqbase;
  };

  #define to_byt_gpio(c)	container_of(c, struct byt_gpio, chip)
@@ -481,7 +494,7 @@ static int byt_gpio_probe(struct platform_device *pdev)
  	struct pinctrl_gpio_range *range;
  	acpi_handle handle = ACPI_HANDLE(dev);
  	unsigned hwirq;
-	int ret;
+	int ret, i;

  	if (acpi_bus_get_device(handle, &acpi_dev))
  		return -ENODEV;
@@ -496,6 +509,12 @@ static int byt_gpio_probe(struct platform_device *pdev)
  		if (!strcmp(acpi_dev->pnp.unique_id, range->name)) {
  			vg->chip.ngpio = range->npins;
  			vg->range = range;
+			ret = kstrtol(range->name, 10, &i);
+			if (ret != 0)
+				return ret;
+
+			i--;
+			vg->pin_irqbase = byt_pin_irqbase[i];
  			break;
  		}
  	}
@@ -527,19 +546,14 @@ static int byt_gpio_probe(struct platform_device 
*pdev)
  	gc->can_sleep = false;
  	gc->dev = dev;

-	ret = gpiochip_add(gc);
-	if (ret) {
-		dev_err(&pdev->dev, "failed adding byt-gpio chip\n");
-		return ret;
-	}
-
  	/* set up interrupts  */
  	irq_rc = platform_get_resource(pdev, IORESOURCE_IRQ, 0);
  	if (irq_rc && irq_rc->start) {
  		hwirq = irq_rc->start;
  		gc->to_irq = byt_gpio_to_irq;

-		vg->domain = irq_domain_add_linear(NULL, gc->ngpio,
+		vg->domain = irq_domain_add_simple(NULL, gc->ngpio,
+						   vg->pin_irqbase,
  						   &byt_gpio_irq_ops, vg);
  		if (!vg->domain)
  			return -ENXIO;
@@ -550,6 +564,12 @@ static int byt_gpio_probe(struct platform_device *pdev)
  		irq_set_chained_handler(hwirq, byt_gpio_irq_handler);
  	}

+	ret = gpiochip_add(gc);
+	if (ret) {
+		dev_err(&pdev->dev, "failed adding byt-gpio chip\n");
+		return ret;
+	}
+
  	pm_runtime_enable(dev);

  	return 0;
@@ -572,6 +592,7 @@ static const struct dev_pm_ops byt_gpio_pm_ops = {

  static const struct acpi_device_id byt_gpio_acpi_match[] = {
  	{ "INT33B2", 0 },
+	{ "INT33FC", 0 },
  	{ }
  };
  MODULE_DEVICE_TABLE(acpi, byt_gpio_acpi_match);
-- 
1.8.3.2




       reply	other threads:[~2014-04-14  2:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1397443272-31467-1-git-send-email-yao.jin@linux.intel.com>
2014-04-14  2:48 ` Jin, Yao [this message]
2014-04-22 13:18   ` [PATCH] pinctrl-baytrail: workaround for irq descriptor conflict on ASUS T100TA Linus Walleij
2014-04-23  2:04     ` Jin, Yao
2014-04-23 11:35     ` Mathias Nyman
2014-04-23 14:28       ` Linus Walleij
2014-04-24  7:25         ` Thomas Gleixner
2014-04-24 13:19           ` Linus Walleij
2014-04-24 14:40             ` Thomas Gleixner
2014-04-25  9:45               ` Mika Westerberg
2014-04-28 10:25               ` [tip:irq/urgent] genirq: x86: Ensure that dynamic irq allocation does not conflict tip-bot for Thomas Gleixner
2014-04-23 15:33       ` [PATCH] pinctrl-baytrail: workaround for irq descriptor conflict on ASUS T100TA Andy Shevchenko

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=534B4C6D.5070003@linux.intel.com \
    --to=yao.jin@linux.intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.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).