linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aaron Lu <aaron.lu@intel.com>
To: "Fu, Zhonghui" <zhonghui.fu@linux.intel.com>,
	chris@printf.net, ulf.hansson@linaro.org, jh80.chung@samsung.com,
	tgih.jun@samsung.com, linux-mmc@vger.kernel.org,
	linux-kernel@vger.kernel.org, jackey.shen@amd.com,
	gregkh@linuxfoundation.org
Subject: Re: one doubt about mmc_sdio_init_card function
Date: Wed, 02 Jul 2014 10:52:02 +0800	[thread overview]
Message-ID: <53B373D2.7000306@intel.com> (raw)
In-Reply-To: <53B249A4.2040404@linux.intel.com>

On 07/01/2014 01:39 PM, Fu, Zhonghui wrote:
> 
> Hi, all
> 
> The mmc_sdio_init_card(drivers/mmc/core/sdio.c) function calls mmc_alloc_card(drivers/mmc/core/bus.c) function to allocate a card structure. card->dev.bus is assigned with mmc_bus_type in mmc_alloc_card function. Why not assign sdio_bus_type to card->dev.bus?

sdio card, mmc card, sd card are all devices on the mmc bus, hence their
bus type is set to mmc_bus_type.

sdio function device is a device on the sdio bus, hence its bus type is
sdio_bus_type.

Hope this helps,
Aaron

> 
> 
> struct mmc_card *mmc_alloc_card(struct mmc_host *host, struct device_type *type)
> {
>     struct mmc_card *card;
> 
>     card = kzalloc(sizeof(struct mmc_card), GFP_KERNEL);
>     if (!card)
>         return ERR_PTR(-ENOMEM);
> 
>     card->host = host;
> 
>     device_initialize(&card->dev);
> 
>     card->dev.parent = mmc_classdev(host);
>     card->dev.bus = &mmc_bus_type;
>     card->dev.release = mmc_release_card;
>     card->dev.type = type;
> 
>     return card;
> }
> 
> 
> Thanks,
> Zhonghui
> 


  reply	other threads:[~2014-07-02  2:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01  5:39 one doubt about mmc_sdio_init_card function Fu, Zhonghui
2014-07-02  2:52 ` Aaron Lu [this message]
2014-07-03 15:47 ` One bug of SDHCI driver Fu, Zhonghui
2014-07-04  2:40   ` Jaehoon Chung
2014-07-06 15:19     ` Fu, Zhonghui
2014-07-08 16:03       ` Fu, Zhonghui
2014-07-14 13:26         ` Chris Ball
2014-07-15  2:54           ` Fu, Zhonghui
2014-07-15  4:14             ` Jaehoon Chung
2014-07-15  4:40               ` Jaehoon Chung
2014-07-20 14:51                 ` Fu, Zhonghui
2014-07-24 15:27                   ` Fu, Zhonghui
     [not found]                     ` <53D85CBF.3070409@linux.intel.com>
2014-07-30  3:40                       ` Jaehoon Chung
2014-08-05  4:56                         ` Fu, Zhonghui
2014-08-07  6:58                           ` Fu, Zhonghui
2014-08-11  5:53                             ` Fu, Zhonghui

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=53B373D2.7000306@intel.com \
    --to=aaron.lu@intel.com \
    --cc=chris@printf.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jackey.shen@amd.com \
    --cc=jh80.chung@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=tgih.jun@samsung.com \
    --cc=ulf.hansson@linaro.org \
    --cc=zhonghui.fu@linux.intel.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;
as well as URLs for NNTP newsgroup(s).