From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH v2 3/3] pinctrl: cherryview: Pass irqchip when adding gpiochip
Date: Wed, 6 Nov 2019 18:16:22 +0200 [thread overview]
Message-ID: <20191106161622.GM32742@smile.fi.intel.com> (raw)
In-Reply-To: <20191106154715.155596-4-hdegoede@redhat.com>
On Wed, Nov 06, 2019 at 04:47:15PM +0100, Hans de Goede wrote:
> We need to convert all old gpio irqchips to pass the irqchip
> setup along when adding the gpio_chip. For more info see
> drivers/gpio/TODO.
>
> For chained irqchips this is a pretty straight-forward conversion.
> + chip->irq.chip = &pctrl->irqchip;
> + if (pctrl->need_valid_mask)
> + chip->irq.init_valid_mask = chv_init_irq_valid_mask;
I just realize we probably may assign here unconditionally
> + chip->irq.init_hw = chv_gpio_irq_init_hw;
> + chip->irq.parent_handler = chv_gpio_irq_handler;
> + chip->irq.num_parents = 1;
> + chip->irq.parents = &pctrl->irq;
> + chip->irq.default_type = IRQ_TYPE_NONE;
> + chip->irq.handler = handle_bad_irq;
>
> if (!pctrl->need_valid_mask) {
> irq_base = devm_irq_alloc_descs(pctrl->dev, -1, 0,
> @@ -1640,18 +1651,9 @@ static int chv_gpio_probe(struct chv_pinctrl *pctrl, int irq)
> }
> }
>
> - pctrl->irqchip.name = "chv-gpio";
> - pctrl->irqchip.irq_startup = chv_gpio_irq_startup;
> - pctrl->irqchip.irq_ack = chv_gpio_irq_ack;
> - pctrl->irqchip.irq_mask = chv_gpio_irq_mask;
> - pctrl->irqchip.irq_unmask = chv_gpio_irq_unmask;
> - pctrl->irqchip.irq_set_type = chv_gpio_irq_type;
> - pctrl->irqchip.flags = IRQCHIP_SKIP_SET_WAKE;
> -
> - ret = gpiochip_irqchip_add(chip, &pctrl->irqchip, 0,
> - handle_bad_irq, IRQ_TYPE_NONE);
> + ret = devm_gpiochip_add_data(pctrl->dev, chip, pctrl);
> if (ret) {
> - dev_err(pctrl->dev, "failed to add IRQ chip\n");
> + dev_err(pctrl->dev, "Failed to register gpiochip\n");
> return ret;
> }
>
> @@ -1665,8 +1667,6 @@ static int chv_gpio_probe(struct chv_pinctrl *pctrl, int irq)
> }
> }
>
> - gpiochip_set_chained_irqchip(chip, &pctrl->irqchip, irq,
> - chv_gpio_irq_handler);
> return 0;
> }
>
> --
> 2.23.0
>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2019-11-06 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 15:47 [PATCH v2 0/3] pinctrl: cherryview: Pass irqchip when adding gpiochip Hans de Goede
2019-11-06 15:47 ` [PATCH v2 1/3] pinctrl: cherryview: Split out irq hw-init into a separate helper function Hans de Goede
2019-11-06 15:47 ` [PATCH v2 2/3] pinctrl: cherryview: Add GPIO <-> pin mapping ranges via callback Hans de Goede
2019-11-06 15:47 ` [PATCH v2 3/3] pinctrl: cherryview: Pass irqchip when adding gpiochip Hans de Goede
2019-11-06 16:16 ` Andy Shevchenko [this message]
2019-11-06 16:17 ` Andy Shevchenko
2019-11-13 18:52 ` Hans de Goede
2019-11-06 16:18 ` [PATCH v2 0/3] " Andy Shevchenko
2019-11-06 17:47 ` Mika Westerberg
2019-11-07 9:41 ` 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=20191106161622.GM32742@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bgolaszewski@baylibre.com \
--cc=hdegoede@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mika.westerberg@linux.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