linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: "Luca Porzio (lporzio)" <lporzio@micron.com>
Cc: Richard Leitner <richard.leitner@skidata.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 11:45:16 +0200	[thread overview]
Message-ID: <CACRpkdb92scfO=tghucfC3RqQpi9K6YSuavte_b-AxH4hS87rQ@mail.gmail.com> (raw)
In-Reply-To: <6b92d0af00024549a0d22dda039780dd@bowex36d.micron.com>

Hi Luca,

thanks for joining!

On Wed, Jun 14, 2017 at 6:12 PM, Luca Porzio (lporzio)
<lporzio@micron.com> wrote:

> This behavior is not Micron specific but instead it is enforced by the Jedec
> Specification. All eMMC must have HW reset disabled by default.

That's very good to know.

> This specification (as Ulf correctly hinted) originated from badly connected
> HW Reset pins which caused unnecessary eMMC reset glitches.
> Disabling this feature is a good option to contain glitches and avoid
> system level bugs.

Ah, makes sense.

> IMHO mmc-util is where the patch really stands: the enabling is OTP,
> the programmer have to use mmc-util only once and the kernel
> will behave accordingly.

So we should not add it to the device tree.

> Any platform vendor must check that the HW Reset pin is actually
> Connected BEFORE enabling this feature otherwise the system may be
> unstable. A DT Binding may be dangerous if this condition is not met
> as well as the code execution at each MMC init is honestly redundant
> for an OTP location of the extCSD.

I agree. So the device should be configured during production, or
a user who know exactly what they are doing may reconfigure it
using the mmc-utils.

Thus the kernel should just read what the device says and stay with
that, no DT props or anything.

This makes a lot of sense.

When say ethernet devices need MAC addresses written to their OTP
we do not put that into the device tree to be programmed either, we assume
production tools to do that job.

Yours,
Linus Walleij

  reply	other threads:[~2017-06-20  9:45 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 [this message]
2017-06-20 10:24           ` Richard Leitner
2017-06-20 16:10             ` Linus Walleij

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='CACRpkdb92scfO=tghucfC3RqQpi9K6YSuavte_b-AxH4hS87rQ@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).