From: Krzysztof Kozlowski <krzk@kernel.org>
To: Rodrigo Gobbi <rodrigo.gobbi.7@gmail.com>,
robh@kernel.org, krzk+dt@kernel.org, jic23@kernel.org,
dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
conor+dt@kernel.org, mranostay@gmail.com
Cc: ~lkcamp/patches@lists.sr.ht, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: iio: proximity: Add Lidar-lite-v2
Date: Sat, 2 Aug 2025 10:24:20 +0200 [thread overview]
Message-ID: <4033d554-c537-4124-8a0f-24875ff9c2af@kernel.org> (raw)
In-Reply-To: <20250801224112.135918-1-rodrigo.gobbi.7@gmail.com>
On 02/08/2025 00:39, Rodrigo Gobbi wrote:
> Move existing ABI documentation from trivial to
> a dedicated binding file since Lidar is not a trivial
> device considering power-enable and mode control pin.
>
> Also, add a fallback compatible for v3, which has the
> same pinout and is already supported by the driver.
Please wrap commit message according to Linux coding style / submission
process (neither too early nor over the limit):
https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597
You add completely new compatible grmn,lidar-lite-v3 and nothing in
subject or commit msg explains that. Actually subject is completely
opposite - says v2, not v3.
>
> Fixes: b257c1a45e99 ("iio: pulsedlight-lidar-lite-v2: add lidar-lite-v3 property")
What is being fixed? I already asked to describe the issue and I do not
see here issue being fixed. You add new stuff mixed with something else.
See submitting patches how to organize your patchset.
> Signed-off-by: Rodrigo Gobbi <rodrigo.gobbi.7@gmail.com>
> ---
> I was unsure about sending a new v0 patch for this or send a v2. To avoid losing
> the lore about this topic, I`m sending a v2. If this is not correct, I can send a
> new patch later.
>
> +properties:
> + compatible:
> + oneOf:
> + - items:
> + - enum:
> + - grmn,lidar-lite-v3
> + - const: pulsedlight,lidar-lite-v2
> + - const: pulsedlight,lidar-lite-v2
> +
> + reg:
> + maxItems: 1
> +
> + power-gpios:
Please use standard gpio naming, see gpio-consumer-common.yaml.
> + description: GPIO that can be driven low to shut off power to the device.
> + maxItems: 1
> +
> + vdd-supply: true
> +
> +required:
> + - compatible
> + - reg
> + - vdd-supply
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + proximity@62 {
lidar@
> + compatible = "grmn,lidar-lite-v3", "pulsedlight,lidar-lite-v2";
> + reg = <0x62>;
> + vdd-supply = <&vdd_5v0>;
> + };
> + };
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-02 8:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-01 22:39 [PATCH v2] dt-bindings: iio: proximity: Add Lidar-lite-v2 Rodrigo Gobbi
2025-08-02 8:24 ` Krzysztof Kozlowski [this message]
2025-08-02 11:12 ` Jonathan Cameron
2025-08-24 10:23 ` William Breathitt Gray
2025-09-24 22:41 ` Rodrigo Gobbi
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=4033d554-c537-4124-8a0f-24875ff9c2af@kernel.org \
--to=krzk@kernel.org \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mranostay@gmail.com \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=rodrigo.gobbi.7@gmail.com \
--cc=~lkcamp/patches@lists.sr.ht \
/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