linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: fabio777 <fabio7774@gmail.com>
To: linuxppc-embedded@ozlabs.org,  bwarren@qstreams.com
Subject: Re: Linuxppc-embedded Digest, Vol 39, Issue 48
Date: Tue, 27 Nov 2007 20:59:44 +0200	[thread overview]
Message-ID: <474C6920.3030109@gmail.com> (raw)
In-Reply-To: <mailman.3149.1196114204.3099.linuxppc-embedded@ozlabs.org>

Thanks Ben,

Here it is

static struct fsl_spi_platform_data k_platform_data = {
    .initial_spmode = 0,
    .bus_num = 1,
    .max_chipselect = 1,
/* board specific information */
    .activate_cs = k_cs_activate,
    .deactivate_cs = k_cs_deactivate,
    .sysclk =    266,
};

static struct spi_board_info spi_board_info[] __initdata = { {
    .modalias    = "kplus",
    .platform_data    = &k_platform_data,
    .max_speed_hz    = 120000,
    .bus_num    = 1,
    .chip_select    = 0,
},
};


struct platform_device k_plus = {
    .name        = "kplus",
    .id        = 1,
    .dev        = {
        .platform_data = &k_platform_data,
    },
};

 platform_device_register(&k_plus);

 spi_register_board_info(spi_board_info, ARRAY_SIZE(spi_board_info))

and then calls  spi_register_driver(&k_driver);

I can't get the into the *probe functions. 

Thanks 





>
> fabio777 wrote:
>   
>> Has anyone been using this driver ?
>>   
>>     
> I use it, on ARCH=powerpc, though.
>   
>> For legacy reasons I need to keep the ppc=arch however I haven't found 
>> out how to get this driver probed at start-up even basing my init on 
>> Lublock.
>>
>>   
>>     
> The driver's expecting a platform device with name "mpc83xx_spi" to be 
> registered in board init code. If you post your init code I may be able 
> to help.
>
> regards,
> Ben
>
>   

       reply	other threads:[~2007-11-27 18:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3149.1196114204.3099.linuxppc-embedded@ozlabs.org>
2007-11-27 18:59 ` fabio777 [this message]
2007-11-27 19:33   ` SPI driver for spi_mpc83xx Ben Warren
2007-11-28 15:41     ` fabio777

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=474C6920.3030109@gmail.com \
    --to=fabio7774@gmail.com \
    --cc=bwarren@qstreams.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;
as well as URLs for NNTP newsgroup(s).