From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7] reset: Add driver for gpio-controlled reset pins
Date: Wed, 29 May 2013 17:19:20 -0600 [thread overview]
Message-ID: <51A68CF8.7000303@wwwdotorg.org> (raw)
In-Reply-To: <1369753575-9818-1-git-send-email-p.zabel@pengutronix.de>
On 05/28/2013 09:06 AM, Philipp Zabel wrote:
> This driver implements a reset controller device that toggle a gpio
> connected to a reset pin of a peripheral IC. The delay between assertion
> and de-assertion of the reset signal can be configured via device tree.
> diff --git a/drivers/reset/gpio-reset.c b/drivers/reset/gpio-reset.c
> +static void __gpio_reset_set(struct reset_controller_dev *rcdev, int asserted)
Nit: Technically I think __ is a reserved name-space, so you shouldn't
prefix "user-level" (rather than libc/similar) symbols with it, but it's
not a big deal.
> +static int gpio_reset_probe(struct platform_device *pdev)
> + if (of_gpio_named_count(np, "reset-gpios") != 1)
> + return -EINVAL;
Should that error-path (and the path for of_property_read_u32() failure)
include a dev_err() like some already do, so it's obvious what the
failure is?
> + reset_controller_register(&drvdata->rcdev);
> +
> + platform_set_drvdata(pdev, drvdata);
It might be better to set the drvdata right after it's been allocated.
It perhaps doesn't matter much here, but if the reset controller core
ever starts calling into the registered device inside the call to
reset_controller_register(), then there might be a problem.
Aside from those minor issues,
Reviewed-by: Stephen Warren <swarren@nvidia.com>
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Philipp Zabel <p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>,
Fabio Estevam
<fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
Mike Turquette
<mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Sascha Hauer <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
"Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org>,
Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH v7] reset: Add driver for gpio-controlled reset pins
Date: Wed, 29 May 2013 17:19:20 -0600 [thread overview]
Message-ID: <51A68CF8.7000303@wwwdotorg.org> (raw)
In-Reply-To: <1369753575-9818-1-git-send-email-p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
On 05/28/2013 09:06 AM, Philipp Zabel wrote:
> This driver implements a reset controller device that toggle a gpio
> connected to a reset pin of a peripheral IC. The delay between assertion
> and de-assertion of the reset signal can be configured via device tree.
> diff --git a/drivers/reset/gpio-reset.c b/drivers/reset/gpio-reset.c
> +static void __gpio_reset_set(struct reset_controller_dev *rcdev, int asserted)
Nit: Technically I think __ is a reserved name-space, so you shouldn't
prefix "user-level" (rather than libc/similar) symbols with it, but it's
not a big deal.
> +static int gpio_reset_probe(struct platform_device *pdev)
> + if (of_gpio_named_count(np, "reset-gpios") != 1)
> + return -EINVAL;
Should that error-path (and the path for of_property_read_u32() failure)
include a dev_err() like some already do, so it's obvious what the
failure is?
> + reset_controller_register(&drvdata->rcdev);
> +
> + platform_set_drvdata(pdev, drvdata);
It might be better to set the drvdata right after it's been allocated.
It perhaps doesn't matter much here, but if the reset controller core
ever starts calling into the registered device inside the call to
reset_controller_register(), then there might be a problem.
Aside from those minor issues,
Reviewed-by: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
next prev parent reply other threads:[~2013-05-29 23:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 15:06 [PATCH v7] reset: Add driver for gpio-controlled reset pins Philipp Zabel
2013-05-28 15:06 ` Philipp Zabel
2013-05-29 23:19 ` Stephen Warren [this message]
2013-05-29 23:19 ` Stephen Warren
2013-05-30 9:08 ` Philipp Zabel
2013-05-30 9:08 ` Philipp Zabel
2013-05-30 10:38 ` Pavel Machek
2013-05-30 10:38 ` Pavel Machek
2013-05-30 13:16 ` Arnd Bergmann
2013-05-30 13:16 ` Arnd Bergmann
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=51A68CF8.7000303@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.