From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bay0-omc4-s1.bay0.hotmail.com (bay0-omc4-s1.bay0.hotmail.com [65.54.190.203]) by ozlabs.org (Postfix) with ESMTP id D5A9BB6F10 for ; Wed, 13 Oct 2010 01:54:48 +1100 (EST) Message-ID: From: WANG YiFei To: Subject: ppc405 + MCP23S17 Date: Tue, 12 Oct 2010 22:49:41 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00C8_01CB6A5F.C22F2CA0" List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , ------=_NextPart_000_00C8_01CB6A5F.C22F2CA0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, I'm a newbie for linux device driver development. We have a custom ppc405 board which has MCP23S17 (16-Bit I/O Expander with SPI Interface) on it. I noticed that current kernel has MCP23S08 driver support, I'd like to know: 1. if passing platform data to MCP23S08 driver, can it make MCP23S17 work? 2. Generally, I'd like to know how to pass platform data to a particular device driver. In my mind, platform data should not be in driver code, right? However, I don't know where is the suitable place to pass platform data to driver. 3. How to describe this in dts file? Thanks in advance, YiFei ------=_NextPart_000_00C8_01CB6A5F.C22F2CA0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

I'm a newbie for linux device driver = development.

We have a custom ppc405 board which has = MCP23S17

(16-Bit I/O Expander with SPI Interface) on = it.

I noticed that current kernel has MCP23S08 = driver

support, I'd like to know:

1. if passing platform data to MCP23S08 driver, = can it make

MCP23S17 work?

2. Generally, I'd like to know how to pass = platform data to

a particular device driver. In my = mind, platform data should

not be in driver code, right? = However, I don't know where is

the suitable place to pass platform = data to driver.

3. How to describe this in dts = file?

Thanks in advance,

YiFei

------=_NextPart_000_00C8_01CB6A5F.C22F2CA0--