From: "Nuno Sá" <noname.nuno@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>, nuno.sa@analog.com
Cc: linux-hwmon@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
Jonathan Corbet <corbet@lwn.net>,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [PATCH v2 3/3] gpio: gpio-ltc4283: Add support for the LTC4283 Swap Controller
Date: Tue, 09 Sep 2025 11:25:32 +0100 [thread overview]
Message-ID: <a7bb4d2057af52f23a73f439190261f8253b9d5c.camel@gmail.com> (raw)
In-Reply-To: <CACRpkdbgcCjZbZ2HtrNO7vK1HXzrwxkrNFCzqGguq=ckKg3cFQ@mail.gmail.com>
On Thu, 2025-09-04 at 21:57 +0200, Linus Walleij wrote:
> Hi Nuno,
>
> thanks for your patch!
>
> On Wed, Sep 3, 2025 at 12:04 PM Nuno Sá via B4 Relay
> <devnull+nuno.sa.analog.com@kernel.org> wrote:
>
> > From: Nuno Sá <nuno.sa@analog.com>
> >
> > The LTC4283 device has up to 8 pins that can be configured as GPIOs.
> >
> > Note that PGIO pins are not set as GPIOs by default so if they are
> > configured to be used as GPIOs we need to make sure to initialize them
> > to a sane default. They are set as inputs by default.
> >
> > Signed-off-by: Nuno Sá <nuno.sa@analog.com>
>
> (...)
>
> > +config GPIO_LTC4283
> > + tristate "Analog Devices LTC4283 GPIO support"
> > + depends on SENSORS_LTC4283
>
> Could that be
> depends on REGMAP && (SENSOR_LTC4283 || COMPILE_TEST)
> ?
>
> Or does something blow up if you do that? (I guess it also needs
> AUXBUS but more on that below)
>
(forgot to reply to this)
Hmm SENSOR_LTC4283 already depends on that and REGMAP (and selects AUXBUS) so
isn't enough to depend on SENSOR_LTC4283? Or is the above so that we can do
COMPILE_TEST?
- Nuno Sá
> should it also be
>
> default SENSOR_LTC4283
>
> Sof if that is compiled in (=y) or module (=m) then this becomes
> the same by default?
>
> > + help
> > + If you say yes here you want the GPIO function available in Analog
> > + Devices LTC4283 Negative Voltage Hot Swap Controller.
> > +
> > + This driver can also be built as a module. If so, the module will
> > + be called gpio-ltc4283.
> > +
> > config GPIO_MB86S7X
>
> This is placed among the memory-mapped drivers, but:
>
> > +#include <linux/auxiliary_bus.h>
> (...)
> > +static struct auxiliary_driver ltc4283_gpio_driver = {
> > + .probe = ltc4283_gpio_probe,
> > + .id_table = ltc4283_aux_id_table,
> > +};
> > +module_auxiliary_driver(ltc4283_gpio_driver);
>
> Create a new submenu for auxiliary bus drivers and add it
> there. We already have a submenu for MFD so why not?
>
> menu "AUXBUS GPIO expanders"
> depends on AUXILIARY_BUS
> ...
>
> Have you looked into using GPIO_REGMAP?
> I guess some specials are used here so maybe it is
> not possible.
>
> Yours,
> Linus Walleij
prev parent reply other threads:[~2025-09-09 10:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 10:04 [PATCH v2 0/3] hwmon: Add support for the LTC4283 Hot Swap Controller Nuno Sá via B4 Relay
2025-09-03 10:04 ` [PATCH v2 1/3] dt-binbings: hwmon: Document the LTC4283 " Nuno Sá via B4 Relay
2025-09-03 21:48 ` Rob Herring
2025-09-06 0:27 ` Guenter Roeck
2025-09-03 10:05 ` [PATCH v2 2/3] hwmon: ltc4283: Add support for " Nuno Sá via B4 Relay
2025-09-04 21:30 ` kernel test robot
2025-09-06 1:24 ` Guenter Roeck
2025-09-12 14:00 ` Nuno Sá
2025-09-13 11:02 ` Guenter Roeck
2025-09-03 10:05 ` [PATCH v2 3/3] gpio: gpio-ltc4283: " Nuno Sá via B4 Relay
2025-09-03 11:26 ` Andy Shevchenko
2025-09-09 10:27 ` Nuno Sá
2025-09-09 11:32 ` Andy Shevchenko
2025-09-04 2:42 ` Randy Dunlap
2025-09-04 19:57 ` Linus Walleij
2025-09-09 10:22 ` Nuno Sá
2025-09-09 10:25 ` Nuno Sá [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=a7bb4d2057af52f23a73f439190261f8253b9d5c.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=nuno.sa@analog.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).