From: David Daney <ddaney@caviumnetworks.com>
To: Markus Gothe <nietzsche@lysator.liu.se>
Cc: ralf@linux-mips.org, linux-mips@linux-mips.org,
linux-usb@vger.kernel.org, gregkh@suse.de
Subject: Re: [PATCH 1/2] MIPS: Octeon: Add USB platform device.
Date: Thu, 08 Oct 2009 14:03:37 -0700 [thread overview]
Message-ID: <4ACE53A9.8080504@caviumnetworks.com> (raw)
In-Reply-To: <39A458B3-45D1-405E-A3F1-E41A6DB7EDE8@lysator.liu.se>
Markus Gothe wrote:
> Is this just the HCD part AND is it tested to be endian safe?
>
This particular patch just adds platform devices for the Octeon SOC.
The main patch (Patch 2/2) can be seen here:
http://marc.info/?l=linux-mips&m=125502126531841&w=2
For some reason it hasn't come out on linux-usb yet.
If you look at '[PATCH 2/2] USB: Add HCD for Octeon SOC', you will see
that it has the hcd support. I have omitted pcd support from this set,
as I am working towards getting hcd mergable first.
As for endian issues, the current Octeon support in the kernel is for
big-endian only, so since the usb hardware is on the same chip as the
CPU, endian safety is not currently an issue. I have heard rumors that
some ralink and PPC variants have the same controller, but I have no way
of confirming this or even testing the code as I don't have that hardware.
> Think of a 16-bits BE GIO-bus connected to the LE-32 HCD. (It's an
> incredible mess to debug that kind of setup...)
>
Indeed.
David Daney
> //Markus Gothe - The panamahat hacker
>
> On 8 Oct 2009, at 02:15, David Daney wrote:
>
>> Signed-off-by: David Daney <ddaney@caviumnetworks.com>
>> ---
>> arch/mips/cavium-octeon/octeon-platform.c | 105 ++
>> arch/mips/include/asm/octeon/cvmx-usbcx-defs.h | 1199
>> ++++++++++++++++++++++++
[...]
next prev parent reply other threads:[~2009-10-08 21:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 0:13 [PATCH 0/2] USB: Add USB HCD for Octeon SOCs David Daney
2009-10-08 0:15 ` [PATCH 1/2] MIPS: Octeon: Add USB platform device David Daney
[not found] ` <39A458B3-45D1-405E-A3F1-E41A6DB7EDE8@lysator.liu.se>
2009-10-08 21:03 ` David Daney [this message]
[not found] ` <200910090935.55346.sr@denx.de>
2009-10-09 15:39 ` David Daney
2009-10-08 0:15 ` [PATCH 2/2] USB: Add HCD for Octeon SOC David Daney
2009-10-08 17:09 ` [PATCH 0/2] USB: Add USB HCD for Octeon SOCs David Daney
2009-10-08 20:55 ` Greg KH
2009-10-08 23:06 ` David Daney
2009-10-08 21:07 ` Ralf Baechle
2009-10-10 1:08 ` Ralf Baechle
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=4ACE53A9.8080504@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=gregkh@suse.de \
--cc=linux-mips@linux-mips.org \
--cc=linux-usb@vger.kernel.org \
--cc=nietzsche@lysator.liu.se \
--cc=ralf@linux-mips.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).