LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Joakim Tjernlund" <joakim.tjernlund@transmode.se>
To: "'Henk Stegeman'" <henk.stegeman@gmail.com>,
	<linuxppc-embedded@ozlabs.org>
Subject: RE: Best location for call to spi_register_board_info () on PPC (MPC5200)
Date: Wed, 13 Dec 2006 22:08:11 +0100	[thread overview]
Message-ID: <035101c71efa$cdf4d3a0$020120ac@Jocke> (raw)
In-Reply-To: <ae4f76fd0612131259h6df7b20fi68561d7878f49483@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]

 


  _____  

From: linuxppc-embedded-bounces+joakim.tjernlund=lumentis.se@ozlabs.org
[mailto:linuxppc-embedded-bounces+joakim.tjernlund=lumentis.se@ozlabs.org] On Behalf Of Henk Stegeman
Sent: den 13 december 2006 21:59
To: linuxppc-embedded@ozlabs.org
Subject: Best location for call to spi_register_board_info () on PPC (MPC5200)


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.  
 
Try doing it as an arch_initcall() in Lite5200.c, I do that in my custom board port file


[-- Attachment #2: Type: text/html, Size: 2148 bytes --]

  reply	other threads:[~2006-12-13 21:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-13 20:59 Best location for call to spi_register_board_info () on PPC (MPC5200) Henk Stegeman
2006-12-13 21:08 ` Joakim Tjernlund [this message]
2006-12-13 21:18 ` Ben Warren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='035101c71efa$cdf4d3a0$020120ac@Jocke' \
    --to=joakim.tjernlund@transmode.se \
    --cc=henk.stegeman@gmail.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox