From: dahuang@nvidia.com (Danny Huang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: tegra: fuse: add fuctions to read speedo id and process id
Date: Wed, 20 Mar 2013 10:20:03 +0800 [thread overview]
Message-ID: <1363746003.3573.80.camel@dahuang-vm> (raw)
In-Reply-To: <514915DB.8060206@wwwdotorg.org>
On Wed, 2013-03-20 at 09:50 +0800, Stephen Warren wrote:
> On 03/19/2013 07:39 PM, Danny Huang wrote:
> > On Wed, 2013-03-20 at 02:05 +0800, Stephen Warren wrote:
> >> On 03/18/2013 08:33 PM, Danny Huang wrote:
> >>> Add functions to read the speedo and process id of both cpu and soc.
> >>> There might be some drivers need the information as well.
> >>
> >> What code wants to use these functions? It'd be best to submit this
> >> patch with that code, so that something actually uses the functions, and
> >> they don't look like dead code.
> >
> > There are some developing drivers that are located in drivers folder
> > needs those information.
>
> Which drivers?
Per my understanding, there is a dvfs development that is trying to use
the devfreq framework.
>
> > I think that they can't include a header file in mach-tegra folder
>
> True.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-03-20 2:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 2:33 [PATCH] ARM: tegra: fuse: add fuctions to read speedo id and process id Danny Huang
2013-03-19 18:05 ` Stephen Warren
2013-03-20 1:39 ` Danny Huang
2013-03-20 1:50 ` Stephen Warren
2013-03-20 2:20 ` Danny Huang [this message]
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=1363746003.3573.80.camel@dahuang-vm \
--to=dahuang@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.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).