From: Alexandre Courbot <gnurou@gmail.com>
To: Vince Hsu <vinceh@nvidia.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
Thierry Reding <thierry.reding@gmail.com>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
Ben Skeggs <bskeggs@redhat.com>,
Martin Peres <martin.peres@free.fr>,
"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND V2 PATCH 1/3] soc/tegra: fuse: export tegra_sku_info for module use
Date: Sat, 29 Nov 2014 16:30:28 +0900 [thread overview]
Message-ID: <CAAVeFuLfqhN87fOxc9sd09rzd4jSLkLs21ZGS1aV8NTo_uwpkQ@mail.gmail.com> (raw)
In-Reply-To: <1417173180-21726-1-git-send-email-vinceh@nvidia.com>
On Fri, Nov 28, 2014 at 8:12 PM, Vince Hsu <vinceh@nvidia.com> wrote:
> Some Tegra drivers might be complied as kernel modules, and
> they need the fuse information for initialization. One
> example is the GK20A Nouveau driver. It needs the GPU speedo
> value to calculate frequency-voltage table. So export
> the tegra_sku_info.
Acked-by: Alexandre Courbot <acourbot@nvidia.com>
This is required for setting the optimal GPU voltage in Nouveau.
next prev parent reply other threads:[~2014-11-29 7:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 11:12 [RESEND V2 PATCH 1/3] soc/tegra: fuse: export tegra_sku_info for module use Vince Hsu
2014-11-28 11:12 ` [RESEND PATCH nouveau 2/3] volt: allow non-bios voltage scaling Vince Hsu
2014-11-29 8:22 ` Alexandre Courbot
2014-12-01 22:57 ` Martin Peres
2014-11-28 11:13 ` [RESEND PATCH nouveau 3/3] volt: add support for GK20A Vince Hsu
2014-12-01 23:00 ` Martin Peres
2014-12-01 23:18 ` [Nouveau] " Ben Skeggs
2014-11-29 7:30 ` Alexandre Courbot [this message]
2014-12-01 10:01 ` [RESEND V2 PATCH 1/3] soc/tegra: fuse: export tegra_sku_info for module use Thierry Reding
2014-12-01 22:23 ` [Nouveau] " Ben Skeggs
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=CAAVeFuLfqhN87fOxc9sd09rzd4jSLkLs21ZGS1aV8NTo_uwpkQ@mail.gmail.com \
--to=gnurou@gmail.com \
--cc=bskeggs@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=martin.peres@free.fr \
--cc=nouveau@lists.freedesktop.org \
--cc=pdeschrijver@nvidia.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
--cc=vinceh@nvidia.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).