mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nobin Mathew" <nobin.mathew@gmail.com>
To: "Midhun Agnihotram" <agnimidhun@gmail.com>
Cc: linux-kernel@vger.kernel.org, "Pierre Ossman" <drzeus-mmc@drzeus.cx>
Subject: Re: platform_driver_register() ??
Date: Tue, 3 Jul 2007 18:28:40 +0530	[thread overview]
Message-ID: <8d6898730707030558o5e110b0v257ffc6350c76069@mail.gmail.com> (raw)
In-Reply-To: <4dde4acb0707030028p2c078a22jd537853f145c2518@mail.gmail.com>

Hi Midhun,
    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.

Nobin Mathew




On 7/3/07, Midhun Agnihotram <agnimidhun@gmail.com> wrote:
> Hi All,
>
>  I have an MMC driver for my kit (i.MX21 based cogent board
> CSB535FS), which is supplied by Cogent (Kernel version 2.6.16).
>
>   The original driver (linux/drivers/mmc/mmc_block.c) uses
> mmc_register_driver() method to register the driver but the one
> supplied by Cogent uses platform_driver_register() method. What is the
> difference between the two?
>
>
> Thanks,
> Midhun.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

  reply	other threads:[~2007-07-03 12:58 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 [this message]
2007-07-03 19:15   ` Pierre Ossman
2007-07-05  9:21     ` Midhun Agnihotram
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=8d6898730707030558o5e110b0v257ffc6350c76069@mail.gmail.com \
    --to=nobin.mathew@gmail.com \
    --cc=agnimidhun@gmail.com \
    --cc=drzeus-mmc@drzeus.cx \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®