From: Lee Jones <lee@kernel.org>
To: Dmitry Rokosov <ddrokosov@salutedevices.com>
Cc: pavel@ucw.cz, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
andy.shevchenko@gmail.com, kernel@sberdevices.ru,
rockosov@gmail.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
George Stark <gnstark@salutedevices.com>
Subject: Re: [PATCH v4 04/11] leds: aw200xx: calculate dts property display_rows in the driver
Date: Thu, 23 Nov 2023 16:32:52 +0000 [thread overview]
Message-ID: <20231123163252.GF1354538@google.com> (raw)
In-Reply-To: <20231121202835.28152-5-ddrokosov@salutedevices.com>
On Tue, 21 Nov 2023, Dmitry Rokosov wrote:
> From: George Stark <gnstark@salutedevices.com>
>
> Get rid of device tree property "awinic,display-rows". The property
> value actually means number of current switches and depends on how leds
Nit: LEDs
> are connected to the device. It should be calculated manually by max
> used led number. In the same way it is computed automatically now.
As above - I won't mention this again.
> Max used led is taken from led definition subnodes.
>
> Signed-off-by: George Stark <gnstark@salutedevices.com>
> Signed-off-by: Dmitry Rokosov <ddrokosov@salutedevices.com>
> ---
> drivers/leds/leds-aw200xx.c | 39 +++++++++++++++++++++++++------------
> 1 file changed, 27 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/leds/leds-aw200xx.c b/drivers/leds/leds-aw200xx.c
> index 7762b3a132ac..4bce5e7381c0 100644
> --- a/drivers/leds/leds-aw200xx.c
> +++ b/drivers/leds/leds-aw200xx.c
> @@ -379,6 +379,30 @@ static void aw200xx_disable(const struct aw200xx *const chip)
> return gpiod_set_value_cansleep(chip->hwen, 0);
> }
>
> +static bool aw200xx_probe_get_display_rows(struct device *dev, struct aw200xx *chip)
> +{
> + struct fwnode_handle *child;
> + u32 max_source = 0;
> +
> + device_for_each_child_node(dev, child) {
> + u32 source;
> + int ret;
> +
> + ret = fwnode_property_read_u32(child, "reg", &source);
> + if (ret || source >= chip->cdef->channels)
Shouldn't the second clause fail instantly?
> + continue;
> +
> + max_source = max(max_source, source);
> + }
> +
> + if (!max_source)
Since max_source is an integer, please use an '== 0' comparison.
> + return false;
> +
> + chip->display_rows = max_source / chip->cdef->display_size_columns + 1;
> +
> + return true;
> +}
> +
> static int aw200xx_probe_fw(struct device *dev, struct aw200xx *chip)
> {
> struct fwnode_handle *child;
> @@ -386,18 +410,9 @@ static int aw200xx_probe_fw(struct device *dev, struct aw200xx *chip)
> int ret;
> int i;
>
> - ret = device_property_read_u32(dev, "awinic,display-rows",
> - &chip->display_rows);
> - if (ret)
> - return dev_err_probe(dev, ret,
> - "Failed to read 'display-rows' property\n");
> -
> - if (!chip->display_rows ||
> - chip->display_rows > chip->cdef->display_size_rows_max) {
> - return dev_err_probe(dev, ret,
> - "Invalid leds display size %u\n",
> - chip->display_rows);
> - }
> + if (!aw200xx_probe_get_display_rows(dev, chip))
Function calls in side if() statements in general is rough.
Please break it out and use 'ret' as we usually do.
> + return dev_err_probe(dev, -EINVAL,
Make this the return value from aw200xx_probe_get_display_rows() and use
'ret' instead.
> + "No valid led definitions found\n");
>
> current_max = aw200xx_imax_from_global(chip, AW200XX_IMAX_MAX_uA);
> current_min = aw200xx_imax_from_global(chip, AW200XX_IMAX_MIN_uA);
> --
> 2.36.0
>
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-11-23 16:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 20:28 [PATCH v4 00/11] leds: aw200xx: several driver updates Dmitry Rokosov
2023-11-21 20:28 ` [PATCH v4 01/11] leds: aw200xx: fix write to DIM parameter Dmitry Rokosov
2023-11-21 20:28 ` [PATCH v4 02/11] leds: aw200xx: support HWEN hardware control Dmitry Rokosov
2023-11-23 15:57 ` Lee Jones
2023-11-21 20:28 ` [PATCH v4 03/11] dt-bindings: leds: aw200xx: introduce optional enable-gpios property Dmitry Rokosov
2023-11-21 20:28 ` [PATCH v4 04/11] leds: aw200xx: calculate dts property display_rows in the driver Dmitry Rokosov
2023-11-23 16:32 ` Lee Jones [this message]
2023-11-24 9:41 ` Dmitry Rokosov
2023-11-27 8:57 ` Lee Jones
2023-11-27 11:41 ` Dmitry Rokosov
2023-11-21 20:28 ` [PATCH v4 05/11] dt-bindings: leds: aw200xx: remove property "awinic,display-rows" Dmitry Rokosov
2023-11-21 20:28 ` [PATCH v4 06/11] leds: aw200xx: add delay after software reset Dmitry Rokosov
2023-11-23 16:38 ` Lee Jones
2023-11-24 9:37 ` Dmitry Rokosov
2023-11-27 9:14 ` Lee Jones
2023-11-21 20:28 ` [PATCH v4 07/11] leds: aw200xx: enable disable_locking flag in regmap config Dmitry Rokosov
2023-11-21 20:28 ` [PATCH v4 08/11] leds: aw200xx: improve autodim calculation method Dmitry Rokosov
2023-11-21 20:28 ` [PATCH v4 09/11] leds: aw200xx: add support for aw20108 device Dmitry Rokosov
2023-11-23 16:44 ` Lee Jones
2023-11-21 20:28 ` [PATCH v4 10/11] dt-bindings: leds: awinic,aw200xx: add AW20108 device Dmitry Rokosov
2023-11-21 20:28 ` [PATCH v4 11/11] dt-bindings: leds: aw200xx: fix led pattern and add reg constraints Dmitry Rokosov
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=20231123163252.GF1354538@google.com \
--to=lee@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=conor+dt@kernel.org \
--cc=ddrokosov@salutedevices.com \
--cc=devicetree@vger.kernel.org \
--cc=gnstark@salutedevices.com \
--cc=kernel@sberdevices.ru \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=rockosov@gmail.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).