From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/3] arm: mvebu: Enable USB controllers on Armada 370/XP boards
Date: Wed, 23 Jan 2013 19:03:52 +0100 [thread overview]
Message-ID: <20130123190352.2d001218@skate> (raw)
In-Reply-To: <CALF0-+XJEXJ2B3NLu5DvyxaDuuMNP=zk+z8QUd4GTQULW3BpyA@mail.gmail.com>
Dear Ezequiel Garcia,
On Wed, 23 Jan 2013 14:04:42 -0300, Ezequiel Garcia wrote:
> from the OpenBlocks AX3-4 board dts file, since you mentioned this
> board uses that USB
> port for a PCIe connector -- if I understood correctly.
No. The OpenBlocks has a different USB controller that sits on the PCIe
bus. There is nothing like a PCIe port that uses a USB port, that
doesn't make sense.
> So, IMHO, if OpenBlocks uses third USB port to connect some PCIe
> controller, we should activate it in the dts file.
>
> What do you think?
No, see above.
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-23 18:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 15:26 [PATCH v2 1/3] arm: mvebu: Add support for USB host controllers in Armada 370/XP Ezequiel Garcia
2013-01-23 15:26 ` [PATCH v2 2/3] arm: mvebu: Enable USB controllers on Armada 370/XP boards Ezequiel Garcia
2013-01-23 17:04 ` Ezequiel Garcia
2013-01-23 18:03 ` Thomas Petazzoni [this message]
2013-01-23 18:08 ` Ezequiel Garcia
2013-01-23 21:14 ` Eric Bénard
2013-02-15 21:28 ` Jason Cooper
2013-01-23 15:26 ` [PATCH v2 3/3] arm: mvebu: Update defconfig to select USB support Ezequiel Garcia
2013-02-15 21:26 ` Jason Cooper
2013-01-23 17:06 ` [PATCH v2 1/3] arm: mvebu: Add support for USB host controllers in Armada 370/XP Ezequiel Garcia
2013-01-23 17:40 ` Jason Cooper
2013-01-29 18:56 ` Ezequiel Garcia
2013-01-29 19:03 ` Jason Cooper
2013-01-31 1:19 ` Nobuhiro Iwamatsu
2013-02-15 21:28 ` Jason Cooper
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=20130123190352.2d001218@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;
as well as URLs for NNTP newsgroup(s).