From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
linux-sh@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH 1/7] gpio: rcar: Add helper variable dev = &pdev->dev
Date: Fri, 28 Mar 2014 17:57:17 +0100 [thread overview]
Message-ID: <1679540.TxvK82nUub@avalon> (raw)
In-Reply-To: <1395953262-4290-2-git-send-email-geert@linux-m68k.org>
Hi Geert,
Thank you for the patch.
On Thursday 27 March 2014 21:47:36 Geert Uytterhoeven wrote:
> From: Geert Uytterhoeven <geert+renesas@glider.be>
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Cc: Linus Walleij <linus.walleij@linaro.org>
> Cc: Laurent Pinchart <Laurent.pinchart@ideasonboard.com>
> Cc: linux-gpio@vger.kernel.org
I'm not sure if I would have bothered, but I have nothing against this :-)
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
> drivers/gpio/gpio-rcar.c | 32 ++++++++++++++++----------------
> 1 file changed, 16 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/gpio/gpio-rcar.c b/drivers/gpio/gpio-rcar.c
> index ca76ce751540..03c91482432c 100644
> --- a/drivers/gpio/gpio-rcar.c
> +++ b/drivers/gpio/gpio-rcar.c
> @@ -356,12 +356,13 @@ static int gpio_rcar_probe(struct platform_device
> *pdev) struct resource *io, *irq;
> struct gpio_chip *gpio_chip;
> struct irq_chip *irq_chip;
> - const char *name = dev_name(&pdev->dev);
> + struct device *dev = &pdev->dev;
> + const char *name = dev_name(dev);
> int ret;
>
> - p = devm_kzalloc(&pdev->dev, sizeof(*p), GFP_KERNEL);
> + p = devm_kzalloc(dev, sizeof(*p), GFP_KERNEL);
> if (!p) {
> - dev_err(&pdev->dev, "failed to allocate driver data\n");
> + dev_err(dev, "failed to allocate driver data\n");
> ret = -ENOMEM;
> goto err0;
> }
> @@ -380,15 +381,14 @@ static int gpio_rcar_probe(struct platform_device
> *pdev) irq = platform_get_resource(pdev, IORESOURCE_IRQ, 0);
>
> if (!io || !irq) {
> - dev_err(&pdev->dev, "missing IRQ or IOMEM\n");
> + dev_err(dev, "missing IRQ or IOMEM\n");
> ret = -EINVAL;
> goto err0;
> }
>
> - p->base = devm_ioremap_nocache(&pdev->dev, io->start,
> - resource_size(io));
> + p->base = devm_ioremap_nocache(dev, io->start, resource_size(io));
> if (!p->base) {
> - dev_err(&pdev->dev, "failed to remap I/O memory\n");
> + dev_err(dev, "failed to remap I/O memory\n");
> ret = -ENXIO;
> goto err0;
> }
> @@ -402,7 +402,7 @@ static int gpio_rcar_probe(struct platform_device *pdev)
> gpio_chip->set = gpio_rcar_set;
> gpio_chip->to_irq = gpio_rcar_to_irq;
> gpio_chip->label = name;
> - gpio_chip->dev = &pdev->dev;
> + gpio_chip->dev = dev;
> gpio_chip->owner = THIS_MODULE;
> gpio_chip->base = p->config.gpio_base;
> gpio_chip->ngpio = p->config.number_of_pins;
> @@ -421,30 +421,30 @@ static int gpio_rcar_probe(struct platform_device
> *pdev) &gpio_rcar_irq_domain_ops, p);
> if (!p->irq_domain) {
> ret = -ENXIO;
> - dev_err(&pdev->dev, "cannot initialize irq domain\n");
> + dev_err(dev, "cannot initialize irq domain\n");
> goto err0;
> }
>
> - if (devm_request_irq(&pdev->dev, irq->start,
> - gpio_rcar_irq_handler, IRQF_SHARED, name, p)) {
> - dev_err(&pdev->dev, "failed to request IRQ\n");
> + if (devm_request_irq(dev, irq->start, gpio_rcar_irq_handler,
> + IRQF_SHARED, name, p)) {
> + dev_err(dev, "failed to request IRQ\n");
> ret = -ENOENT;
> goto err1;
> }
>
> ret = gpiochip_add(gpio_chip);
> if (ret) {
> - dev_err(&pdev->dev, "failed to add GPIO controller\n");
> + dev_err(dev, "failed to add GPIO controller\n");
> goto err1;
> }
>
> - dev_info(&pdev->dev, "driving %d GPIOs\n", p->config.number_of_pins);
> + dev_info(dev, "driving %d GPIOs\n", p->config.number_of_pins);
>
> /* warn in case of mismatch if irq base is specified */
> if (p->config.irq_base) {
> ret = irq_find_mapping(p->irq_domain, 0);
> if (p->config.irq_base != ret)
> - dev_warn(&pdev->dev, "irq base mismatch (%u/%u)\n",
> + dev_warn(dev, "irq base mismatch (%u/%u)\n",
> p->config.irq_base, ret);
> }
>
> @@ -452,7 +452,7 @@ static int gpio_rcar_probe(struct platform_device *pdev)
> ret = gpiochip_add_pin_range(gpio_chip, p->config.pctl_name, 0,
> gpio_chip->base, gpio_chip->ngpio);
> if (ret < 0)
> - dev_warn(&pdev->dev, "failed to add pin range\n");
> + dev_warn(dev, "failed to add pin range\n");
> }
>
> return 0;
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-03-28 16:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1395953262-4290-1-git-send-email-geert@linux-m68k.org>
2014-03-27 20:47 ` [PATCH 1/7] gpio: rcar: Add helper variable dev = &pdev->dev Geert Uytterhoeven
2014-03-28 16:57 ` Laurent Pinchart [this message]
2014-03-28 20:55 ` Linus Walleij
2014-03-27 20:47 ` [PATCH 2/7] gpio: rcar: Add optional functional clock to bindings Geert Uytterhoeven
2014-03-28 16:53 ` Laurent Pinchart
2014-03-31 9:55 ` Geert Uytterhoeven
2014-03-31 10:15 ` Laurent Pinchart
2014-03-27 20:47 ` [PATCH 3/7] gpio: rcar: Add minimal runtime PM support Geert Uytterhoeven
2014-03-28 16:54 ` Laurent Pinchart
2014-03-31 10:04 ` Geert Uytterhoeven
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=1679540.TxvK82nUub@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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;
as well as URLs for NNTP newsgroup(s).