From: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>
To: Shubhrajyoti Datta
<omaplinuxkernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Linux SPI slave support
Date: Tue, 17 Jul 2012 10:52:49 +0200 [thread overview]
Message-ID: <201207171052.49859.marex@denx.de> (raw)
In-Reply-To: <CAM=Q2ctBCOtSkC-vK4+drsuAmEkk4e=Tk3ZQtZYfqqOejhS_xw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Dear Shubhrajyoti Datta,
> On Mon, Jul 16, 2012 at 5:56 AM, Marek Vasut <marex-ynQEQJNshbs@public.gmane.org> wrote:
> > Dear Shubhrajyoti Datta,
> >
> >> Hello,
> >>
> >> On Sat, Jun 30, 2012 at 8:45 AM, Marek Vasut <marex-ynQEQJNshbs@public.gmane.org> wrote:
> >> > Hello,
> >> >
> >> > is there currently any ongoing effort to support SPI slave mode in
> >> > Linux?
> >> >
> >> > If there is none, could you please share any hints that might help me
> >> > better choose and go in the direction of implementing the SPI slave
> >> > support?
> >>
> >> May be you may want to check the archives.
> >> You may want to see below before designing.
> >>
> >> http://permalink.gmane.org/gmane.linux.kernel.spi.devel/7495
> >
> > [...]
> >
> > So, idea V2:
> >
> > 1) Separate out common parts from struct spi_master
> > 2) Create struct spi_slave
> > 2a) Implement spi_slave_send_message for spi_slave
> > 2b) Implement <?> netlink interface to push and pull messages to/from
> > userland ?
> >
> > The protocol won't be done in kernel, but completely in userland.
> >
> > Is this good approach to take? Or maybe 2b can be replaced by blocking
> > read on character device? I think netlink interface might actually be
> > suited quite well for this task.
>
> 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?
Thanks!
> > Best regards,
> > Marek Vasut
Best regards,
Marek Vasut
------------------------------------------------------------------------------
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/
next prev parent reply other threads:[~2012-07-17 8:52 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 [this message]
[not found] ` <201207171052.49859.marex-ynQEQJNshbs@public.gmane.org>
2012-07-17 9:00 ` Shubhrajyoti Datta
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=201207171052.49859.marex@denx.de \
--to=marex-ynqeqjnshbs@public.gmane.org \
--cc=omaplinuxkernel-Re5JQEeQqe8AvxtiuMwx3w@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).