From: Andreas Kemnade <andreas@kemnade.info>
To: Paul Sajna <sajattack@postmarketos.org>
Cc: Lee Jones <lee@kernel.org>, Pavel Machek <pavel@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Nikita Travkin <nikitos.tr@gmail.com>,
Alexey Min <alexeymin@minlexx.ru>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH v2 4/7] leds: aw2013: use dev_err_probe
Date: Wed, 7 Oct 2026 09:36:48 +0200 [thread overview]
Message-ID: <20261007093649.29a2dd6d@kemnade.info> (raw)
In-Reply-To: <20261005-aw2013-aw20xx-rename-v2-4-108ecbdf2775@postmarketos.org>
On Mon, 05 Oct 2026 20:46:05 -0700
Paul Sajna <sajattack@postmarketos.org> wrote:
> Failure to use dev_err_probe() for regulator requests violates
> LED subsystem guidelines.
>
This cleanup is good.
But your comment sounds like there are documented guidelines and not just common
practice, so please add a link if it is not in an usual place which it is not:
~/linux/Documentation/leds$ grep -R probe *
leds-blinkm.rst: $ modprobe ledtrig-heartbeat
well-known-leds.txt:wants to use particular feature, you should probe for good name, first,
~/linux/Documentation/leds$ grep -R http *
leds-lm3556.rst:* Datasheet: http://www.national.com/ds/LM/LM3556.pdf
leds-lp3944.rst: http://www.national.com/pf/LP/LP3944.html
leds-lp5521.rst:* Datasheet: http://www.national.com/pf/LP/LP5521.html
leds-lp5523.rst:* Datasheet: http://www.national.com/pf/LP/LP5523.html
leds-lp5812.rst:* Datasheet: https://www.ti.com/product/LP5812#tech-docs
No links to additional documentation either.
If no such documentation exist, then do not talk about it. Just
say something like "to simplify und unify error reporting" as reason.
Regards,
Andreas
> The original driver didn't use it, but it's worth cleaning up
> while I'm here.
>
> Signed-off-by: Paul Sajna <sajattack@postmarketos.org>
> ---
> drivers/leds/leds-aw2013.c | 28 +++++++++++++---------------
> 1 file changed, 13 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/leds/leds-aw2013.c b/drivers/leds/leds-aw2013.c
> index 340eefdda04f..705de95c6eac 100644
> --- a/drivers/leds/leds-aw2013.c
> +++ b/drivers/leds/leds-aw2013.c
> @@ -448,9 +448,8 @@ static int aw20xx_probe(struct i2c_client *client)
>
> chip->regmap = devm_regmap_init_i2c(client, chip->cdef->regmap_cfg);
> if (IS_ERR(chip->regmap)) {
> - ret = PTR_ERR(chip->regmap);
> - dev_err(&client->dev, "Failed to allocate register map: %d\n",
> - ret);
> + ret = dev_err_probe(&client->dev, PTR_ERR(chip->regmap),
> + "Failed to allocate register map\n");
> goto error;
> }
>
> @@ -460,30 +459,30 @@ static int aw20xx_probe(struct i2c_client *client)
> ARRAY_SIZE(chip->regulators),
> chip->regulators);
> if (ret < 0) {
> - if (ret != -EPROBE_DEFER)
> - dev_err(&client->dev,
> - "Failed to request regulators: %d\n", ret);
> + ret = dev_err_probe(&client->dev, ret,
> + "Failed to request regulators\n");
> goto error;
> }
>
> ret = regulator_bulk_enable(ARRAY_SIZE(chip->regulators),
> chip->regulators);
> if (ret) {
> - dev_err(&client->dev,
> - "Failed to enable regulators: %d\n", ret);
> + ret = dev_err_probe(&client->dev, ret,
> + "Failed to enable regulators\n");
> goto error;
> }
>
> ret = regmap_read(chip->regmap, AW20XX_RSTR, &chipid);
> if (ret) {
> - dev_err(&client->dev, "Failed to read chip ID: %d\n",
> - ret);
> + ret = dev_err_probe(&client->dev, ret,
> + "Failed to read chip ID\n");
> goto error_reg;
> }
> if (chipid != chip->cdef->chip_id) {
> - dev_err(&client->dev, "Chip reported wrong ID: %x\n",
> - chipid);
> ret = -ENODEV;
> + ret = dev_err_probe(&client->dev, ret,
> + "Chip reported wrong ID: %x\n",
> + chipid);
> goto error_reg;
> }
>
> @@ -498,13 +497,12 @@ static int aw20xx_probe(struct i2c_client *client)
> ret = regulator_bulk_disable(ARRAY_SIZE(chip->regulators),
> chip->regulators);
> if (ret) {
> - dev_err(&client->dev,
> - "Failed to disable regulators: %d\n", ret);
> + ret = dev_err_probe(&client->dev, ret,
> + "Failed to disable regulators\n");
> goto error;
> }
>
> mutex_unlock(&chip->mutex);
> -
> return 0;
>
> error_reg:
>
next prev parent reply other threads:[~2026-10-07 7:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 3:46 [PATCH v2 0/7] leds: aw2013: Add AW2027 support Paul Sajna
2026-10-06 3:46 ` [PATCH v2 1/7] dt-bindings: leds: aw2013: Add awinic,aw2027 compatible Paul Sajna
2026-10-07 10:30 ` Conor Dooley
2026-10-06 3:46 ` [PATCH v2 2/7] leds: aw2013: Rename internal APIs from aw2013 to aw20xx Paul Sajna
2026-10-06 10:45 ` Griffin Kroah-Hartman
2026-10-06 18:54 ` Paul Sajna
2026-10-06 3:46 ` [PATCH v2 3/7] leds: aw2013: Add AW2027 support Paul Sajna
2026-10-06 3:46 ` [PATCH v2 4/7] leds: aw2013: use dev_err_probe Paul Sajna
2026-10-06 19:52 ` Griffin Kroah-Hartman
2026-10-07 7:36 ` Andreas Kemnade [this message]
2026-10-06 3:46 ` [PATCH v2 5/7] leds: aw2013: Move assignment of chip->num_leds Paul Sajna
2026-10-06 3:46 ` [PATCH v2 6/7] leds: aw2013: Prevent writes to unpowered chip Paul Sajna
2026-10-06 3:46 ` [PATCH v2 7/7] leds: aw2013: move reset from probe_dt to chip_init Paul Sajna
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=20261007093649.29a2dd6d@kemnade.info \
--to=andreas@kemnade.info \
--cc=alexeymin@minlexx.ru \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=nikitos.tr@gmail.com \
--cc=pavel@kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sajattack@postmarketos.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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®