linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vicente Bergas <vicencb@gmail.com>
To: Vivek Unune <npcomplete13@gmail.com>
Cc: Heiko Stuebner <heiko@sntech.de>, <robh+dt@kernel.org>,
	<mark.rutland@arm.com>, <ezequiel@collabora.com>,
	<akash@openedev.com>, <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-rockchip@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, Felipe Balbi <balbi@kernel.org>,
	Felipe Balbi <felipe.balbi@linux.intel.com>,
	Roger Quadros <rogerq@ti.com>
Subject: Re: [PATCH] arm64: dts: rockchip: Fix usb-c on Hugsun X99 TV Box
Date: Sun, 06 Oct 2019 21:50:16 +0200	[thread overview]
Message-ID: <4cb2b781-e177-4008-86ae-a9108bd303e4@gmail.com> (raw)
In-Reply-To: <20191005005200.GA11418@vivek-desktop>

On Saturday, October 5, 2019 2:52:00 AM CEST, Vivek Unune wrote:
> On Fri, Oct 04, 2019 at 11:45:08PM +0200, Heiko Stuebner wrote:
>> Hi Vivek,
>> 
>> Am Montag, 30. September 2019, 01:46:15 CEST schrieb Vivek Unune: ...
>
> Hi Heiko,
>
> I tested the c09b73cf patch without modifying exsisting dts. I can confirm
> that that patch doesn't work for me. No usb-c devices were recognized.
>
> Vicenç - were you able to test it?

I can also confirm that

c09b73cfac2a9317f1104169045c519c6021aa1d
usb: dwc3: don't set gadget->is_otg flag

alone does not fix the issue.

e1d9149e8389f1690cdd4e4056766dd26488a0fe
arm64: dts: rockchip: Fix USB3 Type-C on rk3399-sapphire

is still required for the USB-C to work on the Sapphire board.

Regards,
  Vicenç.

> As soon as I apply dts patch, usb-c devices are recognized.
>
> Thanks,
>
> Vivek


  reply	other threads:[~2019-10-06 19:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-29  3:22 [PATCH] arm64: dts: rockchip: Fix usb-c on Hugsun X99 TV Box Vivek Unune
2019-09-29 11:22 ` Vicente Bergas
2019-09-29 23:46   ` Vivek Unune
2019-10-04 21:45     ` Heiko Stuebner
2019-10-05  0:52       ` Vivek Unune
2019-10-06 19:50         ` Vicente Bergas [this message]
2019-10-10 21:30 ` Heiko Stuebner

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=4cb2b781-e177-4008-86ae-a9108bd303e4@gmail.com \
    --to=vicencb@gmail.com \
    --cc=akash@openedev.com \
    --cc=balbi@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ezequiel@collabora.com \
    --cc=felipe.balbi@linux.intel.com \
    --cc=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=npcomplete13@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=rogerq@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;
as well as URLs for NNTP newsgroup(s).