From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Radu Rendec <radu.rendec@gmail.com>
Cc: linux-gpio@vger.kernel.org, Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v2 0/3] gpio: pcf857x: Implement get_multiple/set_multiple methods
Date: Wed, 11 Jan 2023 10:58:08 +0100 [thread overview]
Message-ID: <CAMRc=Md7Y6yKerX-3JJ4YGrGp5w5XRqS66s14aCL4h2AS4YPLQ@mail.gmail.com> (raw)
In-Reply-To: <20230106160419.1020733-1-radu.rendec@gmail.com>
On Fri, Jan 6, 2023 at 5:05 PM Radu Rendec <radu.rendec@gmail.com> wrote:
>
> The first two patches are just cosmetic changes. The actual changes are
> in the third patch. They are all bundled together in a patch series just
> because the third patch doesn't apply cleanly without the other two.
>
> Change description from the third patch:
>
> This change allows the GPIO core to read/change multiple pins in a
> single driver call and subsequent I2C transfer. It helps a lot with
> PCF857x devices, since their I2C protocol always reads/changes all
> existing pins anyway. Therefore, when the GPIO client code does a bulk
> operation on multiple pins, the driver makes a single I2C transfer.
>
> Radu Rendec (3):
> gpio: pcf857x: Replace 'unsigned' with 'unsigned int'
> gpio: pcf857x: Fix indentation of variable declarations
> gpio: pcf857x: Implement get_multiple/set_multiple methods
>
> drivers/gpio/gpio-pcf857x.c | 79 +++++++++++++++++++++++++------------
> 1 file changed, 54 insertions(+), 25 deletions(-)
>
> --
> 2.39.0
>
Applied, thanks!
Bart
prev parent reply other threads:[~2023-01-11 10:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 16:04 [PATCH v2 0/3] gpio: pcf857x: Implement get_multiple/set_multiple methods Radu Rendec
2023-01-06 16:04 ` [PATCH v2 1/3] gpio: pcf857x: Replace 'unsigned' with 'unsigned int' Radu Rendec
2023-01-06 16:04 ` [PATCH v2 2/3] gpio: pcf857x: Fix indentation of variable declarations Radu Rendec
2023-01-06 16:04 ` [PATCH v2 3/3] gpio: pcf857x: Implement get_multiple/set_multiple methods Radu Rendec
2023-01-11 9:58 ` Bartosz Golaszewski [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='CAMRc=Md7Y6yKerX-3JJ4YGrGp5w5XRqS66s14aCL4h2AS4YPLQ@mail.gmail.com' \
--to=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=radu.rendec@gmail.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).