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>
Subject: Re: [PATCH v2 3/3] leds: rgb: leds-ktd202x: Skip regulator settings for Xiaomi pad2
Date: Mon, 19 Feb 2024 15:28:24 +0200 (EET) [thread overview]
Message-ID: <9f2d02ff-5a8a-4c11-a1a3-bea43d7b6454@linux.intel.com> (raw)
In-Reply-To: <20240216160526.235594-4-hpa@redhat.com>
On Sat, 17 Feb 2024, Kate Hsuan wrote:
> The controller is already powered by BP25890RTWR on Xiaomi Pad2 so the
> regulator settings can be ignored.
>
> Signed-off-by: Kate Hsuan <hpa@redhat.com>
> ---
> drivers/leds/rgb/leds-ktd202x.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/drivers/leds/rgb/leds-ktd202x.c b/drivers/leds/rgb/leds-ktd202x.c
> index 8eb79c342fb6..6fd0794988e9 100644
> --- a/drivers/leds/rgb/leds-ktd202x.c
> +++ b/drivers/leds/rgb/leds-ktd202x.c
> @@ -14,7 +14,9 @@
> #include <linux/of.h>
> #include <linux/of_device.h>
> #include <linux/regmap.h>
> +#ifndef CONFIG_ACPI
> #include <linux/regulator/consumer.h>
> +#endif
Why you need #ifndef here?
> #define KTD2026_NUM_LEDS 3
> #define KTD2027_NUM_LEDS 4
> @@ -105,18 +107,22 @@ struct ktd202x {
>
> static int ktd202x_chip_disable(struct ktd202x *chip)
> {
> +#ifndef CONFIG_ACPI
> int ret;
> +#endif
>
> if (!chip->enabled)
> return 0;
>
> regmap_write(chip->regmap, KTD202X_REG_RESET_CONTROL, KTD202X_ENABLE_CTRL_SLEEP);
>
> +#ifndef CONFIG_ACPI
> ret = regulator_bulk_disable(ARRAY_SIZE(chip->regulators), chip->regulators);
> if (ret) {
> dev_err(chip->dev, "Failed to disable regulators: %d\n", ret);
> return ret;
> }
> +#endif
>
> chip->enabled = false;
> return 0;
> @@ -129,11 +135,13 @@ static int ktd202x_chip_enable(struct ktd202x *chip)
> if (chip->enabled)
> return 0;
>
> +#ifndef CONFIG_ACPI
> ret = regulator_bulk_enable(ARRAY_SIZE(chip->regulators), chip->regulators);
> if (ret) {
> dev_err(chip->dev, "Failed to enable regulators: %d\n", ret);
> return ret;
> }
> +#endif
> chip->enabled = true;
>
> ret = regmap_write(chip->regmap, KTD202X_REG_RESET_CONTROL, KTD202X_ENABLE_CTRL_WAKE);
> @@ -560,6 +568,7 @@ static int ktd202x_probe(struct i2c_client *client)
> return ret;
> }
>
> +#ifndef CONFIG_ACPI
> chip->regulators[0].supply = "vin";
> chip->regulators[1].supply = "vio";
> ret = devm_regulator_bulk_get(dev, ARRAY_SIZE(chip->regulators), chip->regulators);
> @@ -573,10 +582,12 @@ static int ktd202x_probe(struct i2c_client *client)
> dev_err_probe(dev, ret, "Failed to enable regulators.\n");
> return ret;
> }
> +#endif
>
> chip->num_leds = (int) (unsigned long)i2c_get_match_data(client);
>
> ret = ktd202x_probe_dt(chip);
> +#ifndef CONFIG_ACPI
> if (ret < 0) {
> regulator_bulk_disable(ARRAY_SIZE(chip->regulators), chip->regulators);
> return ret;
> @@ -587,6 +598,10 @@ static int ktd202x_probe(struct i2c_client *client)
> dev_err_probe(dev, ret, "Failed to disable regulators.\n");
> return ret;
> }
> +#else
> + if (ret < 0)
> + return ret;
> +#endif
>
> mutex_init(&chip->mutex);
To me this entire approach looks quite ugly. It would be much cleaner to
have something along these lines:
#ifndef CONFIG_ACPI
static int ktd202x_regulators_disable(struct ktd202x *chip)
{
int ret;
ret = regulator_bulk_disable(ARRAY_SIZE(chip->regulators), chip->regulators);
if (ret)
dev_err(chip->dev, "Failed to disable regulators: %d\n", ret);
return ret;
}
...
#else
static inline int ktd202x_regulators_disable(struct ktd202x *chip) { return 0; }
...
#endif
And call that function without any #ifdefs from the other code.
--
i.
next prev parent reply other threads:[~2024-02-19 13:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 16:05 [PATCH v2 0/3] KTD2026 indicator LED for X86 Xiaomi Pad2 Kate Hsuan
2024-02-16 16:05 ` [PATCH v2 1/3] platform: x86-android-tablets: other: Add swnode for Xiaomi pad2 indicator LED Kate Hsuan
2024-02-19 14:07 ` Hans de Goede
2024-02-20 3:22 ` Kate Hsuan
2024-02-16 16:05 ` [PATCH v2 2/3] leds: rgb: leds-ktd202x: Get device properties through fwnode to support ACPI Kate Hsuan
2024-02-16 16:05 ` [PATCH v2 3/3] leds: rgb: leds-ktd202x: Skip regulator settings for Xiaomi pad2 Kate Hsuan
2024-02-19 13:28 ` Ilpo Järvinen [this message]
2024-02-19 14:04 ` Hans de Goede
2024-02-20 4:21 ` Kate Hsuan
2024-02-19 13:57 ` [PATCH v2 0/3] KTD2026 indicator LED for X86 Xiaomi Pad2 Ilpo Järvinen
2024-02-20 4:34 ` Kate Hsuan
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=9f2d02ff-5a8a-4c11-a1a3-bea43d7b6454@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-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