mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-mmc@drzeus.cx>
To: "Midhun Agnihotram" <agnimidhun@gmail.com>
Cc: "Nobin Mathew" <nobin.mathew@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: platform_driver_register() ??
Date: Sun, 8 Jul 2007 14:23:25 +0200	[thread overview]
Message-ID: <20070708142325.479d380e@poseidon.drzeus.cx> (raw)
In-Reply-To: <4dde4acb0707050221k5a73a4abt2db9e8b0f7c74ae1@mail.gmail.com>

On Thu, 5 Jul 2007 14:51:35 +0530
"Midhun Agnihotram" <agnimidhun@gmail.com> wrote:

> 
>     Is it necessary that the firmware (may be bootloader) notify about
> the MMC host to Linux? The kernel documentation (platform.txt) says :
> 
>  "The firmware should notify the platform bus about devices before the
> legacy drivers have had a chance to load."
> 
>    Have I interpreted the above sentence correctly?
> 

I don't know what the meaning of that sentence was supposed to be, but
platform devices are everything the kernel cannot probe in a "normal"
way. Usually this covers devices that cannot be probed at all, but must
be listed some other way (i.e. manually).

Commonly the arch and machine specific code adds the devices. The
machine code is usually specific to a certain hardware, so the code
"knows" which devices are present, even though it can't probe them.

So to answer your question; no, the firmware doesn't have to tell Linux
about the devices.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org

      reply	other threads:[~2007-07-08 12:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-03  7:28 Midhun Agnihotram
2007-07-03 12:58 ` Nobin Mathew
2007-07-03 19:15   ` Pierre Ossman
2007-07-05  9:21     ` Midhun Agnihotram
2007-07-08 12:23       ` Pierre Ossman [this message]

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=20070708142325.479d380e@poseidon.drzeus.cx \
    --to=drzeus-mmc@drzeus.cx \
    --cc=agnimidhun@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nobin.mathew@gmail.com \
    /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

all inboxes | Powered by JetHome®