From: "Christian Löhle" <CLoehle@hyperstone.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ulf Hansson <ulf.hansson@linaro.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Ricky WU <ricky_wu@realtek.com>
Subject: Re: [PATCH] mmc: rtsx: add 74 Clocks in power on flow
Date: Tue, 10 May 2022 13:02:24 +0000 [thread overview]
Message-ID: <939808fa84904f72a54d427ca4592486@hyperstone.com> (raw)
In-Reply-To: <d569393619d54d8789a223a9db6d455e@hyperstone.com>
>commit 1f311c94aabd ("mmc: rtsx: add 74 Clocks in power on flow") upstream.
>backport note: removed unavailable power_delay_ms 5ms as 10ms is fine, too.
>
>SD spec definition:
>"Host provides at least 74 Clocks before issuing first command"
>After 1ms for the voltage stable then start issuing the Clock signals
>
>if POWER STATE is
>MMC_POWER_OFF to MMC_POWER_UP to issue Clock signal to card
>MMC_POWER_UP to MMC_POWER_ON to stop issuing signal to card
>
>Signed-off-by: Ricky Wu <ricky_wu@realtek.com>
>Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
>Signed-off-by: Christian Loehle <cloehle@hyperstone.com>
>---
Now for 4.9.y and 4.14.y, my bad and thanks a lot.
Regards,
Christian=
Hyperstone GmbH | Reichenaustr. 39a | 78467 Konstanz
Managing Director: Dr. Jan Peter Berns.
Commercial register of local courts: Freiburg HRB381782
next prev parent reply other threads:[~2022-05-10 13:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 13:00 [PATCH] mmc: rtsx: add 74 Clocks in power on flow Christian Löhle
2022-05-10 13:02 ` Christian Löhle [this message]
2022-05-13 7:54 ` Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2022-05-10 12:08 Christian Löhle
2022-05-10 12:09 ` Christian Löhle
2022-05-10 12:40 ` Greg Kroah-Hartman
[not found] <fb7cda69c5c244dfa579229ee2f0da83@realtek.com>
[not found] ` <CAPDyKFrYWgCbwk6-hNZjtx4mdn7Sx1NJLie+f8wEjS==_HXR5Q@mail.gmail.com>
2022-05-09 9:35 ` Christian Löhle
2022-05-09 9:47 ` gregkh
2022-05-09 10:12 ` Christian Löhle
2022-05-10 9:56 ` Ulf Hansson
2022-05-10 10:21 ` gregkh
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=939808fa84904f72a54d427ca4592486@hyperstone.com \
--to=cloehle@hyperstone.com \
--cc=gregkh@linuxfoundation.org \
--cc=ricky_wu@realtek.com \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).