From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Sergio Pérez" <sergio@pereznus.es>, linux-iio@vger.kernel.org
Cc: tduszyns@gmail.com, jic23@kernel.org, lars@metafoo.de,
robh@kernel.org, conor+dt@kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] iio: light: bh1750: Add hardware reset support via GPIO
Date: Tue, 18 Mar 2025 17:23:39 +0100 [thread overview]
Message-ID: <bde38364-5c20-4030-ad7d-9ae38971b260@kernel.org> (raw)
In-Reply-To: <202b4446-0ce4-4288-8588-6edfc32125d1@kernel.org>
On 18/03/2025 17:21, Krzysztof Kozlowski wrote:
> On 18/03/2025 17:06, Sergio Pérez wrote:
>>
>> El 18/03/2025 a las 16:16, Krzysztof Kozlowski escribió:
>>> On 18/03/2025 15:16, Sergio Pérez wrote:
>>>> Hello,
>>>>
>>>> El 17/03/2025 a las 8:24, Krzysztof Kozlowski escribió:
>>>>> 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.
>>> You keep ignoring paragraphs. Did you read this?
>>
>> I pass this check several times and every time I do any step to make
>> sure I am well.
>>
>> scripts/checkpatch.pl -f drivers/iio/light/bh1750.c
>> total: 0 errors, 0 warnings, 354 lines checked
>
>
> That's not how you run checkpatch. Read the submitting patches. Just
> like the name tells you, check the patch, you run it on the patch.
BTW, I wonder which guideline told you to run it on the file? Because
checkpatch description and submitting patches tell about running it on
the patches, so I wonder where did you get suggestion to run it like that?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-18 16:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250316145514.627-1-sergio@pereznus.es>
[not found] ` <01f48f6d-55a4-4dbe-b1ae-ef8c54dcc1ff@kernel.org>
[not found] ` <64182937-29e9-45dc-aa2f-5f2b739056a1@me.com>
2025-03-18 13:28 ` [PATCH] iio: light: bh1750: Add hardware reset support via GPIO 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 [this message]
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
[not found] ` <20250317115815.2416c741@jic23-huawei>
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=bde38364-5c20-4030-ad7d-9ae38971b260@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@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