From: Roger Quadros <rogerq@kernel.org>
To: Shree Ramamoorthy <s-ramamoorthy@ti.com>,
aaro.koskinen@iki.fi, andreas@kemnade.info, khilman@baylibre.com,
tony@atomide.com, linus.walleij@linaro.org, brgl@bgdev.pl,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org
Cc: m-leonard@ti.com, praneeth@ti.com, christophe.jaillet@wanadoo.fr
Subject: Re: [PATCH v2 3/3] gpio tps65215: Add support for varying gpio/offset values
Date: Sat, 4 Jan 2025 20:27:13 +0200 [thread overview]
Message-ID: <a34f42fb-30e0-426b-8efe-9be0c0494fe7@kernel.org> (raw)
In-Reply-To: <20250103225407.196068-4-s-ramamoorthy@ti.com>
On 04/01/2025 00:54, Shree Ramamoorthy wrote:
> Add device-specific structs to select the different PMIC .npgio and .offset
> values. With the chip_data struct values selected based on the match data,
> having a separate GPIO0_OFFSET macro is no longer needed.
>
> Signed-off-by: Shree Ramamoorthy <s-ramamoorthy@ti.com>
> ---
> drivers/gpio/gpio-tps65219.c | 27 ++++++++++++++++++++++++---
> 1 file changed, 24 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpio/gpio-tps65219.c b/drivers/gpio/gpio-tps65219.c
> index 70a4410c473a..14286dd5fdfb 100644
> --- a/drivers/gpio/gpio-tps65219.c
> +++ b/drivers/gpio/gpio-tps65219.c
> @@ -13,7 +13,6 @@
> #include <linux/regmap.h>
>
> #define TPS65219_GPIO0_DIR_MASK BIT(3)
> -#define TPS65219_GPIO0_OFFSET 2
> #define TPS6521X_GPIO0_IDX 0
>
> struct tps65219_gpio {
> @@ -21,6 +20,11 @@ struct tps65219_gpio {
> struct tps65219 *tps;
> };
>
> +struct tps65219_chip_data {
> + int ngpio;
> + int offset;
> +};
> +
> static int tps65219_gpio_get_direction(struct gpio_chip *gc, unsigned int offset)
> {
> struct tps65219_gpio *gpio = gpiochip_get_data(gc);
> @@ -71,7 +75,7 @@ static void tps65219_gpio_set(struct gpio_chip *gc, unsigned int offset, int val
> struct device *dev = gpio->tps->dev;
> int v, mask, bit;
>
> - bit = (offset == TPS6521X_GPIO0_IDX) ? TPS65219_GPIO0_OFFSET : offset - 1;
> + bit = (offset == TPS6521X_GPIO0_IDX) ? (gpio->gpio_chip.ngpio - 1) : offset - 1;
shouldn't this be
bit = (offset == TPS6521X_GPIO0_IDX) ? (gpio->gpio_chip.offset - 1) : offset - 1;
>
> mask = BIT(bit);
> v = value ? mask : 0;
> @@ -148,14 +152,29 @@ static const struct gpio_chip tps65219_template_chip = {
> .get = tps65219_gpio_get,
> .set = tps65219_gpio_set,
> .base = -1,
> - .ngpio = 3,
> .can_sleep = true,
> };
>
> +static const struct tps65219_chip_data chip_info_table[] = {
> + [TPS65215] = {
> + .ngpio = 2,
> + .offset = 1,
> + },
> + [TPS65219] = {
> + .ngpio = 3,
> + .offset = 2,
> + },
> +};
> +
> static int tps65219_gpio_probe(struct platform_device *pdev)
> {
> struct tps65219 *tps = dev_get_drvdata(pdev->dev.parent);
> struct tps65219_gpio *gpio;
> + const struct tps65219_chip_data *pmic;
> +
> + enum pmic_id chip = platform_get_device_id(pdev)->driver_data;
> +
unnecessary newline?
> + pmic = &chip_info_table[chip];
>
here too?
> gpio = devm_kzalloc(&pdev->dev, sizeof(*gpio), GFP_KERNEL);
> if (!gpio)
> @@ -164,6 +183,8 @@ static int tps65219_gpio_probe(struct platform_device *pdev)
> gpio->tps = tps;
> gpio->gpio_chip = tps65219_template_chip;
> gpio->gpio_chip.label = dev_name(&pdev->dev);
> + gpio->gpio_chip.ngpio = pmic->ngpio;
> + gpio->gpio_chip.offset = pmic->offset;
> gpio->gpio_chip.parent = tps->dev;
>
> return devm_gpiochip_add_data(&pdev->dev, &gpio->gpio_chip, gpio);
--
cheers,
-roger
next prev parent reply other threads:[~2025-01-04 18:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 22:54 [PATCH v2 0/3] Add TI TPS65215 PMIC GPIO Support Shree Ramamoorthy
2025-01-03 22:54 ` [PATCH v2 1/3] gpio: tps65215: Add TPS65215 to platform_device_id table Shree Ramamoorthy
2025-01-04 18:21 ` Roger Quadros
2025-01-06 17:30 ` Andrew Davis
2025-01-07 12:41 ` Roger Quadros
2025-01-03 22:54 ` [PATCH v2 2/3] gpio: tps65215: Update GPIO0_IDX macro prefix Shree Ramamoorthy
2025-01-04 18:24 ` Roger Quadros
2025-01-03 22:54 ` [PATCH v2 3/3] gpio tps65215: Add support for varying gpio/offset values Shree Ramamoorthy
2025-01-04 18:27 ` Roger Quadros [this message]
2025-01-06 21:49 ` Shree Ramamoorthy
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=a34f42fb-30e0-426b-8efe-9be0c0494fe7@kernel.org \
--to=rogerq@kernel.org \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=brgl@bgdev.pl \
--cc=christophe.jaillet@wanadoo.fr \
--cc=khilman@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=m-leonard@ti.com \
--cc=praneeth@ti.com \
--cc=s-ramamoorthy@ti.com \
--cc=tony@atomide.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