From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Alexander Stein <alexander.stein@ew.tq-group.com>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
Marek Vasut <marex@denx.de>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: [PATCH v1 3/3] [DNI] arm64: dts: mba8mx: Use gpio-delay for LVDS bridge
Date: Thu, 6 Apr 2023 11:33:44 +0200 [thread overview]
Message-ID: <20230406093344.917259-4-alexander.stein@ew.tq-group.com> (raw)
In-Reply-To: <20230406093344.917259-1-alexander.stein@ew.tq-group.com>
Add a gpio-delay for LVDS_BRIDGE_EN_1V8 which ramp-up time is defined
by the external RC filter.
Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
---
Changes since RFC v2:
* Removed 'input' prefix
* Removed 'gpio-line-names' for GPIO controller node
arch/arm64/boot/dts/freescale/mba8mx.dtsi | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/freescale/mba8mx.dtsi b/arch/arm64/boot/dts/freescale/mba8mx.dtsi
index 691e91e84dec..3bae1c8fb8ed 100644
--- a/arch/arm64/boot/dts/freescale/mba8mx.dtsi
+++ b/arch/arm64/boot/dts/freescale/mba8mx.dtsi
@@ -75,6 +75,14 @@ led2: led2 {
};
};
+ gpio_delays: gpio-delays {
+ compatible = "gpio-delay";
+ #gpio-cells = <3>;
+ gpio-controller;
+ gpios = <&expander0 6 GPIO_ACTIVE_HIGH>;
+ gpio-line-names = "LVDS_BRIDGE_EN_1V8";
+ };
+
panel0: panel_lvds0 {
/*
* Display is not fixed, so compatible has to be added from
@@ -269,7 +277,7 @@ &i2c3 {
dsi_lvds_bridge: bridge@2d {
compatible = "ti,sn65dsi83";
reg = <0x2d>;
- enable-gpios = <&expander0 6 GPIO_ACTIVE_HIGH>;
+ enable-gpios = <&gpio_delays 0 130000 0>;
vcc-supply = <®_sn65dsi83_1v8>;
status = "disabled";
--
2.34.1
next prev parent reply other threads:[~2023-04-06 9:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 9:33 [PATCH v1 0/3] gpio: Add gpio-delay support Alexander Stein
2023-04-06 9:33 ` [PATCH v1 1/3] dt-bindings: gpio: Add gpio-delay binding document Alexander Stein
2023-05-31 16:37 ` Krzysztof Kozlowski
2023-06-02 16:29 ` Bartosz Golaszewski
2023-04-06 9:33 ` [PATCH v1 2/3] gpio: Add gpio delay driver Alexander Stein
2023-06-02 16:31 ` Bartosz Golaszewski
2023-04-06 9:33 ` Alexander Stein [this message]
2023-04-07 18:57 ` [PATCH v1 0/3] gpio: Add gpio-delay support andy.shevchenko
2023-04-11 7:19 ` Alexander Stein
2023-04-11 9:34 ` Andy Shevchenko
2023-04-14 6:37 ` Alexander Stein
2023-04-15 15:06 ` Andy Shevchenko
2023-04-16 7:42 ` Krzysztof Kozlowski
2023-04-16 9:36 ` Andy Shevchenko
2023-04-16 11:04 ` Krzysztof Kozlowski
2023-04-16 11:14 ` Andy Shevchenko
2023-04-16 11:21 ` Krzysztof Kozlowski
2023-04-16 11:33 ` Andy Shevchenko
2023-04-16 11:42 ` Krzysztof Kozlowski
2023-04-16 18:46 ` Andy Shevchenko
2023-05-31 6:53 ` Alexander Stein
2023-05-31 12:02 ` Andy Shevchenko
2023-05-31 13:44 ` Linus Walleij
2023-05-31 14:37 ` Andy Shevchenko
2023-05-31 16:37 ` Krzysztof Kozlowski
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=20230406093344.917259-4-alexander.stein@ew.tq-group.com \
--to=alexander.stein@ew.tq-group.com \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=marex@denx.de \
--cc=robh+dt@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).