From: Jordan Crouse <jcrouse@codeaurora.org>
To: Rob Clark <robdclark@gmail.com>, Mark Rutland <mark.rutland@arm.com>
Cc: "linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [RFC] drm/msm: DT support for 8960/8064
Date: Wed, 02 Jul 2014 15:09:39 -0600 [thread overview]
Message-ID: <53B47513.2040704@codeaurora.org> (raw)
In-Reply-To: <CAF6AEGuK-_frg5ErRNXGpqHfXv85E_6-_iKHWuHyz5g6udVt8Q@mail.gmail.com>
On 07/02/2014 03:01 PM, Rob Clark wrote:
> As far as I can tell from diving downstream android kgsl code, seems
> like some a2xx you might be able to read the value from hw. Beyond
> that I'm not entirely sure. (Remember, no docs.)
Ohhh! I get to tell a story!
The on chip registers have a long and consistent history of being wrong.
And not just the spin ID being wrong - the major and minor have had their
issues too. It got to the point that sometime around the A320 timeframe
we put our foot down and decided that we would never again rely on the
hardware. The reasoning is that the SoC and the GPU are on the same die
so we can use the one to identify the other. And thats what we've done
since then - first in the board files and now in the DT.
So long story short - the registers are there, we don't trust them as
far as we could throw them. Use the SoC instead.
Jordan
--
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-07-02 21:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 18:57 [RFC] drm/msm: DT support for 8960/8064 Rob Clark
2014-07-02 14:26 ` Jordan Crouse
2014-07-02 14:42 ` Rob Clark
2014-07-02 16:42 ` Jordan Crouse
2014-07-02 17:12 ` Olof Johansson
2014-07-02 20:41 ` Rob Clark
2014-07-02 18:09 ` Mark Rutland
2014-07-02 21:01 ` Rob Clark
2014-07-02 21:09 ` Jordan Crouse [this message]
2014-07-03 9:15 ` Mark Rutland
2014-07-03 11:13 ` Rob Clark
2014-07-03 16:36 ` sviau
2014-07-03 18:14 ` Rob Clark
2014-07-08 16:00 ` [RFCv2] " Rob Clark
2014-07-17 8:10 ` divya ojha
2014-07-17 15:29 ` Rob Clark
2014-07-17 16:08 ` Bjorn Andersson
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=53B47513.2040704@codeaurora.org \
--to=jcrouse@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robdclark@gmail.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).