From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: cy_huang <u0084500@gmail.com>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
lee.jones@linaro.org, daniel.thompson@linaro.org,
jingoohan1@gmail.com
Cc: pavel@ucw.cz, deller@gmx.de, cy_huang@richtek.com,
lucas_tsai@richtek.com, devicetree@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: backlight: rt4831: Add the new ocp level property
Date: Thu, 9 Jun 2022 12:31:42 +0200 [thread overview]
Message-ID: <7b8653c1-355d-b390-042d-e02085a3910a@linaro.org> (raw)
In-Reply-To: <1654741339-12756-2-git-send-email-u0084500@gmail.com>
On 09/06/2022 04:22, cy_huang wrote:
> From: ChiYuan Huang <cy_huang@richtek.com>
>
> Add 'richtek,bled-ocp-microamp' property to make it chooseable.
>
> The wrong backlight ocp level may affect the backlight channel output
> current smaller than configured.
>
> Signed-off-by: ChiYuan Huang <cy_huang@richtek.com>
> ---
> Since v3:
> - Refine the description for backlight ocp property.
> - Use the enum to list the supported value.
>
> Since v2:
> - Change the property name from 'richtek,bled-ocp-sel' to 'richtek,bled-ocp-microamp'.
>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-06-09 10:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 2:22 [PATCH v3 0/2] Add the property to make backlight OCP level selectable cy_huang
2022-06-09 2:22 ` [PATCH v3 1/2] dt-bindings: backlight: rt4831: Add the new ocp level property cy_huang
2022-06-09 9:26 ` Daniel Thompson
2022-06-09 10:31 ` Krzysztof Kozlowski [this message]
2022-06-09 2:22 ` [PATCH v3 2/2] backlight: rt4831: Apply ocp level from devicetree cy_huang
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=7b8653c1-355d-b390-042d-e02085a3910a@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=cy_huang@richtek.com \
--cc=daniel.thompson@linaro.org \
--cc=deller@gmx.de \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jingoohan1@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee.jones@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=lucas_tsai@richtek.com \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=u0084500@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;
as well as URLs for NNTP newsgroup(s).