From: Linus Walleij <linus.walleij@linaro.org>
To: Richard Leitner <richard.leitner@skidata.com>
Cc: "Luca Porzio (lporzio)" <lporzio@micron.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Bart Van Assche <bart.vanassche@sandisk.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Shawn Lin <shawn.lin@rock-chips.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Richard Leitner <dev@g0hl1n.net>
Subject: Re: [EXT] Re: [PATCH v2] mmc: core: add mmc-card hardware reset enable support
Date: Tue, 20 Jun 2017 18:10:53 +0200 [thread overview]
Message-ID: <CACRpkdak6ffeN0D4eTJV3cUeJ+T92rg9Pt6AnFMW=VzQ=59XVw@mail.gmail.com> (raw)
In-Reply-To: <dd844df4-ac50-daab-bc31-a636718227f5@skidata.com>
On Tue, Jun 20, 2017 at 12:24 PM, Richard Leitner
<richard.leitner@skidata.com> wrote:
> Should we then add a warning/info message to the kernel if we have a
> reset gpio configured in the DT, but the eMMC hasn't this OTP bit set?
That makes a lot of sense. Because the situation is ambigous.
We provide the hardware to reset the card, but the card says it
does not accept a reset.
Yours,
Linus Walleij
prev parent reply other threads:[~2017-06-20 16:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 7:31 [PATCH v2] mmc: core: add mmc-card hardware reset enable support Richard Leitner
2017-04-11 8:17 ` Linus Walleij
2017-04-11 10:43 ` Ulf Hansson
2017-06-14 7:25 ` Richard Leitner
2017-06-14 16:12 ` [EXT] " Luca Porzio (lporzio)
2017-06-20 9:45 ` Linus Walleij
2017-06-20 10:24 ` Richard Leitner
2017-06-20 16:10 ` Linus Walleij [this message]
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='CACRpkdak6ffeN0D4eTJV3cUeJ+T92rg9Pt6AnFMW=VzQ=59XVw@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=adrian.hunter@intel.com \
--cc=bart.vanassche@sandisk.com \
--cc=dev@g0hl1n.net \
--cc=devicetree@vger.kernel.org \
--cc=jh80.chung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=lporzio@micron.com \
--cc=mark.rutland@arm.com \
--cc=richard.leitner@skidata.com \
--cc=robh+dt@kernel.org \
--cc=shawn.lin@rock-chips.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).