From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: Support Question
Date: Thu, 20 May 2010 15:11:56 +0200 [thread overview]
Message-ID: <4BF5351C.80306@atmel.com> (raw)
In-Reply-To: <AANLkTin9qYxhbKe_ZDFvPbteM6Zn1H2M5jY6mAaH_Jxu@mail.gmail.com>
Le 19/05/2010 19:06, Amit kumar :
> Dear Experts,
>
> I am using SBC 9260 for development of a data acquisition platform. I am
> using the SPI for data acquisition through 14 bit ADC slave. Currently
> my board has debian 5.0 kernel version 2.6.30. I am using the spidriver
> (spidev )for using the SPI on the board in master mode . Everything is
> working fine and I am able to send and receive data . The only problem
> is between the activation and deactivation of chip select.It takes
> around 70microseconds for chipselect deactivation and then activation .
> Since speed of my 4 channel ADC is 1MSPS so i need to bring down delay
> as minimum as possible. I checked out the value of the registers
> DLYBCS , DLYBCT , DLYBS and all are indicating the values 0.
>
> Therefore I don;t have any idea from where the delay is being
> introduced. Is it a problem of OS or there is nythng else involved .
> Kindly guide me through this . I need urgent help .... any information
> abt delay is welcome.
In the atmel SPI driver, chipselect are managed by GPIO and not
automatically by the IP. I think that this is why you experience such
delays.
I am not totally aware about the reasons for this hand-made management
but I guess that you can find information on this mailing-list...
Best regards,
--
Nicolas Ferre
next prev parent reply other threads:[~2010-05-20 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1274199223.1763.0.camel@ubuntu.ubuntu-domain>
2010-05-19 17:06 ` Support Question Amit kumar
2010-05-20 13:11 ` Nicolas Ferre [this message]
2010-05-20 17:18 ` Bill Gatliff
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=4BF5351C.80306@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=linux-arm-kernel@lists.infradead.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).