From: Vincent Yang <vincent.yang.fujitsu@gmail.com>
To: chris@printf.net, linux-mmc@vger.kernel.org
Cc: devicetree@vger.kernel.org, anton@enomsg.org,
linuxppc-dev@lists.ozlabs.org, patches@linaro.org,
andy.green@linaro.org, jaswinder.singh@linaro.org,
Vincent.Yang@tw.fujitsu.com
Subject: [RFC PATCH v2 0/6] mmc: sdhci: adding support for a new Fujitsu sdhci IP
Date: Thu, 26 Jun 2014 14:23:26 +0800 [thread overview]
Message-ID: <1403763812-5495-1-git-send-email-Vincent.Yang@tw.fujitsu.com> (raw)
Hi,
We are adding support for a new Fujitsu sdhci IP.
These patches are against v3.16-rc1 mainline since nothing in
mmc-next at this moment.
These patches are tested on 3.16-rc1 integration tree.
We welcome any comment and advice about how to make any
improvements or better align them with upstream.
Changes from v1:
- Add sufficient description in DT binding ducument
- Remove one patch "mmc: sdhci: add quirk for broken 3.0V support" and use
voltage-ranges = <> in the device tree instead
Thanks a lot!
Best regards,
Vincent Yang
Vincent Yang (6):
mmc: sdhci: add quirk for voltage switch callback
mmc: sdhci: add quirk for tuning work around
mmc: sdhci: add quirk for single block transactions
mmc: sdhci: host: add new f_sdh30
mmc: core: hold SD Clock before CMD11 during Signal Voltage Switch
Procedure
mmc: core: add manual resume capability
.../devicetree/bindings/mmc/sdhci-fujitsu.txt | 35 ++
drivers/mmc/core/core.c | 8 +-
drivers/mmc/core/sd.c | 4 +
drivers/mmc/host/Kconfig | 7 +
drivers/mmc/host/Makefile | 1 +
drivers/mmc/host/sdhci.c | 15 +-
drivers/mmc/host/sdhci.h | 1 +
drivers/mmc/host/sdhci_f_sdh30.c | 435 +++++++++++++++++++++
drivers/mmc/host/sdhci_f_sdh30.h | 40 ++
include/linux/mmc/host.h | 14 +
include/linux/mmc/sdhci.h | 6 +
11 files changed, 561 insertions(+), 5 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mmc/sdhci-fujitsu.txt
create mode 100644 drivers/mmc/host/sdhci_f_sdh30.c
create mode 100644 drivers/mmc/host/sdhci_f_sdh30.h
--
1.9.0
next reply other threads:[~2014-06-26 6:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 6:23 Vincent Yang [this message]
2014-06-26 6:23 ` [RFC PATCH v2 1/6] mmc: sdhci: add quirk for voltage switch callback Vincent Yang
2014-06-26 6:23 ` [RFC PATCH v2 2/6] mmc: sdhci: add quirk for tuning work around Vincent Yang
2014-06-26 6:23 ` [RFC PATCH v2 3/6] mmc: sdhci: add quirk for single block transactions Vincent Yang
2014-06-26 6:23 ` [RFC PATCH v2 4/6] mmc: sdhci: host: add new f_sdh30 Vincent Yang
2014-06-26 11:03 ` Mark Rutland
2014-06-27 3:32 ` Vincent Yang
2014-06-27 10:12 ` Mark Rutland
2014-06-30 2:10 ` Vincent Yang
2014-06-26 6:23 ` [RFC PATCH v2 5/6] mmc: core: hold SD Clock before CMD11 during Signal Voltage Switch Procedure Vincent Yang
2014-06-26 6:23 ` [RFC PATCH v2 6/6] mmc: core: add manual resume capability Vincent Yang
2014-06-26 9:42 ` Ulf Hansson
2014-06-27 2:23 ` Vincent Yang
2014-06-27 9:40 ` Ulf Hansson
2014-06-27 11:00 ` Vincent Yang
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=1403763812-5495-1-git-send-email-Vincent.Yang@tw.fujitsu.com \
--to=vincent.yang.fujitsu@gmail.com \
--cc=Vincent.Yang@tw.fujitsu.com \
--cc=andy.green@linaro.org \
--cc=anton@enomsg.org \
--cc=chris@printf.net \
--cc=devicetree@vger.kernel.org \
--cc=jaswinder.singh@linaro.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=patches@linaro.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