From: Pascal Paillet <p.paillet@st.com>
To: <mcoquelin.stm32@gmail.com>, <alexandre.torgue@st.com>,
<robh+dt@kernel.org>, <mark.rutland@arm.com>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <p.paillet@st.com>
Subject: [PATCH 4/4] ARM: dts: stm32: disable active-discharge for vbus_otg on stm32mp157a-avenger96
Date: Fri, 11 Oct 2019 16:05:33 +0200 [thread overview]
Message-ID: <20191011140533.32619-5-p.paillet@st.com> (raw)
In-Reply-To: <20191011140533.32619-1-p.paillet@st.com>
Active discharge is not needed on vbus_otg and generate unneeded current
consumption.
Signed-off-by: Pascal Paillet <p.paillet@st.com>
---
arch/arm/boot/dts/stm32mp157a-avenger96.dts | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/boot/dts/stm32mp157a-avenger96.dts b/arch/arm/boot/dts/stm32mp157a-avenger96.dts
index d1cc42a92d3f..628c74a45a25 100644
--- a/arch/arm/boot/dts/stm32mp157a-avenger96.dts
+++ b/arch/arm/boot/dts/stm32mp157a-avenger96.dts
@@ -252,7 +252,6 @@
regulator-name = "vbus_otg";
interrupts = <IT_OCP_OTG 0>;
interrupt-parent = <&pmic>;
- regulator-active-discharge = <1>;
};
vbus_sw: pwr_sw2 {
--
2.17.1
next prev parent reply other threads:[~2019-10-11 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 14:05 [PATCH 0/4] update regulator configuration for stm32mp157 boards Pascal Paillet
2019-10-11 14:05 ` [PATCH 1/4] ARM: dts: stm32: add PWR regulators support on stm32mp157 Pascal Paillet
2019-10-11 14:05 ` [PATCH 2/4] ARM: dts: stm32: change default minimal buck1 value " Pascal Paillet
2019-10-11 14:05 ` [PATCH 3/4] ARM: dts: stm32: Fix active discharge usage " Pascal Paillet
2019-10-11 14:05 ` Pascal Paillet [this message]
2019-10-25 10:09 ` [PATCH 0/4] update regulator configuration for stm32mp157 boards Alexandre Torgue
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=20191011140533.32619-5-p.paillet@st.com \
--to=p.paillet@st.com \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--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
all inboxes | Powered by JetHome®