From: Chris Packham <judge.packham@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH 0/2] arm: mvebu: a38x: USB2 serdes changes
Date: Thu, 25 Jun 2020 12:48:49 +1200 [thread overview]
Message-ID: <20200625004851.21056-1-judge.packham@gmail.com> (raw)
While debugging this issue with Marvell I found the change that was made
to Marvell's u-boot but doesn't appear to have made it upstream. We're
in the process of checking the affect it has on the USB compliance
testing we're doing.
I have regression tested it against a couple of USB devices (Ethernet
and Storage). But it'd be good to get some more coverage against other
hardware platforms and USB devices.
Chris Packham (2):
arm: mvebu: a38x: Fix typo
arm: mvebu: a38x: Adjust UTMI PHY parameters
.../serdes/a38x/high_speed_env_spec.c | 27 +++++++++++++++----
1 file changed, 22 insertions(+), 5 deletions(-)
--
2.27.0
next reply other threads:[~2020-06-25 0:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 0:48 Chris Packham [this message]
2020-06-25 0:48 ` [PATCH 1/2] arm: mvebu: a38x: Fix typo Chris Packham
2020-06-29 12:09 ` Stefan Roese
2020-06-25 0:48 ` [PATCH 2/2] arm: mvebu: a38x: Adjust UTMI PHY parameters Chris Packham
2020-06-29 12:09 ` Stefan Roese
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=20200625004851.21056-1-judge.packham@gmail.com \
--to=judge.packham@gmail.com \
--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