From: Lee Jones <lee.jones@linaro.org>
To: Axel Lin <axel.lin@ingics.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Milo Kim <milo.kim@ti.com>, Alexandre Courbot <gnurou@gmail.com>,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH] gpio: lp3943: Drop pin_used and lp3943_gpio_request/lp3943_gpio_free
Date: Wed, 9 Mar 2016 12:37:03 +0700 [thread overview]
Message-ID: <20160309053703.GO13692@x1> (raw)
In-Reply-To: <1456751299.25756.0.camel@ingics.com>
On Mon, 29 Feb 2016, Axel Lin wrote:
> The implementation of lp3943_gpio_request/lp3943_gpio_free test pin_used
> for tracing the pin usage. However, gpiolib already checks FLAG_REQUESTED
> flag for the same purpose. So remove the redundant implementation.
>
> Signed-off-by: Axel Lin <axel.lin@ingics.com>
> ---
> drivers/gpio/gpio-lp3943.c | 22 ----------------------
> include/linux/mfd/lp3943.h | 6 ------
> 2 files changed, 28 deletions(-)
Acked-by: Lee Jones <lee.jones@linaro.org>
> diff --git a/drivers/gpio/gpio-lp3943.c b/drivers/gpio/gpio-lp3943.c
> index 1c8e2ae..9d26ad4 100644
> --- a/drivers/gpio/gpio-lp3943.c
> +++ b/drivers/gpio/gpio-lp3943.c
> @@ -45,26 +45,6 @@ struct lp3943_gpio {
> u16 input_mask; /* 1 = GPIO is input direction, 0 = output */
> };
>
> -static int lp3943_gpio_request(struct gpio_chip *chip, unsigned offset)
> -{
> - struct lp3943_gpio *lp3943_gpio = gpiochip_get_data(chip);
> - struct lp3943 *lp3943 = lp3943_gpio->lp3943;
> -
> - /* Return an error if the pin is already assigned */
> - if (test_and_set_bit(offset, &lp3943->pin_used))
> - return -EBUSY;
> -
> - return 0;
> -}
> -
> -static void lp3943_gpio_free(struct gpio_chip *chip, unsigned offset)
> -{
> - struct lp3943_gpio *lp3943_gpio = gpiochip_get_data(chip);
> - struct lp3943 *lp3943 = lp3943_gpio->lp3943;
> -
> - clear_bit(offset, &lp3943->pin_used);
> -}
> -
> static int lp3943_gpio_set_mode(struct lp3943_gpio *lp3943_gpio, u8 offset,
> u8 val)
> {
> @@ -177,8 +157,6 @@ static int lp3943_gpio_direction_output(struct gpio_chip *chip, unsigned offset,
> static const struct gpio_chip lp3943_gpio_chip = {
> .label = "lp3943",
> .owner = THIS_MODULE,
> - .request = lp3943_gpio_request,
> - .free = lp3943_gpio_free,
> .direction_input = lp3943_gpio_direction_input,
> .get = lp3943_gpio_get,
> .direction_output = lp3943_gpio_direction_output,
> diff --git a/include/linux/mfd/lp3943.h b/include/linux/mfd/lp3943.h
> index 3490db7..d3a73811 100644
> --- a/include/linux/mfd/lp3943.h
> +++ b/include/linux/mfd/lp3943.h
> @@ -94,18 +94,12 @@ struct lp3943_reg_cfg {
> * @regmap: Used for I2C communication on accessing registers
> * @pdata: LP3943 platform specific data
> * @mux_cfg: Register configuration for pin MUX
> - * @pin_used: Bit mask for output pin used.
> - * This bitmask is used for pin assignment management.
> - * 1 = pin used, 0 = available.
> - * Only LSB 16 bits are used, but it is unsigned long type
> - * for atomic bitwise operations.
> */
> struct lp3943 {
> struct device *dev;
> struct regmap *regmap;
> struct lp3943_platform_data *pdata;
> const struct lp3943_reg_cfg *mux_cfg;
> - unsigned long pin_used;
> };
>
> int lp3943_read_byte(struct lp3943 *lp3943, u8 reg, u8 *read);
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-03-09 5:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 13:08 [PATCH] gpio: lp3943: Drop pin_used and lp3943_gpio_request/lp3943_gpio_free Axel Lin
2016-03-09 2:18 ` Linus Walleij
2016-03-09 5:37 ` Lee Jones [this message]
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=20160309053703.GO13692@x1 \
--to=lee.jones@linaro.org \
--cc=axel.lin@ingics.com \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=milo.kim@ti.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).