linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: festevam@gmail.com (Fabio Estevam)
To: linux-arm-kernel@lists.infradead.org
Subject: SLAVE Side SPI kernel driver development
Date: Fri, 24 Aug 2012 12:14:00 -0300	[thread overview]
Message-ID: <CAOMZO5Ds6NKsTCptQXDGZDJasb119hYWqXMzX8nG5WFArysL7A@mail.gmail.com> (raw)
In-Reply-To: <1345820228.87750.YahooMailNeo@web29604.mail.ird.yahoo.com>

On Fri, Aug 24, 2012 at 11:57 AM, Bastelli Carlo (yahoo)
<carlo_bastelli@yahoo.it> wrote:
> Hello, I'm Carlo, I have a difficult task at work, my boss asked me to
> develop
>  a driver SPI slave side on embedded ARM processor running Linux.
> Precisely linux occur on the SPI bus as a slave, not master as required
> by the hierarchical structure of the current kernel. The new driver
> will
>  receive via interrupt and respond when selected by its chip select. Can
>  anyone suggest the best way to develop this driver?. Personally, I
> have identified two main roads, the first if possible to exploit the
> structure SPI master driver, with a few tricks that now I can not
> define. The second most radical, write a driver for a UART like, but
> managing the SPI device.
> Thank you for any suggestions or examples.

Marek got spi slave running on a mx28. See his patch:
http://www.spinics.net/lists/arm-kernel/msg190860.html

Regards,

Fabio Estevam

  reply	other threads:[~2012-08-24 15:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-24 14:57 SLAVE Side SPI kernel driver development Bastelli Carlo (yahoo)
2012-08-24 15:14 ` Fabio Estevam [this message]
2012-08-24 15:38   ` Marek Vasut
2012-08-24 16:54     ` Ned Forrester
2012-08-25  7:46       ` Bastelli Carlo
2012-08-25 11:44         ` Marek Vasut
2012-08-25 14:06           ` Bastelli Carlo

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=CAOMZO5Ds6NKsTCptQXDGZDJasb119hYWqXMzX8nG5WFArysL7A@mail.gmail.com \
    --to=festevam@gmail.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).