From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: horms@verge.net.au, linux-renesas-soc@vger.kernel.org,
robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
devicetree@vger.kernel.org
Cc: magnus.damm@gmail.com, linux@arm.linux.org.uk,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: porter: add MAX3355 support
Date: Wed, 27 Jan 2016 01:14:21 +0300 [thread overview]
Message-ID: <4506196.xOgpYRO52t@wasted.cogentembedded.com> (raw)
In-Reply-To: <1674850.BZpGW9kEud@wasted.cogentembedded.com>
Now that Maxim Integrated MAX3355 'extcon' driver and device tree bindings
are upstream along with the 'extcon' hook in the Renesas USBHS driver, we
can add MAX3355 device node to the Porter device tree and properly refer
to it from the USBHS node instead of using "renesas,enable-gpio" property
which only allowed checking the USB ID pin at the driver probe time; now
this pin's state can be monitored dynamically!
Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
---
This patch is against 'renesas-devel-20160126-v4.5-rc1' tag of Simon Horman's
'renesas.git' repo.
arch/arm/boot/dts/r8a7791-porter.dts | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
Index: renesas/arch/arm/boot/dts/r8a7791-porter.dts
===================================================================
--- renesas.orig/arch/arm/boot/dts/r8a7791-porter.dts
+++ renesas/arch/arm/boot/dts/r8a7791-porter.dts
@@ -90,6 +90,12 @@
1800000 0>;
};
+ max3355: usb-otg {
+ compatible = "maxim,max3355";
+ maxim,shdn-gpios = <&gpio2 4 GPIO_ACTIVE_HIGH>;
+ id-gpios = <&gpio5 31 GPIO_ACTIVE_HIGH>;
+ };
+
hdmi-out {
compatible = "hdmi-connector";
type = "a";
@@ -394,7 +400,7 @@
pinctrl-names = "default";
status = "okay";
- renesas,enable-gpio = <&gpio5 31 GPIO_ACTIVE_HIGH>;
+ extcon = <&max3355>;
};
&usbphy {
next prev parent reply other threads:[~2016-01-26 22:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1674850.BZpGW9kEud@wasted.cogentembedded.com>
2016-01-21 22:36 ` [PATCH] ARM: dts: porter: add sound support Sergei Shtylyov
2016-01-25 0:35 ` Kuninori Morimoto
2016-01-26 0:43 ` Simon Horman
2016-01-26 14:31 ` Sergei Shtylyov
2016-01-26 22:14 ` Sergei Shtylyov [this message]
2016-01-28 5:49 ` [PATCH] ARM: dts: porter: add MAX3355 support Yoshihiro Shimoda
2016-01-29 20:28 ` Sergei Shtylyov
2016-01-29 20:49 ` Sergei Shtylyov
2016-02-01 11:17 ` Yoshihiro Shimoda
2016-02-01 17:54 ` Sergei Shtylyov
2016-02-01 19:00 ` Sergei Shtylyov
2016-02-15 1:45 ` Simon Horman
2016-02-15 10:59 ` Sergei Shtylyov
2016-02-11 20:26 ` [PATCH] ARM: dts: silk: add sound support Sergei Shtylyov
2016-02-15 4:56 ` Kuninori Morimoto
2016-02-11 21:49 ` [PATCH] ARM: dts: porter: fix JP3 jumper description Sergei Shtylyov
2016-02-15 4:50 ` Kuninori Morimoto
2016-02-15 21:55 ` Simon Horman
2016-02-13 22:26 ` [PATCH] ARM: dts: porter: remove enable prop from HS-USB device node Sergei Shtylyov
2016-02-26 19:43 ` Sergei Shtylyov
2016-03-02 0:47 ` Simon Horman
2016-04-13 19:36 ` [PATCH] ARM: dts: silk: add DU pins Sergei Shtylyov
2016-06-17 20:53 ` Sergei Shtylyov
2016-06-20 8:35 ` Simon Horman
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=4506196.xOgpYRO52t@wasted.cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=horms@verge.net.au \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.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