Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: YouShenghui <youshenghui0322@163.com>
Cc: Tomasz Figa <tomasz.figa@gmail.com>,
	linux-samsung-soc@vger.kernel.org, linux-spi@vger.kernel.org,
	jassi.brar@samsung.com
Subject: Re: Re: Ask for help on SPI slave side driver support
Date: Mon, 7 Oct 2013 12:33:23 +0100	[thread overview]
Message-ID: <20131007113323.GL21581@sirena.org.uk> (raw)
In-Reply-To: <4cd52b0c.af8e.14184497bb9.Coremail.youshenghui0322@163.com>

[-- Attachment #1: Type: text/plain, Size: 1450 bytes --]

On Sat, Oct 05, 2013 at 12:25:10AM +0800, YouShenghui wrote:
> At 2013-09-30 17:33:17,"Mark Brown" <broonie@kernel.org> wrote: >On Mon, Sep 30, 2013 at 01:20:42AM +0200, Tomasz Figa wrote: > >> Mark will probably know better, but AFAIK there is no API for slave mode  >> SPI available in Linux kernel. Please correct me if I'm wrong. > >That's correct. > >> The code mentioned in the post from your link was some internal vendor  >> code, which is unlikely to be available publicly. However support for  >> slave mode from hardware side seems more or less similar to master mode,  >> which means that assuming you can add some kernel API for it, the  >> modification to the spi-s3c64xx wouldn't be too big. > >There were some people working on slave mode (or at least talking about >it) but I don't think they ever sent it.  It'd probably just be the same >as master mode but with transfers triggered from /CS instead of from >driver action.  The biggest trick would be making sure the transfer is >running before the master actually starts sending data

The formatting of your mail is really bad, I can barely read it.  Please
check the configuration of your mail program, there are some suggstions
for common clients in Documentation/email-clients.txt.

> Thanks for Mark for your answer.
> But how could I trigger from /CS? Could I enable transfer in open syscall?

I'd expect this to be done in-kernel, at least in the first instance.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2013-10-07 11:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-29 16:23 Ask for help on SPI slave side driver support YouShenghui
2013-09-29 23:20 ` Tomasz Figa
2013-09-30  5:38   ` YouShenghui
2013-09-30  9:33   ` Mark Brown
     [not found]     ` <4cd52b0c.af8e.14184497bb9.Coremail.youshenghui0322@163.com>
2013-10-07 11:33       ` Mark Brown [this message]
     [not found]         ` <4e8f3999.9132.141b335ef13.Coremail.youshenghui0322@163.com>
2013-10-14 11:25           ` Re: " Mark Brown
2013-10-14 14:51             ` ysh
2013-10-14 16:24               ` Mark Brown

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=20131007113323.GL21581@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=jassi.brar@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=tomasz.figa@gmail.com \
    --cc=youshenghui0322@163.com \
    /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