From: Shawn Guo <shawnguo@kernel.org>
To: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
Cc: "Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"NXP Linux Team" <linux-imx@nxp.com>,
"Fabio Estevam" <festevam@gmail.com>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"Oleksij Rempel" <o.rempel@pengutronix.de>,
"Juergen Borleis" <jbe@pengutronix.de>,
"Michael Grzeschik" <m.grzeschik@pengutronix.de>,
"Marco Felsch" <m.felsch@pengutronix.de>,
"Lucas Stach" <l.stach@pengutronix.de>,
"Søren Andersen" <san@skov.dk>, "Sam Ravnborg" <sam@ravnborg.org>
Subject: Re: [PATCH] ARM: dts: imx6: skov: add pwm-regulator to control the panel's VCOM
Date: Sun, 19 Jun 2022 09:42:00 +0800 [thread overview]
Message-ID: <20220619014200.GX254723@dragon> (raw)
In-Reply-To: <20220517071814.3626702-1-u.oelmann@pengutronix.de>
On Tue, May 17, 2022 at 09:18:14AM +0200, Ulrich Ölmann wrote:
> Skov's i.MX6 based boards come in different flavors which have different panels
> attached. For optimal contrast experience each panel type needs an individual
> common voltage (VCOM) to drive its TFT backplane. The latter is generated by an
> LCD bias supply IC controlled by a pwm as input signal. Introduce a pwm-
> regulator to describe this hardware property and parameterize it appropriately
> for the different boards.
>
> Signed-off-by: Ulrich Ölmann <u.oelmann@pengutronix.de>
Applied, thanks!
prev parent reply other threads:[~2022-06-19 1:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 7:18 [PATCH] ARM: dts: imx6: skov: add pwm-regulator to control the panel's VCOM Ulrich Ölmann
2022-06-11 9:31 ` Shawn Guo
2022-06-14 12:53 ` Ulrich Ölmann
2022-06-19 1:42 ` 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=20220619014200.GX254723@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=jbe@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=l.stach@pengutronix.de \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=m.grzeschik@pengutronix.de \
--cc=o.rempel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sam@ravnborg.org \
--cc=san@skov.dk \
--cc=u.oelmann@pengutronix.de \
/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).