From mboxrd@z Thu Jan 1 00:00:00 1970 From: jassi brar Subject: Re: McSPI questions pertaining to GPIO chip select support Date: Thu, 28 Jan 2010 13:33:20 +0900 Message-ID: <1b68c6791001272033q60dd31dbif4de285cd9bac83d@mail.gmail.com> References: <1264016711-sup-309@ben-laptop> <1264651770-sup-5197@ben-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: David Brownell , Michael Hennerich , beagleboard , Eric Miao , spi-devel-general , linux-omap To: Ben Gamari Return-path: In-Reply-To: <1264651770-sup-5197@ben-laptop> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: spi-devel-general-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-spi.vger.kernel.org On Thu, Jan 28, 2010 at 1:10 PM, Ben Gamari wrote: > Hey all! > > Recently I've been thinking about adding support to the McSPI driver for > using GPIO pins as chip selects. As a starting point, I've browsed the > driver source trying to identify what changes would be necessary to add > this support. It seems like the rough idea is, You may loot at drivers/spi/spi_s3c64xx.c in Grant Likely's tree. It doesn't put limit on the number of CS and not even on whether the CS mechanism is simple GPIO toggling(though the callback type is defined to match gpio_set_value). For platform side of it, you need to look in to Ben Dooks' tree. hth ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com