From: Faiz Abbas <faiz_abbas@ti.com>
To: <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-mmc@vger.kernel.org>
Cc: mark.rutland@arm.com, ulf.hansson@linaro.org,
adrian.hunter@intel.com, kishon@ti.com, robh+dt@kernel.org,
faiz_abbas@ti.com, michal.simek@xilinx.com
Subject: [PATCH v3 0/3] Add driver Support for MMCSD on AM654x
Date: Tue, 11 Dec 2018 00:05:04 +0530 [thread overview]
Message-ID: <20181210183507.9617-1-faiz_abbas@ti.com> (raw)
The following patches add driver support for MMCSD on TI's AM654
platforms.
Previously I had added the support to sdhci-of-arasan driver with
a separate phy driver[1]. Since then it has turned out that tuning
operation (for HS200, HS400 and SDR104 speed modes) will require
configuration of phy registers. This completely breaks the model of
the sdhci-of-arasan driver which relies on a separate driver to
configure the phy register space.
Because of this, I am creating a new driver with both the sdhci and
phy register spaces. This helps me use the phy registers in a future
patch that adds tuning support.
DT patches will be posted in a separate series.
Changes in v3:
1. Removed reference to clk_ahb as its not being used.
2. Added comment for pm_runtime being used for enabling
clocks.
Changes in v2:
1. Reset OTAP delay back to default value in init.
2. Improved patch description for patch 2.
3. Minor style fixes.
[1] driver and phy patches posted before
https://patchwork.kernel.org/project/linux-mmc/list/?series=26623
Faiz Abbas (3):
dt-bindings: mmc: sdhci-am654: Document bindings for the host
controllers on TI's AM654 SOCs
dt-bindings: mmc: sdhci-of-arasan: Add deprecated message for am65
mmc: sdhci_am654: Add Initial Support for AM654 SDHCI driver
.../devicetree/bindings/mmc/arasan,sdhci.txt | 4 +
.../devicetree/bindings/mmc/sdhci-am654.txt | 37 ++
drivers/mmc/host/Kconfig | 12 +
drivers/mmc/host/Makefile | 1 +
drivers/mmc/host/sdhci-of-arasan.c | 46 ---
drivers/mmc/host/sdhci_am654.c | 374 ++++++++++++++++++
6 files changed, 428 insertions(+), 46 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mmc/sdhci-am654.txt
create mode 100644 drivers/mmc/host/sdhci_am654.c
--
2.19.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2018-12-10 18:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 18:35 Faiz Abbas [this message]
2018-12-10 18:35 ` [PATCH v3 1/3] dt-bindings: mmc: sdhci-am654: Document bindings for the host controllers on TI's AM654 SOCs Faiz Abbas
2018-12-10 18:35 ` [PATCH v3 2/3] dt-bindings: mmc: sdhci-of-arasan: Add deprecated message for AM65 Faiz Abbas
2018-12-10 18:35 ` [PATCH v3 3/3] mmc: sdhci_am654: Add Initial Support for AM654 SDHCI driver Faiz Abbas
2018-12-11 7:46 ` Adrian Hunter
2018-12-17 8:15 ` [PATCH v3 0/3] Add driver Support for MMCSD on AM654x Faiz Abbas
2018-12-17 8:24 ` Sekhar Nori
2018-12-17 8:26 ` Ulf Hansson
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=20181210183507.9617-1-faiz_abbas@ti.com \
--to=faiz_abbas@ti.com \
--cc=adrian.hunter@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=robh+dt@kernel.org \
--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