linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: Stefan Roese <sr@denx.de>
Cc: Markus Gothe <nietzsche@lysator.liu.se>,
	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: Fri, 09 Oct 2009 08:39:33 -0700	[thread overview]
Message-ID: <4ACF5935.50409@caviumnetworks.com> (raw)
In-Reply-To: <200910090935.55346.sr@denx.de>

Stefan Roese wrote:
> On Thursday 08 October 2009 23:03:37 David Daney wrote:
>> 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.
> 
> Yes, this Synopsys USB-OTG core is also integrated in some AMCC (Applied 
> Micro) PowerPC's (e.g. PPC405EX and PPC460EX). So we should try to make this 
> driver usable by those platforms as well. But this could be done in a later 
> step.

I can only refer you to '[PATCH 2/2] USB: Add HCD for Octeon SOC' 
(unfortunately eaten by linux-usb but available in the linux-mips 
archives),  The target specific code is all in dwc_otg_octeon.c.  The 
rest should be target independent.  My expectation is that, much as the 
ohci and ehci drivers have target specific code spilt out, we would do 
the same with dwc_otg.


> 
> David, on which Synopsys driver version did you base your driver? The latest 
> version available is 2.90a IIRC.
>

It has this annotation:

  "2.40a 10-APR-2006"

We have made local bug fixes though.

> Cheers,
> Stefan
> 
> --
> DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office@denx.de
> 

  parent reply	other threads:[~2009-10-09 15:41 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
     [not found]       ` <200910090935.55346.sr@denx.de>
2009-10-09 15:39         ` David Daney [this message]
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=4ACF5935.50409@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 \
    --cc=sr@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;
as well as URLs for NNTP newsgroup(s).