From: Roger Quadros <rogerq@kernel.org>
To: Nishanth Menon <nm@ti.com>
Cc: vigneshr@ti.com, kristo@kernel.org, srk@ti.com,
r-gunasekaran@ti.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: ti: k3-am625-sk: Enable Type-C port for USB0
Date: Sat, 25 Mar 2023 15:03:49 +0200 [thread overview]
Message-ID: <88c7d438-28ad-cc17-6abe-d8e1853260e9@kernel.org> (raw)
In-Reply-To: <20230324181542.luvmpvjx2uclic52@reemerge>
On 24/03/2023 20:15, Nishanth Menon wrote:
> On 15:31-20230324, Roger Quadros wrote:
>> USB0 is a Type-C port with dual data role and power sink.
>>
>> Signed-off-by: Roger Quadros <rogerq@kernel.org>
>> ---
>> arch/arm64/boot/dts/ti/k3-am625-sk.dts | 40 ++++++++++++++++++++++++--
>> 1 file changed, 38 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-am625-sk.dts b/arch/arm64/boot/dts/ti/k3-am625-sk.dts
>> index be027fad5f61..c80b12943881 100644
>> --- a/arch/arm64/boot/dts/ti/k3-am625-sk.dts
>> +++ b/arch/arm64/boot/dts/ti/k3-am625-sk.dts
>> @@ -315,6 +315,33 @@ &main_i2c0 {
>> pinctrl-names = "default";
>> pinctrl-0 = <&main_i2c0_pins_default>;
>> clock-frequency = <400000>;
>> +
>> + tps6598x@3f {
>> + compatible = "ti,tps6598x";
>> + reg = <0x3f>;
>> + interrupt-parent = <&exp1>;
>> + interrupts = <17 IRQ_TYPE_EDGE_FALLING>;
>> + interrupt-names = "irq";
>> +
>> + connector {
>> + compatible = "usb-c-connector";
>> + label = "USB-C";
>> + self-powered;
>> + data-role = "dual";
>> + power-role = "sink";
>> + ports {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + port@0 {
>> + reg = <0>;
>> + usb_con_hs: endpoint {
>> + remote-endpoint = <&usb0_hs_ep>;
>> + };
>> + };
>> + };
>> + };
>> + };
>> };
>>
>> &main_i2c1 {
>> @@ -336,7 +363,7 @@ exp1: gpio@22 {
>> "UART1_FET_BUF_EN", "WL_LT_EN",
>> "GPIO_HDMI_RSTn", "CSI_GPIO1",
>> "CSI_GPIO2", "PRU_3V3_EN",
>> - "HDMI_INTn", "TEST_GPIO2",
>> + "HDMI_INTn", "PD_I2C_IRQ",
>> "MCASP1_FET_EN", "MCASP1_BUF_BT_EN",
>> "MCASP1_FET_SEL", "UART1_FET_SEL",
>> "TSINT#", "IO_EXP_TEST_LED";
>> @@ -486,7 +513,16 @@ &usbss1 {
>> };
>>
>> &usb0 {
>> - dr_mode = "peripheral";
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> + usb-role-switch;
>> +
>> + port@0 {
>> + reg = <0>;
>> + usb0_hs_ep: endpoint {
>> + remote-endpoint = <&usb_con_hs>;
>> + };
>> + };
>> };
>>
>> &usb1 {
>> --
>> 2.34.1
>>
>
> Please see thread:
> https://lore.kernel.org/all/20230321-am62-lp-sk-v2-0-0a56e1694804@ti.com/
> you might need to rebase off that.
>
OK.
cheers,
-roger
prev parent reply other threads:[~2023-03-25 13:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 13:31 [PATCH 0/2] arm64: dts: ti: k3-am625-sk: Enable Type-C dual-role Roger Quadros
2023-03-24 13:31 ` [PATCH 1/2] arm64: dts: ti: k3-am625-sk: Add ti,vbus-divider property to usbss1 Roger Quadros
2023-03-24 18:14 ` Nishanth Menon
2023-03-25 13:03 ` Roger Quadros
2023-03-24 13:31 ` [PATCH 2/2] arm64: dts: ti: k3-am625-sk: Enable Type-C port for USB0 Roger Quadros
2023-03-24 18:15 ` Nishanth Menon
2023-03-25 13:03 ` Roger Quadros [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=88c7d438-28ad-cc17-6abe-d8e1853260e9@kernel.org \
--to=rogerq@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nm@ti.com \
--cc=r-gunasekaran@ti.com \
--cc=srk@ti.com \
--cc=vigneshr@ti.com \
/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