linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Remi Lefevre" <rlefevre@gmail.com>
To: "Laurent Pinchart" <laurentp@cse-semaphore.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: FHCI driver adaptation for CPM2
Date: Wed, 17 Dec 2008 21:27:49 +0100	[thread overview]
Message-ID: <4e0b9cb00812171227g47647d31ufaec827ddbab0232@mail.gmail.com> (raw)
In-Reply-To: <200812171633.58081.laurentp@cse-semaphore.com>

> Hi Remi,

Hi Laurent,

> You will find my latest version of the CPM2 FHCI patch attached to this e=
-
> mail. I've never bothered to clean it as we decided to drop the USB host
> function from our device.

Thank you very much. Not clean is better than lost.

> This depends on the disk. Some will probably not check the SOF token, oth=
ers
> will do and behave strangely.
>
>> Also 40% seems quite a lot, even at 1000Hz interruptions, an idea how mu=
ch
>> does the CRC computation contribute in this CPU hogging ?
>
> I haven't measured that, but probably not much. The biggest CPU time eate=
r
> isn't the SOF generation interrupt but the USB packet handling code. The =
CPM2
> USB host controller is really too low-level to be usable (except maybe fo=
r
> specific applications). Comparing the OHCI/UHCI/EHCI and FHCI controllers=
 is
> akin to  bit like comparing a full 16550 UART with a software bit-bang
> implementation. You can get around with it, it might work for your specif=
ic
> application, but you shouldn't try a full speed 115200bds communication w=
hile
> computing a CPU-hungry physical simulation.

That's what I was afraid of. I now understand clearly why you didn't expect=
 that
much better performance with CPM3 in a past message
(http://ozlabs.org/pipermail/linuxppc-embedded/2008-May/030508.html).
Still, as you said, it can have some use for specific applications.

Do you remember the throughput you were able to reach with this cpu overhea=
d ?

> Laurent Pinchart
> CSE Semaphore Belgium

Kind regards,
R=E9mi Lef=E8vre

  reply	other threads:[~2008-12-17 20:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17 15:10 FHCI driver adaptation for CPM2 Remi Lefevre
2008-12-17 15:33 ` Laurent Pinchart
2008-12-17 20:27   ` Remi Lefevre [this message]
2008-12-18 10:23     ` Laurent Pinchart

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=4e0b9cb00812171227g47647d31ufaec827ddbab0232@mail.gmail.com \
    --to=rlefevre@gmail.com \
    --cc=laurentp@cse-semaphore.com \
    --cc=linuxppc-dev@ozlabs.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).