From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.229]) by ozlabs.org (Postfix) with ESMTP id 7034F67B61 for ; Thu, 14 Dec 2006 07:59:22 +1100 (EST) Received: by wr-out-0506.google.com with SMTP id 71so160994wri for ; Wed, 13 Dec 2006 12:59:19 -0800 (PST) Message-ID: Date: Wed, 13 Dec 2006 21:59:18 +0100 From: "Henk Stegeman" To: linuxppc-embedded@ozlabs.org Subject: Best location for call to spi_register_board_info () on PPC (MPC5200) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_119890_10051454.1166043558769" List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , ------=_Part_119890_10051454.1166043558769 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline I'm working on an SPI procol driver on the MPC52XX. I spend some time in trying to find the best location for calling spi_register_board_info () (which basically registers the relations between protocol drivers and the SPI chip selects). I wish to call this function from my copy of the arch/ppc/platforms/Lite5200.c file since these relations are board-specific, however I found that placing the call in any of these functions (eg. lite5200_setup_arch) results in an -ENOMEM from the spi_register_board_info () call. Now I'm calling spi_register_board_info () from the spi controller driver which is soo ugly. Thanks in advance, Henk. ------=_Part_119890_10051454.1166043558769 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I'm working on an SPI procol driver on the MPC52XX.
I spend some time in trying to find the best location for calling spi_register_board_info () (which basically registers the relations between protocol drivers and the SPI chip selects).

I wish to call this function from my copy of the arch/ppc/platforms/Lite5200.c file  since these relations are board-specific, however I found that placing the call in any of these functions (eg. lite5200_setup_arch) results in an -ENOMEM from the spi_register_board_info () call.

Now I'm calling spi_register_board_info () from the spi controller driver which is soo ugly.

Thanks in advance,

Henk.


------=_Part_119890_10051454.1166043558769--