All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Boibessot <julien.boibessot-GANU6spQydw@public.gmane.org>
To: Sascha Hauer <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	linux-arm-kernel-xIg/pKzrS19vn6HldHNs0ANdhmdF6hFW@public.gmane.org
Subject: Re: SPI: Add SPI driver for most known i.MX SoCs
Date: Sun, 21 Jun 2009 15:10:21 +0200	[thread overview]
Message-ID: <4A3E313D.8020008@free.fr> (raw)
In-Reply-To: <20090602172259.GB32355-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>

Hi Sascha,

Sascha Hauer a écrit :
> On Tue, Jun 02, 2009 at 10:13:22AM +0200, Julien Boibessot wrote:
>   
>> I don't know yet if it's related to bitbang but I would say that your  
>> driver is 2x slowier that current inkernel one.
>>     
>
> Have you checked that the driver gets the baudrate correct? If it is
> maybe my driver produces more interrupts than the in kernel driver.
> Maybe you could produce a defined workload with both drivers and compare
> the outputs of /proc/interrupts afterwards.
>   
Clock seems ok. The problem is the "setup" time between 2 transfers.
We use an ADC (MAX1027) from which we try to get the data as fast as 
possible (successive SPI read transfers of 16 bytes) and the time 
between 2 transfers was quite doubled when switching to your new driver.

I will try to spend more time to check that after the summer holidays ;-).

Regards,
Julien

------------------------------------------------------------------------------
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org

      parent reply	other threads:[~2009-06-21 13:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-04 21:43 SPI: Add SPI driver for most known i.MX SoCs Sascha Hauer
     [not found] ` <20090504214307.GN15603-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-06-02  8:13   ` Julien Boibessot
     [not found]     ` <4A24DF22.4040601-GANU6spQydw@public.gmane.org>
2009-06-02 17:22       ` Sascha Hauer
     [not found]         ` <20090602172259.GB32355-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-06-21 13:10           ` Julien Boibessot [this message]

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=4A3E313D.8020008@free.fr \
    --to=julien.boibessot-ganu6spqydw@public.gmane.org \
    --cc=linux-arm-kernel-xIg/pKzrS19vn6HldHNs0ANdhmdF6hFW@public.gmane.org \
    --cc=s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
    --cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.