From: Simon South <simon@simonsouth.net>
To: u-boot@lists.denx.de
Subject: Pinebook Pro keyboard (RK3399 OHCI)?
Date: Tue, 14 Jul 2020 11:29:18 -0400 [thread overview]
Message-ID: <875zaq869d.fsf@simonsouth.net> (raw)
In-Reply-To: <87r1teyw59.fsf@lechat.rtp-net.org> (Arnaud Patard's message of "Tue, 14 Jul 2020 17:05:38 +0200")
Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org> writes:
> Did you check if everything needed is enabled in your configuration and
> if the keyboard is detected after a usb start / usb tree ?
It is detected, yes.
I believe the configuration is fine; I see this issue using the standard
"pinebook-pro-rk3399_defconfig" and building either from the latest
commit in git or from the tree at commit 3a5771249 (Peter's, which he
mentioned earlier).
Changing the configuration to remove the XHCI and EHCI drivers, or to
add the Inno USB phy driver, doesn't help.
Beyond that, for BL31 I'm using a release build of v2.3 of the ARM
Trusted Firmware. I've tested using debug and release builds of v2.3 and
v2.2 without seeing a difference.
> Your keyboard is working with linux, right ?
Yes it is. It's only U-Boot that's affected.
The only things I've thought of so far that might be unique about my
setup are
- My PBP is from the latest manufacturing run of a few months ago, not
last year's; and
- I currently have the eMMC module disabled via the internal switch and
am booting off a microSD card.
Otherwise I'm at a total loss. The driver sets everything up correctly
and then the controller just does nothing. In GNU/Linux, everything
works fine. Very strange.
--
Simon South
simon at simonsouth.net
next prev parent reply other threads:[~2020-07-14 15:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 20:31 Pinebook Pro keyboard (RK3399 OHCI)? Simon South
2020-07-14 8:07 ` Peter Robinson
2020-07-14 10:48 ` Simon South
2020-07-14 10:53 ` Peter Robinson
2020-07-14 15:05 ` Arnaud Patard
2020-07-14 15:29 ` Simon South [this message]
2020-07-14 15:40 ` Peter Robinson
2020-07-14 16:04 ` Arnaud Patard
2020-07-14 17:18 ` Simon South
2020-10-01 14:56 ` Simon South
2020-10-02 8:07 ` Arnaud Patard
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=875zaq869d.fsf@simonsouth.net \
--to=simon@simonsouth.net \
--cc=u-boot@lists.denx.de \
/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