devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Takao Orito <orito.takao@socionext.com>
To: ulf.hansson@linaro.org, robh+dt@kernel.org, mark.rutland@arm.com
Cc: linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, masami.hiramatsu@linaro.org,
	jaswinder.singh@linaro.org, sugaya.taichi@socionext.com,
	kasai.kazuhiro@socionext.com, kanematsu.shinji@socionext.com,
	orito.takao@socionext.com
Subject: [PATCH v1 0/2] mmc: sdhci_f_sdh30: Add support for Milbeaut
Date: Tue, 26 Mar 2019 14:53:29 +0900	[thread overview]
Message-ID: <1553579609-6100-1-git-send-email-orito.takao@socionext.com> (raw)

The following patches add driver support for SD Host controller on
Socionext's Milbeaut M10V platforms.

SD Host controller on Milbeaut is consist of two controller parts.
One is core controller F_SDH30, this is similar to sdhci-fujitsu
controller.
Another is bridge controller. This bridge controller is not compatible
with sdhci-fujitsu controller. This is special for Milbeaut series.

It has the several parts,
 - reset control
 - clock enable / select for SDR50/25/12
 - hold control of DATA/CMD line
 - select characteristics for WP/CD/LED line
 - Re-tuning control for mode3
 - Capability setting
   Timeout Clock / Base Clock / Timer Count for Re-Tuning /
   Debounce period
These requires special procedures at reset or clock enable/change or
 further tuning of clock.

Takao Orito (2):
  dt-bindings: mmc: sdhci-fujitsu.txt: add miilbeaut driver
  mmc: sdhci_f_sdh30: Add support for Milbeaut M10V host controller

 .../devicetree/bindings/mmc/sdhci-fujitsu.txt      |  22 +-
 drivers/mmc/host/sdhci_f_sdh30.c                   | 324 +++++++++++++++++++--
 2 files changed, 315 insertions(+), 31 deletions(-)

-- 
1.9.1

                 reply	other threads:[~2019-03-26  5:53 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=1553579609-6100-1-git-send-email-orito.takao@socionext.com \
    --to=orito.takao@socionext.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jaswinder.singh@linaro.org \
    --cc=kanematsu.shinji@socionext.com \
    --cc=kasai.kazuhiro@socionext.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=masami.hiramatsu@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=sugaya.taichi@socionext.com \
    --cc=ulf.hansson@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;
as well as URLs for NNTP newsgroup(s).