linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Misbah khan <misbah_khan@engineer.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Drivers' probe function calling order
Date: Fri, 4 Jan 2008 00:41:14 -0800 (PST)	[thread overview]
Message-ID: <14612559.post@talk.nabble.com> (raw)
In-Reply-To: <20080103215456.GA20691@mail.gnudd.com>


Hi Mr Rubini ...

I am writing a driver in which device port is mapped to CPLD and 8 bit data
bus is directly connected from processor to CPLD. Read write on CPLD memory
mapped (buffer/register) is required to control the device. This is now IO
mapped to processor. 

I need to know whether i am right if i impliment like this :- 
         addr=ioremap(base_addr,size);          // Remap to Mem mapped
address 
         out_8(addr) and in_8(addr); 


Alessandro Rubini wrote:
> 
> 
>> how can I force the system to call
>> probe function of the spi driver first?
> 
> You can declare their init functions at different initcall level.  For
> example declaring the dataflash one as late_initcall(). Or declare
> the spi one as subsys_initcall() -- whatever makes more sense.
> 
> There might be cleaner ways according to your setup, but this will
> surely work.
> 
> /alessandro
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 
> 

-- 
View this message in context: http://www.nabble.com/Drivers%27-probe-function-calling-order-tp14601099p14612559.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.

  reply	other threads:[~2008-01-04  8:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-03 16:57 Drivers' probe function calling order DI BACCO ANTONIO - technolabs
2008-01-03 18:04 ` Jeff Mock
2008-01-03 21:54 ` Alessandro Rubini
2008-01-04  8:41   ` Misbah khan [this message]
2008-01-04 10:20   ` ioremap and outb Alessandro Rubini
2008-01-04 10:45     ` Arnd Bergmann

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=14612559.post@talk.nabble.com \
    --to=misbah_khan@engineer.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).