From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Marcel Ziswiler <marcel-mitwqZ+T+m9Wk0Htik3J/w@public.gmane.org>,
Peter De Schrijver
<pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Thierry Reding
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: Tegra30: Unknown SKU 177
Date: Tue, 08 Apr 2014 09:25:38 -0600 [thread overview]
Message-ID: <534414F2.8080407@wwwdotorg.org> (raw)
In-Reply-To: <534403CD.8010303-mitwqZ+T+m9Wk0Htik3J/w@public.gmane.org>
On 04/08/2014 08:12 AM, Marcel Ziswiler wrote:
> Hi there
>
> Looks like the latest T30MQS-P-A3 embedded SKUs that can e.g. be found
> on Toradex Colibri T30 V1.1D modules are not yet recognised by the
> mainline speedo driver:
>
> [ 0.000000] Tegra30: Unknown SKU 177
> [ 0.000000] fuse_speedo_calib: ATE prog ver 4.0
> [ 0.000000] Tegra30: CPU Speedo ID 0, Soc Speedo ID 0
> [ 0.000000] Tegra Revision: A03 SKU: 177 CPU Process: 2 Core Process: 0
>
> Does this have any adverse effects?
No.
NVIDIA's downstream kernels use SKU (along with other) information to
determine clock/voltage limits, etc. However, we don't have any DVFS
code or aggressive clock settings in mainline at present, so unknown
SKUS won't be a problem. The same goes for mainline U-Boot.
Still, it would be nice to squash the warning for you.
Peter, any chance you could look up the appropriate speedo IDs and fill
in a case for this SKU in tegra30_speedo.c? Is it possible to fill in
all known SKUs?
next prev parent reply other threads:[~2014-04-08 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 14:12 Tegra30: Unknown SKU 177 Marcel Ziswiler
[not found] ` <534403CD.8010303-mitwqZ+T+m9Wk0Htik3J/w@public.gmane.org>
2014-04-08 15:25 ` Stephen Warren [this message]
[not found] ` <534414F2.8080407-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-06-25 14:47 ` Marcel Ziswiler
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=534414F2.8080407@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=marcel-mitwqZ+T+m9Wk0Htik3J/w@public.gmane.org \
--cc=pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.