From: Shawn Guo <shawnguo2@yeah.net>
To: "Michal Vokáč" <michal.vokac@ysoft.com>
Cc: Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: imx6dl-yapp43: Increase LED current to match the yapp4 HW design
Date: Mon, 12 Aug 2024 19:48:36 +0800 [thread overview]
Message-ID: <Zrn2lL6E1IEBAlYj@dragon> (raw)
In-Reply-To: <20240723142519.134083-1-michal.vokac@ysoft.com>
On Tue, Jul 23, 2024 at 04:25:19PM +0200, Michal Vokáč wrote:
> On the imx6dl-yapp4 revision based boards, the RGB LED is not driven
> directly by the LP5562 driver but through FET transistors. Hence the LED
> current is not determined by the driver but by the LED series resistors.
>
> On the imx6dl-yapp43 revision based boards, we removed the FET transistors
> to drive the LED directly from the LP5562 but forgot to tune the output
> current to match the previous HW design.
>
> Set the LED current on imx6dl-yapp43 based boards to the same values
> measured on the imx6dl-yapp4 boards and limit the maximum current to 20mA.
>
> Fixes: 7da4734751e0 ("ARM: dts: imx6dl-yapp43: Add support for new HW revision of the IOTA board")
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Michal Vokáč <michal.vokac@ysoft.com>
Applied, thanks!
prev parent reply other threads:[~2024-08-12 11:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 14:25 [PATCH] ARM: dts: imx6dl-yapp43: Increase LED current to match the yapp4 HW design Michal Vokáč
2024-08-12 11:48 ` Shawn Guo [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=Zrn2lL6E1IEBAlYj@dragon \
--to=shawnguo2@yeah.net \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.vokac@ysoft.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stable@vger.kernel.org \
/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).