From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Stephan Gerhold <stephan@gerhold.net>,
Pavel Machek <pavel@ucw.cz>, Lee Jones <lee@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Nikita Travkin <nikita@trvn.ru>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, "Lin,
Meng-Bo" <linmengbo0689@protonmail.com>
Subject: Re: [PATCH v3 1/3] dt-bindings: leds: aw2013: Document interrupt
Date: Tue, 15 Aug 2023 22:31:04 +0200 [thread overview]
Message-ID: <ced3e7fd-dca2-0ea7-8847-54c3efbe3165@linaro.org> (raw)
In-Reply-To: <20230815-aw2013-vio-v3-1-2505296b0856@gerhold.net>
On 15/08/2023 19:21, Stephan Gerhold wrote:
> AW2013 has an optional interrupt pin "INTN" which is used to report
> completion of started operations (e.g. power up or LED breath effects).
> The driver does not use it (yet) but it should be described for
> completeness inside the DT schema.
>
> Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
> ---
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-08-15 20:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 17:21 [PATCH v3 0/3] leds: aw2013: Document interrupt and pull-up supply Stephan Gerhold
2023-08-15 17:21 ` [PATCH v3 1/3] dt-bindings: leds: aw2013: Document interrupt Stephan Gerhold
2023-08-15 20:31 ` Krzysztof Kozlowski [this message]
2023-08-15 17:21 ` [PATCH v3 3/3] leds: aw2013: Enable pull-up supply for interrupt and I2C Stephan Gerhold
[not found] ` <20230815-aw2013-vio-v3-2-2505296b0856@gerhold.net>
2023-08-15 20:31 ` [PATCH v3 2/3] dt-bindings: leds: Document " Krzysztof Kozlowski
2023-08-16 5:38 ` [PATCH v3 0/3] leds: aw2013: Document interrupt and pull-up supply Nikita Travkin
2023-08-18 15:47 ` Lee Jones
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=ced3e7fd-dca2-0ea7-8847-54c3efbe3165@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linmengbo0689@protonmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=nikita@trvn.ru \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=stephan@gerhold.net \
/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;
as well as URLs for NNTP newsgroup(s).