From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: mvebu: enable the third USB interface on OpenBlocks AX3
Date: Fri, 17 May 2013 15:47:37 +0200 [thread overview]
Message-ID: <519634F9.7060700@free-electrons.com> (raw)
In-Reply-To: <20130517.111810.02327269.yamagata@plathome.co.jp>
Hi Thomas,
On 05/17/2013 04:18 AM, yamagata at plathome.co.jp wrote:
> Dear Mr. Petazzoni
>
>> Besides the two "classic" USB interfaces with normal USB ports on the
>> front side, the PlatHome OpenBlocks AX3 uses the third USB interface
>> of the Marvell SoC in the mini-PCIe connector. This allows certain
>> mini-PCIe cards to expose parts of their functionality as a USB
>> peripheral.
>>
>> This commit enables this third USB interface in the OpenBlocks AX3
>> Device Tree, and also adds comments on top of the two other USB
>> interfaces so that the Device Tree makes it clear which USB interface
>> at the SoC level matches which USB interface visible on the board.
>
> I see the following messages by dmesg with your patch for
> linux-3.10-rc1 and 3.9.2.
>
> ...
> usb 3-1: New USB device found, idVendor=0a5c, idProduct=219c
> usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> usb 3-1: Product: Broadcom BCM2070 Bluetooth Device
> usb 3-1: Manufacturer: Broadcom Corp
> usb 3-1: SerialNumber: B4749F63C1B6
> ...
> Bluetooth: Core ver 2.16
> NET: Registered protocol family 31
> Bluetooth: HCI device and connection manager initialized
> Bluetooth: HCI socket layer initialized
> Bluetooth: L2CAP socket layer initialized
> Bluetooth: SCO socket layer initialized
> usbcore: registered new interface driver btusb
This patch is nice and adds useful information.
I applied and tested on my OpenBlocks AX3 and get the 3rd USB
interface detected. As I don't have any mini-PCIe card which use USB,
I didn't tested it furthermore, but as Atsushi Yamagata managed to
detect an USB device on this interface, we can be pretty confident
with this patch:
Acked-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
Thanks,
--
Gregory Clement, 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-05-17 13:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 16:07 [PATCH] arm: mvebu: enable the third USB interface on OpenBlocks AX3 Thomas Petazzoni
2013-05-17 2:18 ` yamagata at plathome.co.jp
2013-05-17 13:47 ` Gregory CLEMENT [this message]
2013-05-18 19:52 ` Willy Tarreau
2013-05-19 20:19 ` Jason Cooper
2013-05-19 21:30 ` Willy Tarreau
2013-05-20 15:10 ` Jason Cooper
2013-05-20 5:50 ` yamagata at plathome.co.jp
2013-05-20 15:10 ` Jason Cooper
2013-05-20 17:51 ` 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=519634F9.7060700@free-electrons.com \
--to=gregory.clement@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.