public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Richard <thomas.richard@bootlin.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Lee Jones <lee@kernel.org>, Pavel Machek <pavel@ucw.cz>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-leds@vger.kernel.org, thomas.petazzoni@bootlin.com,
	DanieleCleri@aaeon.eu, GaryWang@aaeon.com.tw
Subject: Re: [PATCH 3/5] gpiolib: add gpiochip_add_pinlist_range() function
Date: Mon, 16 Dec 2024 11:02:33 +0100	[thread overview]
Message-ID: <19311182-b5d5-44e9-96f5-ee21f2178668@bootlin.com> (raw)
In-Reply-To: <CAMRc=MfUDGaW1cBrsLzAZ6GORFFv5fAjEKXu7esO44v4XckheQ@mail.gmail.com>

On 12/16/24 10:17, Bartosz Golaszewski wrote:
> On Wed, Dec 11, 2024 at 5:27 PM Thomas Richard
> <thomas.richard@bootlin.com> wrote:
>>
>> Add gpiochip_add_pinlist_range() function to add a range for GPIO <-> pin
>> mapping, using a list of non consecutive pins.
>> Previously, it was only possible to add range of consecutive pins using
>> gpiochip_add_pin_range().
>>
>> The struct pinctrl_gpio_range has a 'pins' member which allows to set a
>> list of pins (which can be non consecutive). gpiochip_add_pinlist_range()
>> is identical to gpiochip_add_pin_range(), except it set 'pins' member
>> instead of 'pin_base' member.
>>
>> Signed-off-by: Thomas Richard <thomas.richard@bootlin.com>
>> ---
> 
> I don't have anything against this change so in any case:
> 
> Acked-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> 
> But may I suggest the name to be changed to
> gpiochip_add_pin_range_sparse() for a better indication of its
> purpose?

Hi Bartosz,

Yes for sure, I will change the name for the v2.

Regards,

Thomas


  reply	other threads:[~2024-12-16 10:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11 16:27 [PATCH 0/5] Add support for the AAEON UP board FPGA Thomas Richard
2024-12-11 16:27 ` [PATCH 1/5] mfd: Add support for " Thomas Richard
2024-12-11 16:27 ` [PATCH 2/5] leds: Add AAEON UP board LED driver Thomas Richard
2024-12-11 16:27 ` [PATCH 3/5] gpiolib: add gpiochip_add_pinlist_range() function Thomas Richard
2024-12-16  9:17   ` Bartosz Golaszewski
2024-12-16 10:02     ` Thomas Richard [this message]
2024-12-20 12:31   ` Linus Walleij
2024-12-11 16:27 ` [PATCH 4/5] pinctrl: Add pin controller driver for AAEON UP boards Thomas Richard
2024-12-20 12:22   ` Linus Walleij
2024-12-20 13:50     ` Thomas Richard
2024-12-21 23:43       ` Linus Walleij
2025-01-03 10:28         ` Thomas Richard
2025-01-13  9:46           ` Andy Shevchenko
2025-01-14 10:28             ` Thomas Richard
2025-01-16  9:12               ` Andy Shevchenko
2025-01-16 12:21                 ` Thomas Richard
2025-01-16 12:31                   ` Andy Shevchenko
2025-01-16 13:23                     ` Thomas Richard
2025-01-16 14:14                       ` Andy Shevchenko
2025-02-05 11:17                         ` Thomas Richard
2025-02-05 11:41                           ` Andy Shevchenko
2025-04-04 13:11                             ` Thomas Richard
2025-04-04 13:26                               ` Andy Shevchenko
2025-01-22 12:46                   ` Linus Walleij
2024-12-11 16:27 ` [PATCH 5/5] MAINTAINERS: Add entry for AAEON UP board FPGA drivers Thomas Richard
2024-12-13 17:09 ` (subset) [PATCH 0/5] Add support for the AAEON UP board FPGA Lee Jones

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=19311182-b5d5-44e9-96f5-ee21f2178668@bootlin.com \
    --to=thomas.richard@bootlin.com \
    --cc=DanieleCleri@aaeon.eu \
    --cc=GaryWang@aaeon.com.tw \
    --cc=brgl@bgdev.pl \
    --cc=lee@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=thomas.petazzoni@bootlin.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