From: Scott Wood <scottwood@freescale.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Yangbo Lu <yangbo.lu@freescale.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
linux-mmc <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH 3/3] mmc: sdhci-of-esdhc: add workaround for T4240 incorrect HOSTVER value
Date: Fri, 24 Jul 2015 21:27:22 -0500 [thread overview]
Message-ID: <1437791242.2993.268.camel@freescale.com> (raw)
In-Reply-To: <CAPDyKFpf6Ayw28dmbHhLJ8HSOSie60sUjaAnK7qqONHsRN4BDA@mail.gmail.com>
On Tue, 2015-07-21 at 15:02 +0200, Ulf Hansson wrote:
> On 21 July 2015 at 11:45, Yangbo Lu <yangbo.lu@freescale.com> wrote:
> > For T4240-R1.0-R2.0, the HOSTVER register has incorrcet vender
> > version value and sdhc spec version value. This will break down
> > the ADMA data transfer. So add workaround to get right value
> > VVN=0x13, SVN = 0x1.
>
> So T4240-R1.0-R2.0 is the version of the controller, right?
>
> If I understand correct you are checking what CPU/SoC you are running
> on, to figure out which controller version you are using, as that
> can't be fetched (trusted) from the registers of the esdhc controller
> itself!?
>
> Instead, you could deal with this directly in the DTS files. I assume
> you have some DTS file for each SoC/board variant, right?
No, we do not have a separate DTS file for each revision of an SoC -- and if
we did, we'd constantly have people using the wrong one.
> In principle, in your DTS file specific for the board/SoC that holds
> the T4240-R1.0-R2.0 version of the controller, should add a specific
> esdhc DT property to indicate this errata.
No, because (in addition to the above issue about chip revisions) the device
tree is stable ABI and errata are often discovered after device trees are
deployed.
-Scott
next prev parent reply other threads:[~2015-07-25 2:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 9:45 [PATCH 3/3] mmc: sdhci-of-esdhc: add workaround for T4240 incorrect HOSTVER value Yangbo Lu
2015-07-21 13:02 ` Ulf Hansson
2015-07-25 2:27 ` Scott Wood [this message]
2015-07-27 7:58 ` Ulf Hansson
2015-07-27 15:57 ` Scott Wood
2015-08-25 12:04 ` Ulf Hansson
2015-08-26 7:49 ` Lu Y.B.
2015-08-26 14:16 ` Scott Wood
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=1437791242.2993.268.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ulf.hansson@linaro.org \
--cc=yangbo.lu@freescale.com \
/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).