linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: plagnioj@jcrosoft.com (Jean-Christophe PLAGNIOL-VILLARD)
To: linux-arm-kernel@lists.infradead.org
Subject: AT91: SPI: On implementing peripheral chip select decoding
Date: Mon, 16 May 2011 14:44:01 +0200	[thread overview]
Message-ID: <20110516124401.GA17895@game.jcrosoft.org> (raw)
In-Reply-To: <4DCFDBA6.6050007@techworks.ie>

On 14:56 Sun 15 May     , Christian Gagneraud wrote:
> Hi there,
> 
> The AT91SAM9G20 SPI controller (and possibly other SAM9 or other
> SoC) has the ability to work with CS decoding, thus allowing up to
> 15 peripherals with only 4 CS lines (CS[0:3]=0xF meaning no
> peripheral selected).
> I would like to know if anyone has experimented with this feature,
> or if anyone has advices/ideas on how to add support for this
> feature in the linux kernel.
As far as I remenber all at91 and avr32 have this
> 
> Before starting to work on this, I would like to know if this
> feature is common on other platforms or if it's AT91 specific.
> In the former case, it might be wise to include it in the SPI
> subsystem, and in the latter case keep it inside AT91 code.
Make it generic is always good but this can be extended to external Cs
extender as you can use any gpio to manage the Cs or a gpio extender on i2c

Best Regards,
J.

      reply	other threads:[~2011-05-16 12:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-15 13:56 AT91: SPI: On implementing peripheral chip select decoding Christian Gagneraud
2011-05-16 12:44 ` Jean-Christophe PLAGNIOL-VILLARD [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=20110516124401.GA17895@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.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).