[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250522-led-fix-v2-0-652046323ec3@axis.com>
Date: Thu, 22 May 2025 16:14:47 +0200
From: Johan Adolfsson <johan.adolfsson@...s.com>
To: Lee Jones <lee@...nel.org>, Pavel Machek <pavel@...nel.org>, "Jacek
Anaszewski" <jacek.anaszewski@...il.com>
CC: <linux-leds@...r.kernel.org>, <linux-kernel@...r.kernel.org>, "Johan
Adolfsson" <johan.adolfsson@...s.com>, <kernel@...s.com>
Subject: [PATCH RFC v2 0/2] leds-lp50xx: Support reg to set multi_index.
Since devicetree nodes are (sometimes?) processed in reverse order,
support reg as the actual multi_index index so yo get well defined
color order presented in the multi_index file.
Not sure if reusing reg for this is the correct way or if another
property such as "multi_index" or similar should be used instead.
Looks like reg is used for similar things at least.
Or should the whole "reverse the devicetree" problem be fixed instead?
Update bindings to match implementation, and add description for the
reg property.
Signed-off-by: Johan Adolfsson <johan.adolfsson@...s.com>
---
Changes in v2:
- Avoid duplicate assignment. dev_err and return -EINVAL on error.
- Update bindings doc.
- Link to v1: https://lore.kernel.org/r/20250506-led-fix-v1-1-56a39b55a7fc@axis.com
---
Johan Adolfsson (2):
leds: leds-lp50xx: Handle reg to get correct multi_index
dt-bindings: leds: lp50xx: Document child reg, fix example
Documentation/devicetree/bindings/leds/leds-lp50xx.yaml | 11 ++++++++---
drivers/leds/leds-lp50xx.c | 8 +++++++-
2 files changed, 15 insertions(+), 4 deletions(-)
---
base-commit: 38fec10eb60d687e30c8c6b5420d86e8149f7557
change-id: 20250225-led-fix-444fb544584a
Best regards,
--
Johan Adolfsson <johan.adolfsson@...s.com>
Powered by blists - more mailing lists