Linux-Rockchip Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
To: Tomohiro Mayama
	<parly-gh-HEvi76orzLt5vQOrPBq+1Q@public.gmane.org>,
	linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: rk3328-rock64: USB ports are broken since commit ef05bcb6
Date: Thu, 7 Mar 2019 14:19:23 +0000	[thread overview]
Message-ID: <4543627b-e68d-2cd6-ebaa-b53d4e81a35d@arm.com> (raw)
In-Reply-To: <f1894045-573b-dd6e-4453-fbec702aa9ad-HEvi76orzLt5vQOrPBq+1Q@public.gmane.org>

On 07/03/2019 13:52, Tomohiro Mayama wrote:
> Hello,
> 
> I'm experiencing a problem that Rock64 USB ports (both 2.0 and 3.0) are
> not working.
> 
> After some investigation, I found that reverting a pin assignment change
> by the commit ef05bcb6[1] seems to make functioning them again.
> But according to the schematic[2], the pin assignment seems to be
> correct. I suspect that the schematic might be incorrect.

Judging by that schematic, I suspect that the GPIO should probably be 
ACTIVE_LOW.

Robin.

> There are some people experiencing the same problem in Arch Linux ARM
> forum[3].
> 
> Is this a known issue?
> 
> 
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git/diff/?id=ef05bcb60c1a8841e38c91923ba998181117a87c
> [2] http://files.pine64.org/doc/rock64/ROCK64_Schematic_v2.0_20171019.pdf, page 8
> [3] https://archlinuxarm.org/forum/viewtopic.php?f=23&t=13321
> 
> 
> Regards,
> Tomohiro Mayama
> 
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip
> 

  parent reply	other threads:[~2019-03-07 14:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 13:52 rk3328-rock64: USB ports are broken since commit ef05bcb6 Tomohiro Mayama
     [not found] ` <f1894045-573b-dd6e-4453-fbec702aa9ad-HEvi76orzLt5vQOrPBq+1Q@public.gmane.org>
2019-03-07 14:19   ` Robin Murphy [this message]
     [not found]     ` <4543627b-e68d-2cd6-ebaa-b53d4e81a35d-5wv7dgnIgG8@public.gmane.org>
2019-03-07 14:51       ` Tomohiro Mayama

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=4543627b-e68d-2cd6-ebaa-b53d4e81a35d@arm.com \
    --to=robin.murphy-5wv7dgnigg8@public.gmane.org \
    --cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=parly-gh-HEvi76orzLt5vQOrPBq+1Q@public.gmane.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