From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Kate Hsuan <hpa@redhat.com>
Cc: "Pavel Machek" <pavel@ucw.cz>, "Lee Jones" <lee@kernel.org>,
linux-leds@vger.kernel.org, platform-driver-x86@vger.kernel.org,
"Hans de Goede" <hdegoede@redhat.com>,
"André Apitzsch" <git@apitzsch.eu>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 2/2] leds: rgb: leds-ktd202x: Get device properties through fwnode to support ACPI
Date: Mon, 11 Mar 2024 14:03:29 +0200 (EET) [thread overview]
Message-ID: <b6e19702-8ec1-38cb-8c43-a3067ebb2017@linux.intel.com> (raw)
In-Reply-To: <20240306025801.8814-3-hpa@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 533 bytes --]
On Wed, 6 Mar 2024, Kate Hsuan wrote:
> This LED controller also installed on a Xiaomi pad2 and it is a x86
> platform. The original driver is based on device tree and can't be
> used for this ACPI based system. This patch migrated the driver to
> use fwnode to access the properties. Moreover, the fwnode API
> supports device tree so this work won't effect the original
> implementations.
>
> Signed-off-by: Kate Hsuan <hpa@redhat.com>
FWIW,
Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
--
i.
next prev parent reply other threads:[~2024-03-11 12:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 2:57 [PATCH v4 0/2] KTD2026 indicator LED for X86 Xiaomi Pad2 Kate Hsuan
2024-03-06 2:58 ` [PATCH v4 1/2] platform: x86-android-tablets: other: Add swnode for Xiaomi pad2 indicator LED Kate Hsuan
2024-03-11 22:42 ` Andy Shevchenko
2024-03-12 10:35 ` Ilpo Järvinen
2024-03-13 7:44 ` Kate Hsuan
2024-03-06 2:58 ` [PATCH v4 2/2] leds: rgb: leds-ktd202x: Get device properties through fwnode to support ACPI Kate Hsuan
2024-03-11 12:03 ` Ilpo Järvinen [this message]
2024-03-11 18:48 ` André Apitzsch
2024-03-11 23:04 ` Andy Shevchenko
2024-03-22 5:44 ` Kate Hsuan
2024-03-22 16:01 ` Andy Shevchenko
2024-03-24 14:48 ` Kate Hsuan
2024-03-11 12:05 ` [PATCH v4 0/2] KTD2026 indicator LED for X86 Xiaomi Pad2 Ilpo Järvinen
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=b6e19702-8ec1-38cb-8c43-a3067ebb2017@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=git@apitzsch.eu \
--cc=hdegoede@redhat.com \
--cc=hpa@redhat.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=platform-driver-x86@vger.kernel.org \
/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