From: Lee Jones <lee@kernel.org>
To: Alexey Charkov <alchark@flipper.net>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Chris Morgan <macromorgan@hotmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Sebastian Reichel <sre@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Sebastian Reichel <sebastian.reichel@collabora.com>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v5 09/11] mfd: bq257xx: Add BQ25792 support
Date: Tue, 31 Mar 2026 14:17:06 +0100 [thread overview]
Message-ID: <20260331131706.GH3795166@google.com> (raw)
In-Reply-To: <CAKTNdwE4omfEkd6FNdj=hZUY2ZwLprXzUu1L4juFhWCxbWEjpQ@mail.gmail.com>
On Tue, 31 Mar 2026, Alexey Charkov wrote:
> On Tue, Mar 31, 2026 at 2:27 PM Lee Jones <lee@kernel.org> wrote:
> >
> > On Tue, 24 Mar 2026, Alexey Charkov wrote:
> >
> > > Add register definitions and a new 'type' enum to be passed via MFD
> > > private data to support the BQ25792, which is a newer variant of the
> > > BQ257xx family.
> > >
> > > BQ25792 shares similar logic of operation with the already supported
> > > BQ25703A but has a completely different register map and different
> > > electrical constraints.
> > >
> > > Tested-by: Chris Morgan <macromorgan@hotmail.com>
> > > Signed-off-by: Alexey Charkov <alchark@flipper.net>
> > > ---
> > > drivers/mfd/bq257xx.c | 54 +++++-
> > > include/linux/mfd/bq257xx.h | 412 ++++++++++++++++++++++++++++++++++++++++++++
> > > 2 files changed, 463 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/drivers/mfd/bq257xx.c b/drivers/mfd/bq257xx.c
> > > index e9d49dac0a16..31654925afa5 100644
> > > --- a/drivers/mfd/bq257xx.c
> > > +++ b/drivers/mfd/bq257xx.c
> > > @@ -39,6 +39,39 @@ static const struct regmap_config bq25703_regmap_config = {
> > > .val_format_endian = REGMAP_ENDIAN_LITTLE,
> > > };
> > >
> > > +static const struct regmap_range bq25792_writeable_reg_ranges[] = {
> > > + regmap_reg_range(BQ25792_REG00_MIN_SYS_VOLTAGE,
> > > + BQ25792_REG18_NTC_CONTROL_1),
> > > + regmap_reg_range(BQ25792_REG28_CHARGER_MASK_0,
> > > + BQ25792_REG30_ADC_FUNCTION_DISABLE_1),
> > > +};
> > > +
> > > +static const struct regmap_access_table bq25792_writeable_regs = {
> > > + .yes_ranges = bq25792_writeable_reg_ranges,
> > > + .n_yes_ranges = ARRAY_SIZE(bq25792_writeable_reg_ranges),
> > > +};
> > > +
> > > +static const struct regmap_range bq25792_volatile_reg_ranges[] = {
> > > + regmap_reg_range(BQ25792_REG19_ICO_CURRENT_LIMIT,
> > > + BQ25792_REG27_FAULT_FLAG_1),
> > > + regmap_reg_range(BQ25792_REG31_IBUS_ADC,
> > > + BQ25792_REG47_DPDM_DRIVER),
> > > +};
> > > +
> > > +static const struct regmap_access_table bq25792_volatile_regs = {
> > > + .yes_ranges = bq25792_volatile_reg_ranges,
> > > + .n_yes_ranges = ARRAY_SIZE(bq25792_volatile_reg_ranges),
> > > +};
> > > +
> > > +static const struct regmap_config bq25792_regmap_config = {
> > > + .reg_bits = 8,
> > > + .val_bits = 8,
> > > + .max_register = BQ25792_REG48_PART_INFORMATION,
> > > + .cache_type = REGCACHE_MAPLE,
> > > + .wr_table = &bq25792_writeable_regs,
> > > + .volatile_table = &bq25792_volatile_regs,
> > > +};
> > > +
> > > static const struct mfd_cell cells[] = {
> > > MFD_CELL_NAME("bq257xx-regulator"),
> > > MFD_CELL_NAME("bq257xx-charger"),
> > > @@ -46,6 +79,7 @@ static const struct mfd_cell cells[] = {
> > >
> > > static int bq257xx_probe(struct i2c_client *client)
> > > {
> > > + const struct regmap_config *rcfg;
> > > struct bq257xx_device *ddata;
> > > int ret;
> > >
> > > @@ -53,9 +87,21 @@ static int bq257xx_probe(struct i2c_client *client)
> > > if (!ddata)
> > > return -ENOMEM;
> > >
> > > + ddata->type = (uintptr_t)i2c_get_match_data(client);
> > > ddata->client = client;
> > >
> > > - ddata->regmap = devm_regmap_init_i2c(client, &bq25703_regmap_config);
> > > + switch (ddata->type) {
> > > + case BQ25703A:
> > > + rcfg = &bq25703_regmap_config;
> > > + break;
> > > + case BQ25792:
> > > + rcfg = &bq25792_regmap_config;
> > > + break;
> > > + default:
> > > + return dev_err_probe(&client->dev, -EINVAL, "Unsupported device type\n");
> >
> > Nit: Shouldn't we be returning '-ENODEV' here for an unsupported device?
>
> Hi Lee,
>
> Indeed, I've had a quick look and other drivers seem to return -ENODEV
> in similar situations. Shall I respin a new version with that change?
Yes please. And add a change log so I am reminded of it.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2026-03-31 13:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 11:38 [PATCH v5 00/11] Add support for the TI BQ25792 battery charger Alexey Charkov
2026-03-24 11:38 ` [PATCH v5 01/11] dt-bindings: mfd: ti,bq25703a: Expand to include BQ25792 Alexey Charkov
2026-03-24 11:38 ` [PATCH v5 02/11] regulator: bq257xx: Remove reference to the parent MFD's dev Alexey Charkov
2026-03-24 11:38 ` [PATCH v5 03/11] regulator: bq257xx: Drop the regulator_dev from the driver data Alexey Charkov
2026-03-24 11:38 ` [PATCH v5 04/11] regulator: bq257xx: Make OTG enable GPIO really optional Alexey Charkov
2026-03-24 11:38 ` [PATCH v5 05/11] power: supply: bq257xx: Fix VSYSMIN clamping logic Alexey Charkov
2026-03-24 11:38 ` [PATCH v5 06/11] power: supply: bq257xx: Make the default current limit a per-chip attribute Alexey Charkov
2026-03-24 11:38 ` [PATCH v5 07/11] power: supply: bq257xx: Consistently use indirect get/set helpers Alexey Charkov
2026-03-24 11:38 ` [PATCH v5 08/11] power: supply: bq257xx: Add fields for 'charging' and 'overvoltage' states Alexey Charkov
2026-03-24 11:38 ` [PATCH v5 09/11] mfd: bq257xx: Add BQ25792 support Alexey Charkov
2026-03-31 10:27 ` Lee Jones
2026-03-31 12:37 ` Alexey Charkov
2026-03-31 13:17 ` Lee Jones [this message]
2026-03-24 11:38 ` [PATCH v5 10/11] regulator: bq257xx: Add support for BQ25792 Alexey Charkov
2026-03-24 11:38 ` [PATCH v5 11/11] power: supply: " Alexey Charkov
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=20260331131706.GH3795166@google.com \
--to=lee@kernel.org \
--cc=alchark@flipper.net \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=macromorgan@hotmail.com \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=sre@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