Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: Serge Semin <fancer.lancer@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Patrice Chotard <patrice.chotard@st.com>,
	Alexandre TORGUE <alexandre.torgue@st.com>
Subject: Re: [PATCH] gpio: stmpe: Use irqchip template
Date: Tue, 28 Jul 2020 00:13:31 +0300	[thread overview]
Message-ID: <20200727211331.npttctrjmkfhezhn@mobilestation> (raw)
In-Reply-To: <20200716100638.112451-1-linus.walleij@linaro.org>

On Thu, Jul 16, 2020 at 12:06:38PM +0200, 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: Patrice Chotard <patrice.chotard@st.com>
> Cc: Alexandre TORGUE <alexandre.torgue@st.com>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
>  drivers/gpio/gpio-stmpe.c | 24 +++++++++++-------------
>  1 file changed, 11 insertions(+), 13 deletions(-)
> 
> diff --git a/drivers/gpio/gpio-stmpe.c b/drivers/gpio/gpio-stmpe.c
> index 542706a852e6..395ee51445ea 100644
> --- a/drivers/gpio/gpio-stmpe.c
> +++ b/drivers/gpio/gpio-stmpe.c
> @@ -507,6 +507,8 @@ static int stmpe_gpio_probe(struct platform_device *pdev)
>  	}
>  
>  	if (irq > 0) {
> +		struct gpio_irq_chip *girq;
> +
>  		ret = devm_request_threaded_irq(&pdev->dev, irq, NULL,
>  				stmpe_gpio_irq, IRQF_ONESHOT,
>  				"stmpe-gpio", stmpe_gpio);
> @@ -514,20 +516,16 @@ static int stmpe_gpio_probe(struct platform_device *pdev)
>  			dev_err(&pdev->dev, "unable to get irq: %d\n", ret);
>  			goto out_disable;
>  		}
> -		ret =  gpiochip_irqchip_add_nested(&stmpe_gpio->chip,
> -						   &stmpe_gpio_irq_chip,
> -						   0,
> -						   handle_simple_irq,
> -						   IRQ_TYPE_NONE);
> -		if (ret) {
> -			dev_err(&pdev->dev,
> -				"could not connect irqchip to gpiochip\n");
> -			goto out_disable;
> -		}
>  
> -		gpiochip_set_nested_irqchip(&stmpe_gpio->chip,
> -					    &stmpe_gpio_irq_chip,
> -					    irq);

> +		girq = &stmpe_gpio->chip.irq;
> +		girq->chip = &stmpe_gpio_irq_chip;
> +		/* 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;

Hmm, the GPIO-irq-chip setting are initialized after the GPIO-chip has been
registered by calling the gpiochip_add_data() method earlier in this method.
That means the IRQ-chip won't be created by the GPIOlib, which will introduce a
bug. In order to fix the problem it's better to move the whole "if (irq > 0)
{...}" clause to be executed before the gpiochip_add_data() function invocation.

Though I could misunderstood something...

-Sergey

>  	}
>  
>  	platform_set_drvdata(pdev, stmpe_gpio);
> -- 
> 2.26.2
> 

  parent reply	other threads:[~2020-07-27 21:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16 10:06 [PATCH] gpio: stmpe: Use irqchip template Linus Walleij
2020-07-27 12:32 ` Patrice CHOTARD
2020-07-27 21:13 ` Serge Semin [this message]
2020-07-28  7:28   ` Linus Walleij

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=20200727211331.npttctrjmkfhezhn@mobilestation \
    --to=fancer.lancer@gmail.com \
    --cc=alexandre.torgue@st.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=patrice.chotard@st.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