From: zhangfei gao <zhangfei.gao@gmail.com>
To: Chris Ball <cjb@laptop.org>,
linux-mmc@vger.kernel.org, Jun Nie <njun@marvell.com>,
Raymond Wu <xywu@marvell.com>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Philip Rakity <prakity@ma>
Subject: [PATCH v2 0/2] add call backs in sdhci-pxa.c
Date: Wed, 18 May 2011 04:40:40 -0400 [thread overview]
Message-ID: <BANLkTimwFxEdS6H+UvJAYoafyGe1g2eHGw@mail.gmail.com> (raw)
v2, sync to mmc-next
patch 1: move sdhci_priv and sdhci_ops definition to
include/linux/mmc/sdhci.h from drivers/mmc/host/sdhci.h
1. platfrom could directly overwrite sdhci_ops with soc specific ops,
this case occurs at different controller share the same driver, while
different ops they may use, so move sdhci_ops definition to include
2. platform code will use sdhci_priv to access host->private
Patch 2: Introduce several call backs.
pxa955 may require external gpio to detect card insert and remove.
soc_set_ops is used to overwrite host ops directly from platfrom ops.
reply other threads:[~2011-05-18 8:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=BANLkTimwFxEdS6H+UvJAYoafyGe1g2eHGw@mail.gmail.com \
--to=zhangfei.gao@gmail.com \
--cc=cjb@laptop.org \
--cc=haojian.zhuang@gmail.com \
--cc=linux-mmc@vger.kernel.org \
--cc=njun@marvell.com \
--cc=prakity@ma \
--cc=xywu@marvell.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).