From: Lee Jones <lee@kernel.org>
To: Paul Sajna <sajattack@postmarketos.org>
Cc: 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>,
Nikita Travkin <nikita@trvn.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 v3 2/6] leds: aw2013: Add AW2027 support
Date: Tue, 20 Oct 2026 11:16:09 +0100 [thread overview]
Message-ID: <179198402838.839288.17911568760182808689@kernel.org> (raw)
In-Reply-To: <20261012-aw2013-aw20xx-rename-v3-2-cab1fdd050b6@postmarketos.org>
Please review, explain or fix the Sashiko review(s).
If this is a set, this request includes the other patches too.
--- checkpatch.pl (2 issues) ---
Line 19: WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
Line 262: WARNING: DT compatible string "awinic,aw2027" appears un-documented -- check ./Documentation/devicetree/bindings/
----------------------------------
On Mon, 12 Oct 2026, Paul Sajna wrote:
> The AW2027 is basically the same as the AW2013.
>
> It differs in:
> - the max current (30mA rather than 15)
> - the number of current levels for colour-mixing (16 rather than 4)
> - the supply voltage max
> - the charge indicator (unsupported by our driver at this time)
>
> The max current register (imax) also moves from LCFG to GCR2, and the
> selectable current levels for colour-mixing (LCFG_CUR) take their place.
>
> The current driver implementation provided here sets the global imax to
> it's maximum, and scales each led to the closest value using the local
> imax. It's the best result achievable short of adding custom sysfs
> entries and mucking up the linux interfaces.
>
> Comparison of all AW20XX chips https://www.awinic.com/en/productCompareList?id=47&ids=1022,74,96,75,72,71,928,927,73,76,578
> AW2027 datasheet: https://doc.awinic.com/doc/202507/77b87097-27bf-48cd-af9b-9b615064c1e1.pdf
> Vendor driver: https://www.awinic.com/en/driver/AW2027DNR/454
>
> Signed-off-by: Paul Sajna <sajattack@postmarketos.org>
> ---
> drivers/leds/leds-aw2013.c | 137 ++++++++++++++++++++++++++++++++++++++-------
> 1 file changed, 117 insertions(+), 20 deletions(-)
>
> diff --git a/drivers/leds/leds-aw2013.c b/drivers/leds/leds-aw2013.c
> index 216755d6010f..4da33a86af16 100644
> --- a/drivers/leds/leds-aw2013.c
> +++ b/drivers/leds/leds-aw2013.c
> @@ -1,5 +1,5 @@
> // SPDX-License-Identifier: GPL-2.0+
> -// Driver for Awinic AW2013 3-channel LED driver
> +// Driver for Awinic AW2013/AW2027 3-channel LED drivers
>
> #include <linux/i2c.h>
> #include <linux/leds.h>
> @@ -20,13 +20,15 @@
> #define AW2013_GCR 0x01
> #define AW2013_GCR_ENABLE BIT(0)
>
> +#define AW20XX_GCR2 0x04
> +#define AW2013_IMAX_MASK (BIT(0) | BIT(1)) // Should be 0-3
> +
> /* LED channel enable register */
> #define AW2013_LCTR 0x30
> #define AW2013_LCTR_LE(x) BIT((x))
>
> /* LED channel control registers */
> #define AW2013_LCFG(x) (0x31 + (x))
> -#define AW2013_LCFG_IMAX_MASK (BIT(0) | BIT(1)) // Should be 0-3
> #define AW2013_LCFG_MD BIT(4)
> #define AW2013_LCFG_FI BIT(5)
> #define AW2013_LCFG_FO BIT(6)
> @@ -50,6 +52,13 @@
> #define AW2013_REG_MAX 0x77
>
> #define AW2013_TIME_STEP 130 /* ms */
> +#define AW2027_RSTR_CHIP_ID 0x09
> +#define AW2027_REG_MAX 0x7F /* copied from vendor driver, but only up to 0x3F is documented */
> +
> +#define AW2027_IMAX_15MA (0)
> +#define AW2027_IMAX_30MA (1)
> +#define AW2027_IMAX_5MA (2)
> +#define AW2027_IMAX_10MA (3)
Why the parentheses around simple integer literals?
> struct aw2013;
>
> @@ -60,16 +69,70 @@ struct aw2013_led {
> unsigned int imax;
> };
>
> +struct aw2013_chipdef {
> + u8 chip_id;
> + const struct regmap_config *regmap_cfg;
> + u32 default_imax;
> + bool gcr2_imax;
> + unsigned int current_levels;
> + unsigned int current_max;
> +};
> +
> struct aw2013 {
> struct mutex mutex; /* held when writing to registers */
> struct regulator_bulk_data regulators[2];
> struct i2c_client *client;
> struct aw2013_led leds[AW2013_MAX_LEDS];
> struct regmap *regmap;
> + const struct aw2013_chipdef *cdef;
> int num_leds;
> bool enabled;
> };
>
> +static const struct regmap_config aw2013_regmap_config = {
> + .reg_bits = 8,
> + .val_bits = 8,
> + .max_register = AW2013_REG_MAX,
> +};
> +
> +static const struct regmap_config aw2027_regmap_config = {
> + .reg_bits = 8,
> + .val_bits = 8,
> + .max_register = AW2027_REG_MAX,
> +};
> +
> +static const struct aw2013_chipdef aw2013_chipdef = {
> + .chip_id = AW2013_RSTR_CHIP_ID,
> + .regmap_cfg = &aw2013_regmap_config,
> + .default_imax = 1, // 5mA
> + .gcr2_imax = false,
> + .current_levels = 4,
> + .current_max = 15000,
> +};
> +
> +static const struct aw2013_chipdef aw2027_chipdef = {
> + .chip_id = AW2027_RSTR_CHIP_ID,
> + .regmap_cfg = &aw2027_regmap_config,
> + .default_imax = 3, // 6mA
> + .gcr2_imax = true,
> + .current_levels = 16,
> + .current_max = 30000,
> +};
> +
> +/**
> + * aw2013_microamp_to_imax() - Finds the closest current step to the given microamp
> + * @microamp: Desired current in microamps
> + * @cdef: Chip definition
> + *
> + * Return: The closest current-step to the given microamp
> + */
> +static inline u32 aw2013_microamp_to_imax(u32 microamp, const struct aw2013_chipdef *cdef)
> +{
> + return min_t(u32, (microamp * (cdef->current_levels - 1))
> + / cdef->current_max,
> + cdef->current_levels - 1);
> +}
This is hard to read, I think we can do better.
Also, does it need to be a separate helper function when it only has a
single call site?
> +
> static int aw2013_chip_init(struct aw2013 *chip)
> {
> int i, ret;
> @@ -81,17 +144,50 @@ static int aw2013_chip_init(struct aw2013 *chip)
> return ret;
> }
>
> - for (i = 0; i < chip->num_leds; i++) {
> + if (chip->cdef->gcr2_imax) {
> + /*
> + * AW2027 supports 4-step global imax, and also a 16-step control for limiting
> + * individual current per LED. This doesn't map to the single value the
> + * devicetree provides super well, so set global imax to maximum, and
> + * local imax to whatever gets us closest to the value in the devicetree.
> + */
> ret = regmap_update_bits(chip->regmap,
> - AW2013_LCFG(chip->leds[i].num),
> - AW2013_LCFG_IMAX_MASK,
> - chip->leds[i].imax);
> + AW20XX_GCR2,
> + AW2013_IMAX_MASK,
> + AW2027_IMAX_30MA);
> if (ret) {
> dev_err(&chip->client->dev,
> - "Failed to set maximum current for led %d: %d\n",
> - chip->leds[i].num, ret);
> + "Failed to set maximum global current: %d\n",
> + ret);
> return ret;
> }
> +
> + for (i = 0; i < chip->num_leds; i++) {
> + ret = regmap_update_bits(chip->regmap,
> + AW2013_LCFG(chip->leds[i].num),
> + AW2013_IMAX_MASK,
> + chip->leds[i].imax);
> + if (ret) {
> + dev_err(&chip->client->dev,
> + "Failed to set maximum current for led %d: %d\n",
> + chip->leds[i].num, ret);
> + return ret;
> + }
> + }
> + } else {
> + /* AW2013 only supports 4-step individual current per LED */
> + for (i = 0; i < chip->num_leds; i++) {
> + ret = regmap_update_bits(chip->regmap,
> + AW2013_LCFG(chip->leds[i].num),
> + AW2013_IMAX_MASK,
> + chip->leds[i].imax);
> + if (ret) {
> + dev_err(&chip->client->dev,
> + "Failed to set maximum current for led %d: %d\n",
> + chip->leds[i].num, ret);
> + return ret;
> + }
> + }
> }
Consider using functions instead of massive seconds of indented code.
Also, the for() loops are identical and are the last pieces of both
branches, so why are they duplicated?
> return ret;
> @@ -292,9 +388,9 @@ static int aw2013_probe_dt(struct aw2013 *chip)
> init_data.fwnode = of_fwnode_handle(child);
>
> if (!of_property_read_u32(child, "led-max-microamp", &imax)) {
> - led->imax = min_t(u32, imax / 5000, 3);
> + led->imax = aw2013_microamp_to_imax(imax, chip->cdef);
> } else {
> - led->imax = 1; // 5mA
> + led->imax = chip->cdef->default_imax;
> dev_info(&chip->client->dev,
> "DT property led-max-microamp is missing\n");
> }
> @@ -323,18 +419,18 @@ static void aw2013_chip_disable_action(void *data)
> aw2013_chip_disable(data);
> }
>
> -static const struct regmap_config aw2013_regmap_config = {
> - .reg_bits = 8,
> - .val_bits = 8,
> - .max_register = AW2013_REG_MAX,
> -};
>
> static int aw2013_probe(struct i2c_client *client)
> {
> struct aw2013 *chip;
> + const struct aw2013_chipdef *cdef;
> int ret;
> unsigned int chipid;
>
> + cdef = device_get_match_data(&client->dev);
> + if (!cdef)
> + return -ENODEV;
> +
> chip = devm_kzalloc(&client->dev, sizeof(*chip), GFP_KERNEL);
> if (!chip)
> return -ENOMEM;
> @@ -346,9 +442,10 @@ static int aw2013_probe(struct i2c_client *client)
> mutex_lock(&chip->mutex);
>
> chip->client = client;
> + chip->cdef = cdef;
> i2c_set_clientdata(client, chip);
>
> - chip->regmap = devm_regmap_init_i2c(client, &aw2013_regmap_config);
> + 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",
> @@ -382,8 +479,7 @@ static int aw2013_probe(struct i2c_client *client)
> ret);
> goto error_reg;
> }
> -
> - if (chipid != AW2013_RSTR_CHIP_ID) {
> + if (chipid != chip->cdef->chip_id) {
> dev_err(&client->dev, "Chip reported wrong ID: %x\n",
> chipid);
> ret = -ENODEV;
> @@ -420,7 +516,8 @@ static int aw2013_probe(struct i2c_client *client)
> }
>
> static const struct of_device_id aw2013_match_table[] = {
> - { .compatible = "awinic,aw2013", },
> + { .compatible = "awinic,aw2013", .data = &aw2013_chipdef },
> + { .compatible = "awinic,aw2027", .data = &aw2027_chipdef },
> { /* sentinel */ },
> };
>
> @@ -437,5 +534,5 @@ static struct i2c_driver aw2013_driver = {
> module_i2c_driver(aw2013_driver);
>
> MODULE_AUTHOR("Nikita Travkin <nikitos.tr@gmail.com>");
> -MODULE_DESCRIPTION("AW2013 LED driver");
> +MODULE_DESCRIPTION("AW2013/AW2027 LED driver");
> MODULE_LICENSE("GPL v2");
>
> --
> 2.55.0
>
>
--
Lee Jones
next prev parent reply other threads:[~2026-10-20 10:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 5:39 [PATCH v3 0/6] " Paul Sajna
2026-10-13 5:39 ` [PATCH v3 1/6] dt-bindings: leds: aw2013: Add awinic,aw2027 compatible Paul Sajna
2026-10-13 6:31 ` Krzysztof Kozlowski
2026-10-13 5:39 ` [PATCH v3 2/6] leds: aw2013: Add AW2027 support Paul Sajna
2026-10-20 10:16 ` Lee Jones [this message]
2026-10-13 5:39 ` [PATCH v3 3/6] leds: aw2013: Use dev_err_probe Paul Sajna
2026-10-13 5:39 ` [PATCH v3 4/6] leds: aw2013: Move assignment of chip->num_leds Paul Sajna
2026-10-13 5:39 ` [PATCH v3 5/6] leds: aw2013: Prevent writes to unpowered chip Paul Sajna
2026-10-13 5:40 ` [PATCH v3 6/6] leds: aw2013: Move reset register write 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=179198402838.839288.17911568760182808689@kernel.org \
--to=lee@kernel.org \
--cc=alexeymin@minlexx.ru \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=nikita@trvn.ru \
--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®