From: Helmut Grohne <h.grohne@intenta.de>
To: "Adrian Hunter" <adrian.hunter@intel.com>,
"Michal Simek" <michal.simek@xilinx.com>,
"Sören Brinkmann" <soren.brinkmann@xilinx.com>,
"Ulf Hansson" <ulf.hansson@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
linux-mmc@vger.kernel.org, devicetree@vger.kernel.org
Cc: Atul Garg <agarg@arasan.com>, linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] mmc: sdhci-of-arasan: workaround for broken clocks
Date: Wed, 20 Jun 2018 13:32:41 +0200 [thread overview]
Message-ID: <cover.1529493667.git.h.grohne@intenta.de> (raw)
In-Reply-To: <20180615081830.zrgx6arwn6ga27gu@laureti-dev>
This patch series works around the internal clock indicating stability too
quickly to operate. It manifests itself as:
mmc0: error -84 whilst initialising SD card
Changes since v2:
* Ulf Hansson requested splitting the patch in accordance with
Documentation/devicetree/bindings/submitting-patches.txt. Also update
recipient list accordingly.
* Added Acked-by from Adrian Hunter.
Helmut Grohne (2):
dt-bindings: mmc: broken clock stable indicator on arasan controllers
mmc: sdhci-of-arasan: Add quirk for unstable clocks
Documentation/devicetree/bindings/mmc/arasan,sdhci.txt | 2 ++
drivers/mmc/host/sdhci-of-arasan.c | 16 ++++++++++++++++
2 files changed, 18 insertions(+)
--
2.11.0
next parent reply other threads:[~2018-06-20 11:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180615081830.zrgx6arwn6ga27gu@laureti-dev>
2018-06-20 11:32 ` Helmut Grohne [this message]
2018-06-20 11:32 ` [PATCH v3 1/2] dt-bindings: mmc: broken clock stable indicator on arasan controllers Helmut Grohne
2018-06-20 19:08 ` Rob Herring
2018-06-20 11:33 ` [PATCH v3 2/2] mmc: sdhci-of-arasan: Add quirk for unstable clocks Helmut Grohne
2018-07-02 13:17 ` [PATCH v3 0/2] mmc: sdhci-of-arasan: workaround for broken clocks 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=cover.1529493667.git.h.grohne@intenta.de \
--to=h.grohne@intenta.de \
--cc=adrian.hunter@intel.com \
--cc=agarg@arasan.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=soren.brinkmann@xilinx.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).