From: Svyatoslav Ryhel <clamor95@gmail.com>
To: "Lee Jones" <lee@kernel.org>, "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Jonathan Cameron" <jic23@kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Pavel Machek" <pavel@ucw.cz>,
"Daniel Thompson" <danielt@kernel.org>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Helge Deller" <deller@gmx.de>,
"Svyatoslav Ryhel" <clamor95@gmail.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org, linux-leds@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org
Subject: [PATCH v2 0/2] mfd: lm3533: convert to use OF
Date: Tue, 18 Feb 2025 15:26:58 +0200 [thread overview]
Message-ID: <20250218132702.114669-1-clamor95@gmail.com> (raw)
Add schema and add support for lm3533 mfd to use device
tree bindings.
---
Changes on switching from v1 to v2:
- added unit seffix where it is suitable
- added vendor prefixes where it is suitable
- light sensor mover out of pattern properties
- added references to common schemas
- added detailed descriptions of properties
- removed platform data use
- devices bind and configure themself entirely
using device tree
---
Svyatoslav Ryhel (2):
dt-bindings: mfd: Document TI LM3533 MFD
mfd: lm3533: convert to use OF
.../devicetree/bindings/mfd/ti,lm3533.yaml | 231 ++++++++++++++++++
drivers/iio/light/lm3533-als.c | 40 ++-
drivers/leds/leds-lm3533.c | 45 ++--
drivers/mfd/lm3533-core.c | 199 ++++++---------
drivers/video/backlight/lm3533_bl.c | 68 ++++--
include/linux/mfd/lm3533.h | 35 +--
6 files changed, 417 insertions(+), 201 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mfd/ti,lm3533.yaml
--
2.43.0
next reply other threads:[~2025-02-18 13:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 13:26 Svyatoslav Ryhel [this message]
2025-02-18 13:26 ` [PATCH v2 1/2] dt-bindings: mfd: Document TI LM3533 MFD Svyatoslav Ryhel
2025-02-21 20:38 ` Rob Herring
2025-02-22 7:01 ` Svyatoslav Ryhel
2025-02-22 14:26 ` Jonathan Cameron
2025-02-22 14:29 ` Jonathan Cameron
2025-02-22 14:39 ` Svyatoslav Ryhel
2025-02-22 17:27 ` Jonathan Cameron
2025-02-18 13:27 ` [PATCH v2 2/2] mfd: lm3533: convert to use OF Svyatoslav Ryhel
2025-02-19 14:26 ` Andy Shevchenko
2025-02-19 14:36 ` Svyatoslav Ryhel
2025-02-19 15:06 ` Andy Shevchenko
2025-02-19 15:13 ` Svyatoslav Ryhel
2025-02-19 15:23 ` Andy Shevchenko
2025-02-19 17:39 ` Svyatoslav Ryhel
2025-02-19 20:18 ` Andy Shevchenko
2025-02-19 16:02 ` kernel test robot
2025-02-19 20:20 ` Andy Shevchenko
2025-02-19 23:51 ` kernel test robot
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=20250218132702.114669-1-clamor95@gmail.com \
--to=clamor95@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=conor+dt@kernel.org \
--cc=danielt@kernel.org \
--cc=deller@gmx.de \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jic23@kernel.org \
--cc=jingoohan1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=lee@kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh@kernel.org \
--cc=u.kleine-koenig@baylibre.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