From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/6] arm: mvebu: Enable USB controllers on Armada XP OpenBlocks AX3-4 board
Date: Wed, 16 Jan 2013 20:37:13 +0100 [thread overview]
Message-ID: <20130116203713.7b396070@skate> (raw)
In-Reply-To: <CALF0-+XKGk+ru3VZ6815KTu_Aj_daYafr+Y5WJ9dXUoFqbTHOQ@mail.gmail.com>
Dear Ezequiel Garcia,
On Wed, 16 Jan 2013 16:16:59 -0300, Ezequiel Garcia wrote:
> >> + usb at d0050000 {
> >> + status = "okay";
> >> + };
> >> + usb at d0051000 {
> >> + status = "okay";
> >> + };
> >> + usb at d0052000 {
> >> + status = "okay";
> >> + };
> > USB2 of openblocks-ax3-4 is used as Mini-PCIE.
> > I think this is unnecessary.
>
> Mmm... could you explain this with some more detail.
> Unfortunately, I don't have access to an Openblocks board to check on
> this, so I'd appreciate any clarification.
>
> Is there any Openblocks datasheet or hardware schematics publicly
> available for me to look at?
As far as I know, there is no public document. I've been given access
to a PDF, in Japanese, that gives some details about the hardware.
>From what I can read, only 2 USB ports are used from the internal
Marvell EHCI controller.
Another USB port is available, but it is connected to a USB controller
that sits on the PCIe bus. And the PCIe interface on which this USB
controller is connected is not enabled in the default U-Boot shipped
with AX3-4 (at least not with the generation I have). I've been given
an U-Boot version that is supposed to enable this PCIe interface, but I
haven't tested yet.
Anyway, from a Marvell EHCI controller perspective, only two ports are
used, as Nobuhiro said. I am not sure which ports, but it seems like
the first two ones were used. One of the two physical ports is a
combined USB / eSATA port, but I don't think this makes any difference
at the software level.
I don't have the OpenBlocks AX3-4 with me right now, but I could
probably make a test on Friday.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-01-16 19:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 9:54 [PATCH 1/6] arm: mvebu: Add support for USB host controllers in Armada 370/XP Ezequiel Garcia
2013-01-15 9:54 ` [PATCH 2/6] arm: mvebu: Enable USB controllers on Armada 370 evaluation board Ezequiel Garcia
2013-01-15 13:07 ` Arnd Bergmann
2013-01-15 13:58 ` Ezequiel Garcia
2013-01-15 9:54 ` [PATCH 3/6] arm: mvebu: Enable USB controllers on Armada 370 Mirabox board Ezequiel Garcia
2013-01-15 9:54 ` [PATCH 4/6] arm: mvebu: Enable USB controllers on Armada XP evaluation board Ezequiel Garcia
2013-01-15 9:54 ` [PATCH 5/6] arm: mvebu: Enable USB controllers on Armada XP OpenBlocks AX3-4 board Ezequiel Garcia
2013-01-16 0:01 ` Nobuhiro Iwamatsu
2013-01-16 19:16 ` Ezequiel Garcia
2013-01-16 19:37 ` Thomas Petazzoni [this message]
2013-01-19 0:07 ` Nobuhiro Iwamatsu
2013-01-19 0:11 ` Gregory CLEMENT
2013-01-19 0:21 ` Nobuhiro Iwamatsu
2013-01-15 9:54 ` [PATCH 6/6] arm: mvebu: Update defconfig to select USB support Ezequiel Garcia
2013-01-15 10:23 ` [PATCH 1/6] arm: mvebu: Add support for USB host controllers in Armada 370/XP Florian Fainelli
2013-01-15 10:49 ` Ezequiel Garcia
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=20130116203713.7b396070@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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