Many applications require more chip select lines than the board or
processor allow. Introduce a mechanism to allow use of GPIO pins as
chip select lines with the McSPI controller. To use this
tionality,
one simply provides a table mapping CS line numbers to GPIO numbers
omap2_mcspi_platform_config
On Sat, 12 Feb 2011 01:33:24 -0700, Grant Likely
wrote:
> (Sorry for the really laggy reply)
>
No worries, I was just starting to think about this again myself.
> I don't see it being that big a deal. gpio drivers are pretty
> lightweight and it is fine to have domain-specific limitations on h
On Fri, Dec 24, 2010 at 01:05:56AM -0500, Ben Gamari wrote:
> On Thu, 23 Dec 2010 20:28:19 -0700, Grant Likely
> wrote:
> > On Thu, Dec 23, 2010 at 09:27:20PM -0500, Ben Gamari wrote:
> > > I understand your concerns, but I'm not sure how to satisfy them without
> > > crippling the design's abili
On Thu, 23 Dec 2010 20:28:19 -0700, Grant Likely
wrote:
> On Thu, Dec 23, 2010 at 09:27:20PM -0500, Ben Gamari wrote:
> > I understand your concerns, but I'm not sure how to satisfy them without
> > crippling the design's ability to accomodate my use-case. I can't pass a
> > GPIO line per spi_boa
On Thu, Dec 23, 2010 at 09:27:20PM -0500, Ben Gamari wrote:
> On Thu, 23 Dec 2010 17:37:12 -0700, Grant Likely
> wrote:
> > On Thu, Dec 23, 2010 at 4:09 PM, Ben Gamari wrote:
> > > The reason I left this up to the board is it's easy to foresee cases
> > > where you want a non-trivial mapping bet
On Thu, 23 Dec 2010 17:37:12 -0700, Grant Likely
wrote:
> On Thu, Dec 23, 2010 at 4:09 PM, Ben Gamari wrote:
> > The reason I left this up to the board is it's easy to foresee cases
> > where you want a non-trivial mapping between logical CS numbers and CS
> > pin states. In my case, I using a 2
On Thu, Dec 23, 2010 at 4:09 PM, Ben Gamari wrote:
> On Thu, 23 Dec 2010 14:38:57 -0700, Grant Likely
> wrote:
>> On Tue, Dec 21, 2010 at 10:56 AM, Ben Gamari wrote:
>> > This mechanism is in large part stolen from the s3c64xx-spi module. To
>> > use this functionality, one simply must define a
On Thu, 23 Dec 2010 14:38:57 -0700, Grant Likely
wrote:
> On Tue, Dec 21, 2010 at 10:56 AM, Ben Gamari wrote:
> > This mechanism is in large part stolen from the s3c64xx-spi module. To
> > use this functionality, one simply must define a set_level function to
> > set the CS state and a omap2_mcs
On Tue, Dec 21, 2010 at 10:56 AM, Ben Gamari wrote:
> This mechanism is in large part stolen from the s3c64xx-spi module. To
> use this functionality, one simply must define a set_level function to
> set the CS state and a omap2_mcspi_csinfo struct for each chip select in
> the board file.
>
> Eac
* Ben Gamari [101221 09:56]:
> This mechanism is in large part stolen from the s3c64xx-spi module. To
> use this functionality, one simply must define a set_level function to
> set the CS state and a omap2_mcspi_csinfo struct for each chip select in
> the board file.
>
> Each spi_board_info.contr
This mechanism is in large part stolen from the s3c64xx-spi module. To
use this functionality, one simply must define a set_level function to
set the CS state and a omap2_mcspi_csinfo struct for each chip select in
the board file.
Each spi_board_info.controller_data should then be set
to point to
11 matches
Mail list logo
