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

Hi All,


> >     I think mmc driver is layered modules, only top block driver
> > registers driver under  "mmc_bus_type" bus, see
> > drivers/mmc/mmc_sysfs.c and mmc_block.c. I think they are creating a
> > tree of devices of same characteristics under that bus.
> > I think your driver is linux/drivers/mmc/imxmmc.c where it registers a
> > driver for device of type "platform_bus_type". This module will come
> > under above mentioned block driver.
> > Corresponding platform device is registered in
> > linux/arch/arm/mach-imx/generic.c see platform_device imx_mmc_device.


    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?

Thanks,
Midhun.

  reply	other threads:[~2007-07-05  9:21 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 [this message]
2007-07-08 12:23       ` Pierre Ossman

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=4dde4acb0707050221k5a73a4abt2db9e8b0f7c74ae1@mail.gmail.com \
    --to=agnimidhun@gmail.com \
    --cc=drzeus-mmc@drzeus.cx \
    --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®