From: Stephen Warren <swarren@nvidia.com>
To: Denis Kuzmenko <linux@solonet.org.ua>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Grant Likely <grant.likely@secretlab.ca>,
Linus Walleij <linus.walleij@linaro.org>,
Richard Purdie <rpurdie@rpsys.net>,
Wolfram Sang <w.sang@pengutronix.de>
Subject: RE: [PATCH] s3c/s3c24xx: arm: leds: Make s3c24xx LEDS driver use gpiolib
Date: Fri, 18 Nov 2011 13:59:33 -0800 [thread overview]
Message-ID: <74CDBE0F657A3D45AFBB94109FB122FF1740D74FAD@HQMAIL01.nvidia.com> (raw)
In-Reply-To: <4EC6D1D5.9060808@solonet.org.ua>
Denis Kuzmenko wrote at Friday, November 18, 2011 2:45 PM:
> Make s3c24xx LEDS driver use gpiolib. Disable using pull-resistor when not
> using S3C24XX_LEDF_TRISTATE and enble it when in opposite case.
>
> Signed-off-by: Denis Kuzmenko <linux@solonet.org.ua>
> if (pdata->flags & S3C24XX_LEDF_TRISTATE) {
> - s3c2410_gpio_setpin(pdata->gpio, 0);
> - s3c2410_gpio_cfgpin(pdata->gpio, S3C2410_GPIO_INPUT);
> + /*
> + * pull is needed here to protect pin from being left
> + * floating
> + */
> + ret = s3c_gpio_setpull(pdata->gpio, S3C_GPIO_PULL_UP);
> + if (ret)
> + s3c_gpio_setpull(pdata->gpio, S3C_GPIO_PULL_DOWN);
Sorry, could you explain why it's appropriate to configure a pull here
at all, let alone why it's OK to have a random pull on the line?
> + /* initially turn off led */
> + ret = gpio_direction_input(pdata->gpio);
> } else {
> - s3c2410_gpio_pullup(pdata->gpio, 0);
> - s3c2410_gpio_setpin(pdata->gpio, 0);
> - s3c2410_gpio_cfgpin(pdata->gpio, S3C2410_GPIO_OUTPUT);
> + /* no point in having a pull-up as we are always driving */
> + s3c_gpio_setpull(pdata->gpio, S3C_GPIO_PULL_NONE);
> + ret = gpio_request_one(pdata->gpio, GPIOF_OUT_INIT_LOW,
> + pdata->name);
> + /* initially turn off led */
> + ret = gpio_direction_output(pdata->gpio,
> + !!(pdata->flags & S3C24XX_LEDF_ACTLOW));
Wouldn't it be better to pass GPIOF_OUT_INIT_HIGH or GPIOF_OUT_INIT_LOW
to gpio_request_one() based on S3C24XX_LEDF_ACTLOW, and avoid the call to
gpio_direction_output; that will avoid glitching the line for a short time.
I'm fine with the rest of the code.
--
nvpublic
next prev parent reply other threads:[~2011-11-18 21:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 20:47 Denis Kuzmenko
2011-11-18 17:08 ` Stephen Warren
2011-11-18 21:00 ` Denis Kuzmenko
2011-11-18 21:44 ` Denis Kuzmenko
2011-11-18 21:59 ` Stephen Warren [this message]
2011-11-18 22:34 ` Denis Kuzmenko
2011-11-18 22:39 ` [PATCH v2] " Denis Kuzmenko
2011-11-18 22:44 ` [PATCH] " Stephen Warren
2011-11-18 23:16 ` Denis Kuzmenko
2011-11-21 18:07 ` Stephen Warren
2011-11-21 19:37 ` Denis Kuzmenko
2011-11-21 22:03 ` Stephen Warren
2011-11-21 22:52 ` Denis Kuzmenko
2011-11-21 23:39 ` Stephen Warren
2011-11-22 0:28 ` Denis Kuzmenko
2011-11-22 0:40 ` Stephen Warren
2011-11-18 21:47 ` Stephen Warren
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=74CDBE0F657A3D45AFBB94109FB122FF1740D74FAD@HQMAIL01.nvidia.com \
--to=swarren@nvidia.com \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@solonet.org.ua \
--cc=rpurdie@rpsys.net \
--cc=w.sang@pengutronix.de \
/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
all inboxes | Powered by JetHome®