public inbox for linux-gpio@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Linus Walleij <linus.walleij@linaro.org>, linux-gpio@vger.kernel.org
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Bin Gao <bin.gao@linux.intel.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH] gpio: wcove: Use irqchip template
Date: Wed, 22 Jul 2020 10:57:08 +0200	[thread overview]
Message-ID: <840db56f-d041-6bac-fdca-3dd26152e313@redhat.com> (raw)
In-Reply-To: <20200717151955.159819-1-linus.walleij@linaro.org>

Hi,

On 7/17/20 5:19 PM, Linus Walleij wrote:
> This makes the driver use the irqchip template to assign
> properties to the gpio_irq_chip instead of using the
> explicit calls to gpiochip_irqchip_add_nested() and
> gpiochip_set_nested_irqchip(). The irqchip is instead
> added while adding the gpiochip.
> 
> Cc: Bin Gao <bin.gao@linux.intel.com>
> Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Cc: Hans de Goede <hdegoede@redhat.com>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> Same notices as on the Crystalcove: this one I actually
> managed to compiletest properly.

I've given this patch a test-run on a machine with the
Whiskey Cove PMIC and with the caveat that I've not
actually tested the GPIO IRQ functionality, since that
does not seem to be used on any machines, I see no adverse
side effects from this patch, so it is:

Tested-by: Hans de Goede <hdegoede@redhat.com>

Regards,

Hans




> ---
>   drivers/gpio/gpio-wcove.c | 30 ++++++++++++++++--------------
>   1 file changed, 16 insertions(+), 14 deletions(-)
> 
> diff --git a/drivers/gpio/gpio-wcove.c b/drivers/gpio/gpio-wcove.c
> index 8b481b3c1ebe..135645096575 100644
> --- a/drivers/gpio/gpio-wcove.c
> +++ b/drivers/gpio/gpio-wcove.c
> @@ -400,6 +400,7 @@ static int wcove_gpio_probe(struct platform_device *pdev)
>   	struct wcove_gpio *wg;
>   	int virq, ret, irq;
>   	struct device *dev;
> +	struct gpio_irq_chip *girq;
>   
>   	/*
>   	 * This gpio platform device is created by a mfd device (see
> @@ -442,19 +443,6 @@ static int wcove_gpio_probe(struct platform_device *pdev)
>   	wg->dev = dev;
>   	wg->regmap = pmic->regmap;
>   
> -	ret = devm_gpiochip_add_data(dev, &wg->chip, wg);
> -	if (ret) {
> -		dev_err(dev, "Failed to add gpiochip: %d\n", ret);
> -		return ret;
> -	}
> -
> -	ret = gpiochip_irqchip_add_nested(&wg->chip, &wcove_irqchip, 0,
> -					  handle_simple_irq, IRQ_TYPE_NONE);
> -	if (ret) {
> -		dev_err(dev, "Failed to add irqchip: %d\n", ret);
> -		return ret;
> -	}
> -
>   	virq = regmap_irq_get_virq(wg->regmap_irq_chip, irq);
>   	if (virq < 0) {
>   		dev_err(dev, "Failed to get virq by irq %d\n", irq);
> @@ -468,7 +456,21 @@ static int wcove_gpio_probe(struct platform_device *pdev)
>   		return ret;
>   	}
>   
> -	gpiochip_set_nested_irqchip(&wg->chip, &wcove_irqchip, virq);
> +	girq = &wg->chip.irq;
> +	girq->chip = &wcove_irqchip;
> +	/* This will let us handle the parent IRQ in the driver */
> +	girq->parent_handler = NULL;
> +	girq->num_parents = 0;
> +	girq->parents = NULL;
> +	girq->default_type = IRQ_TYPE_NONE;
> +	girq->handler = handle_simple_irq;
> +	girq->threaded = true;
> +
> +	ret = devm_gpiochip_add_data(dev, &wg->chip, wg);
> +	if (ret) {
> +		dev_err(dev, "Failed to add gpiochip: %d\n", ret);
> +		return ret;
> +	}
>   
>   	/* Enable GPIO0 interrupts */
>   	ret = regmap_update_bits(wg->regmap, IRQ_MASK_BASE, GPIO_IRQ0_MASK,
> 


  reply	other threads:[~2020-07-22  8:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17 15:19 [PATCH] gpio: wcove: Use irqchip template Linus Walleij
2020-07-22  8:57 ` Hans de Goede [this message]
2020-07-22 10:58   ` 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=840db56f-d041-6bac-fdca-3dd26152e313@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=bin.gao@linux.intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@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