Linux IIO development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sergio Perez <sergio@pereznus.es>, linux-iio@vger.kernel.org
Cc: jic23@kernel.org
Subject: Re: [PATCH] iio: light: bh1750: Add hardware reset support via GPIO
Date: Mon, 17 Mar 2025 08:24:21 +0100	[thread overview]
Message-ID: <01f48f6d-55a4-4dbe-b1ae-ef8c54dcc1ff@kernel.org> (raw)
In-Reply-To: <20250316145514.627-1-sergio@pereznus.es>

On 16/03/2025 15:55, 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>

Please run scripts/checkpatch.pl and fix reported warnings. After that,
run also `scripts/checkpatch.pl --strict` and (probably) fix more
warnings. Some warnings can be ignored, especially from --strict run,
but the code here looks like it needs a fix. Feel free to get in touch
if the warning is not clear.

<form letter>
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.
</form letter>


> ---
>  .../devicetree/bindings/iio/light/bh1750.yaml |  20 +++-
>  drivers/iio/light/bh1750.c                    | 113 ++++++++++++------


... and please go through your patch and see what happened there.
>  2 files changed, 95 insertions(+), 38 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/iio/light/bh1750.yaml b/Documentation/devicetree/bindings/iio/light/bh1750.yaml
> index 1a88b3c253d5..d53b221eb84b 100644
> --- a/Documentation/devicetree/bindings/iio/light/bh1750.yaml
> +++ b/Documentation/devicetree/bindings/iio/light/bh1750.yaml
> @@ -11,6 +11,9 @@ maintainers:
>  
>  description: |
>    Ambient light sensor with an i2c interface.
> +  
> +  Some BH1750 sensors require a hardware reset before being properly detected
> +  on the I2C bus. This can be done using the optional reset-gpios property.
>  
>  properties:
>    compatible:
> @@ -23,6 +26,10 @@ properties:
>  
>    reg:
>      maxItems: 1
> +    
> +  reset-gpios:
> +    description: GPIO connected to the sensor's reset line (active low)
> +    maxItems: 1
>  
>  required:
>    - compatible
> @@ -41,5 +48,16 @@ examples:
>          reg = <0x23>;
>        };
>      };
> +  - |
> +    i2c {
> +      #address-cells = <1>;
> +      #size-cells = <0>;
> +
> +      light-sensor@23 {
> +        compatible = "rohm,bh1750";
> +        reg = <0x23>;
> +        reset-gpios = <&gpio2 17 GPIO_ACTIVE_HIGH>;
> +      };
> +    };
>  
> -...
> +...
> \ No newline at end of file

You have unrelated changed all over the place.


Best regards,
Krzysztof

  reply	other threads:[~2025-03-17  7:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-16 14:55 [PATCH] iio: light: bh1750: Add hardware reset support via GPIO Sergio Perez
2025-03-17  7:24 ` Krzysztof Kozlowski [this message]
     [not found]   ` <64182937-29e9-45dc-aa2f-5f2b739056a1@me.com>
2025-03-18 13:28     ` Krzysztof Kozlowski
2025-03-18 14:16   ` Sergio Pérez
2025-03-18 15:16     ` Krzysztof Kozlowski
2025-03-18 16:06       ` Sergio Pérez
2025-03-18 16:21         ` Krzysztof Kozlowski
2025-03-18 16:23           ` Krzysztof Kozlowski
2025-03-18 17:26             ` Sergio Pérez
2025-03-18 17:37               ` Krzysztof Kozlowski
2025-03-18 19:51                 ` Sergio Pérez
2025-03-20  7:15                   ` Krzysztof Kozlowski
2025-03-19  8:46                 ` Krzysztof Kozlowski
2025-03-19 16:26                   ` Sergio Pérez
2025-03-20  7:18                     ` Krzysztof Kozlowski
2025-03-17 11:58 ` Jonathan Cameron
2025-03-18  7:18   ` Krzysztof Kozlowski
2025-03-18 14:35   ` 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=01f48f6d-55a4-4dbe-b1ae-ef8c54dcc1ff@kernel.org \
    --to=krzk@kernel.org \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=sergio@pereznus.es \
    /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