From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sergio Perez <sergio@pereznus.es>, linux-iio@vger.kernel.org
Cc: devicetree@vger.kernel.org, tduszyns@gmail.com, jic23@kernel.org
Subject: Re: [PATCH v3] iio: light: bh1750: Add hardware reset support via GPIO
Date: Tue, 18 Mar 2025 08:31:02 +0100 [thread overview]
Message-ID: <eeb66fc0-27f6-49c7-a539-2964c6a4662a@kernel.org> (raw)
In-Reply-To: <20250318005045.3189-1-sergio@pereznus.es>
On 18/03/2025 01:50, Sergio Perez wrote:
> Some BH1750 sensors require a hardware reset before they can be
> detected on the I2C bus. This patch adds support for an optional
> reset GPIO that can be specified in the device tree.
>
> The reset sequence pulls the GPIO low and then high before
> initializing the sensor, which enables proper detection with
> tools like i2cdetect.
>
> Update the devicetree binding documentation to include the new
> reset-gpios property with examples.
>
> Signed-off-by: Sergio Perez <sergio@pereznus.es>
> ---
> .../devicetree/bindings/iio/light/bh1750.yaml | 5 +++++
> drivers/iio/light/bh1750.c | 22 +++++++++++++++++++
Nothing improved.
If you keep ignoring our responses, you will get a NAK. Respond inline
to previous emails and confirm that you understand the feedback and you
implemented it.
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.
Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.
You missed at least devicetree list (maybe more), so this won't be
tested by automated tooling. Performing review on untested code might be
a waste of time.
Please kindly resend and include all necessary To/Cc entries.
It seems my or other reviewer's previous comments were not fully
addressed. Maybe the feedback got lost between the quotes, maybe you
just forgot to apply it. Please go back to the previous discussion and
either implement all requested changes or keep discussing them.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-03-18 7:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 0:50 [PATCH v3] iio: light: bh1750: Add hardware reset support via GPIO Sergio Perez
2025-03-18 7:31 ` Krzysztof Kozlowski [this message]
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=eeb66fc0-27f6-49c7-a539-2964c6a4662a@kernel.org \
--to=krzk@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.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