From: Lukasz Majewski <lukma@denx.de>
To: Rob Herring <robh+dt@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
Fabio Estevam <festevam@gmail.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Mans Rullgard <mans@mansr.com>
Subject: [PATCH 2/3] ARM: dts: imx28: add pinmux for USB1 overcurrent on pwm2
Date: Wed, 25 Nov 2020 17:18:14 +0100 [thread overview]
Message-ID: <20201125161815.2361-2-lukma@denx.de> (raw)
In-Reply-To: <20201125161815.2361-1-lukma@denx.de>
From: Mans Rullgard <mans@mansr.com>
Add pinmux setting for USB1 overcurrent on pwm2 pad.
Signed-off-by: Mans Rullgard <mans@mansr.com>
---
arch/arm/boot/dts/imx28.dtsi | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/imx28.dtsi b/arch/arm/boot/dts/imx28.dtsi
index 6e7531b64bf7..6d24546f0abe 100644
--- a/arch/arm/boot/dts/imx28.dtsi
+++ b/arch/arm/boot/dts/imx28.dtsi
@@ -948,6 +948,16 @@
fsl,pull-up = <MXS_PULL_DISABLE>;
};
+ usb1_pins_b: usb1@1 {
+ reg = <1>;
+ fsl,pinmux-ids = <
+ MX28_PAD_PWM2__USB1_OVERCURRENT
+ >;
+ fsl,drive-strength = <MXS_DRIVE_12mA>;
+ fsl,voltage = <MXS_VOLTAGE_HIGH>;
+ fsl,pull-up = <MXS_PULL_DISABLE>;
+ };
+
usb0_id_pins_a: usb0id@0 {
reg = <0>;
fsl,pinmux-ids = <
--
2.20.1
next prev parent reply other threads:[~2020-11-25 16:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 16:18 [PATCH 1/3] ARM: dts: imx28: Fix label name for L2 switch Lukasz Majewski
2020-11-25 16:18 ` Lukasz Majewski [this message]
2020-12-01 1:43 ` [PATCH 2/3] ARM: dts: imx28: add pinmux for USB1 overcurrent on pwm2 Shawn Guo
2020-11-25 16:18 ` [PATCH 3/3] ARM: dts: imx28: Add DTS description of imx28 based XEA board Lukasz Majewski
2020-12-09 22:11 ` Lukasz Majewski
2020-12-22 17:42 ` Lukasz Majewski
2020-12-22 17:58 ` Fabio Estevam
2020-12-01 1:42 ` [PATCH 1/3] ARM: dts: imx28: Fix label name for L2 switch Shawn Guo
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=20201125161815.2361-2-lukma@denx.de \
--to=lukma@denx.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mans@mansr.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).