From: Krzysztof Kozlowski <krzk@kernel.org>
To: Matthias Fend <matthias.fend@emfend.at>,
Pavel Machek <pavel@ucw.cz>, Lee Jones <lee@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
bsp-development.geo@leica-geosystems.com
Subject: Re: [PATCH 2/2] leds: tps6131x: add support for Texas Instruments TPS6131X flash LED driver
Date: Mon, 10 Mar 2025 08:46:39 +0100 [thread overview]
Message-ID: <554823f8-be69-452d-908d-a7c7a80bcd9e@kernel.org> (raw)
In-Reply-To: <20250228-leds-tps6131x-v1-2-d1071d90f9ea@emfend.at>
On 28/02/2025 11:31, Matthias Fend wrote:
> + tps6131x->reset_gpio = devm_gpiod_get_optional(&client->dev, "reset", GPIOD_OUT_HIGH);
> + ret = tps6131x_reset_chip(tps6131x);
> + if (ret)
> + return dev_err_probe(&client->dev, ret, "Failed to reset LED controller\n");
> +
> + ret = tps6131x_init_chip(tps6131x);
> + if (ret)
> + return dev_err_probe(&client->dev, ret, "Failed to initialize LED controller\n");
> +
> + ret = tps6131x_led_class_setup(tps6131x);
> + if (ret)
> + return dev_err_probe(&client->dev, ret, "Failed to setup led class\n");
> +
> + ret = tps6131x_v4l2_setup(tps6131x);
> + if (ret)
> + return dev_err_probe(&client->dev, ret, "Failed to setup v4l2 flash\n");
> +
> + return 0;
> +}
> +
> +static void tps6131x_remove(struct i2c_client *client)
> +{
> + struct tps6131x *tps6131x = i2c_get_clientdata(client);
> +
> + v4l2_flash_release(tps6131x->v4l2_flash);
> +
> + cancel_delayed_work_sync(&tps6131x->torch_refresh_work);
> +}
> +
> +static const struct of_device_id of_tps6131x_leds_match[] = {
> + { .compatible = "ti,tps61310" },
> + { .compatible = "ti,tps61311" },
No differences? So devices are fully compatible? Then it should be
expressed in the binding with fallback. Or the binding description or
commit msg should explain why they are not compatible.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-10 7:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 10:31 [PATCH 0/2] Support for Texas Instruments TPS6131X flash LED driver Matthias Fend
2025-02-28 10:31 ` [PATCH 1/2] dt-bindings: leds: add Texas Instruments TPS6131x " Matthias Fend
2025-02-28 18:24 ` Conor Dooley
2025-03-10 7:20 ` Matthias Fend
2025-03-10 7:43 ` Krzysztof Kozlowski
2025-03-10 7:49 ` Krzysztof Kozlowski
2025-03-10 8:40 ` Matthias Fend
2025-03-10 11:45 ` Krzysztof Kozlowski
2025-02-28 10:31 ` [PATCH 2/2] leds: tps6131x: add support for Texas Instruments TPS6131X " Matthias Fend
2025-03-10 7:46 ` Krzysztof Kozlowski [this message]
2025-03-10 8:04 ` Matthias Fend
2025-03-10 11:46 ` Krzysztof Kozlowski
2025-03-10 14:49 ` Lee Jones
2025-03-14 8:28 ` Matthias Fend
2025-03-14 10:52 ` Lee Jones
2025-03-14 11:27 ` Matthias Fend
2025-03-14 11:45 ` Lee Jones
2025-03-14 12:38 ` Matthias Fend
2025-03-14 14:13 ` Lee Jones
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=554823f8-be69-452d-908d-a7c7a80bcd9e@kernel.org \
--to=krzk@kernel.org \
--cc=bsp-development.geo@leica-geosystems.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=matthias.fend@emfend.at \
--cc=pavel@ucw.cz \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).