From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sergio Perez <sergio@pereznus.es>,
Tomasz Duszynski <tduszyns@gmail.com>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: iio: light: bh1750: Add reset-gpios property
Date: Wed, 19 Mar 2025 20:12:57 +0100 [thread overview]
Message-ID: <61d55149-1955-4d5c-84de-d8644727b87f@kernel.org> (raw)
In-Reply-To: <20250319161117.1780-1-sergio@pereznus.es>
On 19/03/2025 17:11, Sergio Perez wrote:
> Some BH1750 sensors require a hardware reset via GPIO before they can
> be properly detected on the I2C bus. Add a new reset-gpios property
> to the binding to support this functionality.
>
> The reset-gpios property allows specifying a GPIO that will be toggled
> during driver initialization to reset the sensor.
>
> Signed-off-by: Sergio Perez <sergio@pereznus.es>
> ---
> Documentation/devicetree/bindings/iio/light/bh1750.yaml | 5 +++++
> 1 file changed, 5 insertions(+)
You just sent v3, while v4 was already on the lists, without improving
and without responding to review.
NAK.
You keep repeating the same mistakes: not reading and responding
feedback and it is getting tiresome.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-19 19:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 16:11 [PATCH v3 1/2] dt-bindings: iio: light: bh1750: Add reset-gpios property Sergio Perez
2025-03-19 16:11 ` [PATCH v3 2/2] iio: light: bh1750: Add hardware reset support via GPIO Sergio Perez
2025-03-19 19:15 ` Krzysztof Kozlowski
2025-03-19 22:40 ` Sergio Pérez
2025-03-20 8:55 ` Krzysztof Kozlowski
2025-03-20 14:38 ` Sergio Pérez
2025-03-19 19:12 ` Krzysztof Kozlowski [this message]
2025-03-19 22:38 ` [PATCH v3 1/2] dt-bindings: iio: light: bh1750: Add reset-gpios property Sergio Pérez
2025-03-20 8:52 ` Krzysztof Kozlowski
2025-03-20 14:32 ` Sergio Pérez
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=61d55149-1955-4d5c-84de-d8644727b87f@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sergio@pereznus.es \
--cc=tduszyns@gmail.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