linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shubhrajyoti Datta <omaplinuxkernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Linux SPI slave support
Date: Tue, 17 Jul 2012 14:30:57 +0530	[thread overview]
Message-ID: <CAM=Q2csOFt5hnvS-Ah8ghrSympgkfv0zAYgb7sMu_GacWkLCBA@mail.gmail.com> (raw)
In-Reply-To: <201207171052.49859.marex-ynQEQJNshbs@public.gmane.org>

On Tue, Jul 17, 2012 at 2:22 PM, Marek Vasut <marex-ynQEQJNshbs@public.gmane.org> wrote:
> Dear Shubhrajyoti Datta,
>
>> On Mon, Jul 16, 2012 at 5:56 AM, Marek Vasut <marex-ynQEQJNshbs@public.gmane.org> wrote:
>> > Dear Shubhrajyoti Datta,
[..]
>> The other option is to have something like a gpio  for synchronization.
>
> Synchronisation of what exactly? With my hardware (that doesn't exist yet I
> guess), the idea is to simply cross-connect the MISO/MOSI pins and connect the
> CLK signal. Is that possible btw?

IIUC , the clock is to be driven by master. The slave gets the clock.
Master knows when to start and stop the transaction.

However for the slave the options are to
1) Keep listening always.
2) Use something to syncronize( I may have used the word loosely)
master and slave.
So that it doesnt have to listen always.

Btw it is just a suggestion. I am not opposed to any other implementation.

Thanks and Regards,

>
> Thanks!
>

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

      parent reply	other threads:[~2012-07-17  9:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-30  3:15 Linux SPI slave support Marek Vasut
     [not found] ` <201206300515.41575.marex-ynQEQJNshbs@public.gmane.org>
2012-06-30  6:28   ` Shubhrajyoti Datta
     [not found]     ` <CAM=Q2cs8zGTMu+Du1E8aLkiLpyB6mVH=Omt7pJRe1iFBb+Zqaw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-06-30 11:42       ` Marek Vasut
2012-07-01 18:23       ` Marek Vasut
2012-07-16  0:26       ` Marek Vasut
     [not found]         ` <201207160226.19409.marex-ynQEQJNshbs@public.gmane.org>
2012-07-17  8:12           ` Shubhrajyoti Datta
     [not found]             ` <CAM=Q2ctBCOtSkC-vK4+drsuAmEkk4e=Tk3ZQtZYfqqOejhS_xw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-07-17  8:52               ` Marek Vasut
     [not found]                 ` <201207171052.49859.marex-ynQEQJNshbs@public.gmane.org>
2012-07-17  9:00                   ` Shubhrajyoti Datta [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='CAM=Q2csOFt5hnvS-Ah8ghrSympgkfv0zAYgb7sMu_GacWkLCBA@mail.gmail.com' \
    --to=omaplinuxkernel-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=marex-ynQEQJNshbs@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 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).