DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.it;
  h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=l6TZdMHeOMwmDBoxKxNV/8fTQ2LGtL1BfkMK/nwQmuoZCBDTdfnmgHJ9cn2fEQr30kNYytAAxrdB0l/VmfH/i9+SiDeUpkbsCw3WHeUdI3++fCbEM6rqf39q1ae9KzBJhMS8gRb0Fx/Xvkt3UUIfoPPoR+ZUGAKrlWk604/irig=;
Message-ID: <1345820228.87750.YahooMailNeo@web29604.mail.ird.yahoo.com>
Date: Fri, 24 Aug 2012 15:57:08 +0100 (BST)
From: "Bastelli Carlo \(yahoo\)" <carlo_bastelli@yahoo.it>
Reply-To: "Bastelli Carlo \(yahoo\)" <carlo_bastelli@yahoo.it>
Subject: SLAVE Side SPI kernel driver development
To: "linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 972
Lines: 20

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.

Carlo Bastelli
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/