linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurentp@cse-semaphore.com>
To: avorontsov@ru.mvista.com
Cc: mike@compulab.co.il, linuxppc-dev@ozlabs.org
Subject: Re: CPM2 USB host driver
Date: Fri, 30 Nov 2007 16:28:27 +0100	[thread overview]
Message-ID: <200711301628.33526.laurentp@cse-semaphore.com> (raw)
In-Reply-To: <20071130124801.GA13141@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 2865 bytes --]

On Friday 30 November 2007 13:48, Anton Vorontsov wrote:
> On Fri, Nov 30, 2007 at 01:30:18PM +0100, Laurent Pinchart wrote:
> > On Friday 30 November 2007 12:16, Vitaly Bordug wrote:
> > > On Fri, 30 Nov 2007 11:45:49 +0100
> > >
> > > Laurent Pinchart wrote:
> > > > Hi everybody,
> > > >
> > > > Linux USB host support for the CPM, CPM2 and CPM2 pro is far from
> > > > complete. Many people showed interest on this list (and on
> > > > linuxppc-embedded) in the past, but nobody managed to complete a
> > > > driver and get it merged.
> > >
> > > that is mainly because of its semi-software nature. However, any
> > > approach would be helpful I beleive.
> >
> > The CPM/CPM2 USB host controller does indeed put some pressure on the
> > CPU. The PowerQuick III family is much better in that respect as its USB
> > host controller is EHCI compliant.
>
> I didn't yet compare with CPM/CPM2, but I wonder if PQIIPro (MPC8360E)
> USB controller is similar to cpms?..

If I'm not mistaken it is very similar to the CPM2 USB host controller, with 
the added ability to generate SOF packets automatically.

The CPM has a packet-level USB host controller. CPM2 introduced a 
transaction-level mode (it still supports packet-level mode). CPM2 pro fixes 
the SOF packets generation issue that wakes the CPU once per millisecond with 
CPM and CPM2.

Some members of the PQ2 and PQ2 pro families don't have a CPM but include a 
USB EHCI controller. I suppose those processors are less versatile (as the 
communication controllers are hardware-based instead of software-based) but 
offer more communication performance.

If I'm not mistaken, the only processor to support USB in the PQ3 family is 
the MPC8555E. Its USB host controller is similar to the CPM2 as it supports 
both packet-level and transaction-level modes, but doesn't generate SOF 
packets automatically. I assume the PQ3 integrates a CPM2 and not a CPM2 pro.

To summarize the issue (and I'd appreciate if someone could confirm this), a 
packet-level FHCI driver would work with CPM, CPM2 and CPM2 pro based 
processors. A transaction-level FHCI driver would work with the CPM2 and CPM2 
pro based processors. For CPM2 pro based processors, SOF packet generation 
can be handled by the CPM.

> I tried to forward-port FHCI from Freescale 2.6.11 kernels. Twice.
> But these efforts always stumbled over more important tasks.

Do you think I start from the FHCI driver provided by Freescale for 2.6.11, 
from the cpm2usb driver or from scratch ?

Both the cpm2usb and FHCI drivers seem to use the packet-level interface. Is 
there any reason not to use the transaction-level interface ?

Best regards,

-- 
Laurent Pinchart
CSE Semaphore Belgium

Chaussée de Bruxelles, 732A
B-1410 Waterloo
Belgium

T +32 (2) 387 42 59
F +32 (2) 387 42 75

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-11-30 15:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30 10:45 CPM2 USB host driver Laurent Pinchart
2007-11-30 11:16 ` Vitaly Bordug
2007-11-30 12:30   ` Laurent Pinchart
2007-11-30 12:48     ` Anton Vorontsov
2007-11-30 13:00       ` Vitaly Bordug
2007-11-30 15:28       ` Laurent Pinchart [this message]
2007-11-30 16:11         ` Anton Vorontsov
2007-11-30 22:32           ` Arnd Bergmann
2007-11-30 23:18             ` David Brownell
2007-12-02  6:31         ` Mike Rapoport
2007-11-30 13:02     ` Vitaly Bordug

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=200711301628.33526.laurentp@cse-semaphore.com \
    --to=laurentp@cse-semaphore.com \
    --cc=avorontsov@ru.mvista.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mike@compulab.co.il \
    /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).