mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martyn Welch <martyn.welch@collabora.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	kernel@collabora.com,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/5] gpio: pca953x: Add support for PCAL6534 and compatible
Date: Wed, 31 Aug 2022 17:30:38 +0100	[thread overview]
Message-ID: <e89ccd1ecb675ab899dba0f08624a3dde195c970.camel@collabora.com> (raw)
In-Reply-To: <CAMRc=McbNwLRq_OBo_=xwFJJ-_8C5VfjQt75dvSVC9SqUYTpFg@mail.gmail.com>

On Wed, 2022-08-31 at 13:57 +0200, Bartosz Golaszewski wrote:
> On Mon, Aug 29, 2022 at 3:39 PM Martyn Welch
> <martyn.welch@collabora.com> wrote:
> > 
> > Add support for the NXP PCAL6534 and Diodes Inc. PI4IOE5V6534Q.
> > These
> > devices, which have identical register layouts and features, are
> > broadly a
> > 34-bit version of the PCAL6524.
> > 
> > However, whilst the registers are broadly what you'd expect for a
> > 34-bit
> > version of the PCAL6524, the spacing of the registers has been
> > compacted. This has the unfortunate effect of breaking the bit
> > shift
> > based mechanism that is employed to work out register locations
> > used by
> > the other chips supported by this driver, resulting in special
> > handling
> > needing to be introduced in pca953x_recalc_addr() and
> > pca953x_check_register().
> > 
> > Datasheet: https://www.nxp.com/docs/en/data-sheet/PCAL6534.pdf
> > Datasheet:
> > https://www.diodes.com/assets/Datasheets/PI4IOE5V6534Q.pdf
> > Signed-off-by: Martyn Welch <martyn.welch@collabora.com>
> > ---
> 
> Is this series complete? I don't have patch 1/5 in my inbox and
> neither does patchwork.
> 

I used get_maintainers to generate the recipients, it's a patch for the
binding documentation relating to the driver so didn't get sent to the
same lists:

https://lore.kernel.org/lkml/20220829133923.1114555-3-martyn.welch@collabora.com/T/

Martyn

> Bart


  reply	other threads:[~2022-08-31 16:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29 13:39 [PATCH 1/5] dt-bindings: vendor-prefixes: add Diodes Martyn Welch
2022-08-29 13:39 ` [PATCH 2/5] dt-bindings: gpio: pca95xx: add entry for pcal6534 and PI4IOE5V6534Q Martyn Welch
2022-08-30  7:50   ` Krzysztof Kozlowski
2022-08-31 13:26     ` Linus Walleij
2022-08-31 13:34       ` Krzysztof Kozlowski
2022-09-08 12:06         ` Linus Walleij
2022-08-29 13:39 ` [PATCH 3/5] gpio: pca953x: Fix pca953x_gpio_set_pull_up_down() Martyn Welch
2022-08-31 12:35   ` Linus Walleij
2022-08-31 20:54   ` Andy Shevchenko
2022-08-29 13:39 ` [PATCH 4/5] gpio: pca953x: Swap if statements to save later complexity Martyn Welch
2022-08-31 12:36   ` Linus Walleij
2022-08-31 20:55   ` Andy Shevchenko
2022-08-29 13:39 ` [PATCH 5/5] gpio: pca953x: Add support for PCAL6534 and compatible Martyn Welch
2022-08-31 11:57   ` Bartosz Golaszewski
2022-08-31 16:30     ` Martyn Welch [this message]
2022-08-31 19:44       ` Bartosz Golaszewski
2022-08-31 21:02   ` Andy Shevchenko
2022-09-01 17:18     ` Martyn Welch
2022-08-30  9:14 ` [PATCH 1/5] dt-bindings: vendor-prefixes: add Diodes Krzysztof Kozlowski

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=e89ccd1ecb675ab899dba0f08624a3dde195c970.camel@collabora.com \
    --to=martyn.welch@collabora.com \
    --cc=brgl@bgdev.pl \
    --cc=kernel@collabora.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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®