linux-kernel - Re: platform_driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070703211513.5245946b@poseidon.drzeus.cx>
Date:	Tue, 3 Jul 2007 21:15:13 +0200
From:	Pierre Ossman <drzeus-mmc@...eus.cx>
To:	"Nobin Mathew" <nobin.mathew@...il.com>
Cc:	"Midhun Agnihotram" <agnimidhun@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: platform_driver_register() ??

On Tue, 3 Jul 2007 18:28:40 +0530
"Nobin Mathew" <nobin.mathew@...il.com> wrote:

> 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.
> 

Indeed. You seem to have the hang of this ;)

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/