From: Peter Zijlstra <peterz@infradead.org>
To: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
mahesh.kumar.p@intel.com, tglx@linutronix.de,
rafael.j.wysocki@intel.com, andriy.shevchenko@linux.intel.com,
hpa@zytor.com, mingo@kernel.org, aubrey.li@linux.intel.com
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/platform] x86/platform/intel/pmc_atom: Add Cherrytrail PMC interface
Date: Mon, 6 Jul 2015 21:09:17 +0200 [thread overview]
Message-ID: <20150706190917.GK3644@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <tip-daf61e1b7fc31d553fe3bf2dead95d9404ad0f57@git.kernel.org>
On Mon, Jul 06, 2015 at 09:35:33AM -0700, tip-bot for Kumar P Mahesh wrote:
> Commit-ID: daf61e1b7fc31d553fe3bf2dead95d9404ad0f57
> Gitweb: http://git.kernel.org/tip/daf61e1b7fc31d553fe3bf2dead95d9404ad0f57
> Author: Kumar P Mahesh <mahesh.kumar.p@intel.com>
> AuthorDate: Mon, 6 Jul 2015 17:29:03 +0300
> Committer: Ingo Molnar <mingo@kernel.org>
> CommitDate: Mon, 6 Jul 2015 17:50:59 +0200
>
> x86/platform/intel/pmc_atom: Add Cherrytrail PMC interface
>
> The patch adds CHT PMC interface. This exposes all the South IP
> device power states and S0ix states for CHT. The bit map of
> FUNC_DIS and D3_STS_0 registers for SoCs are consistent. The
> D3_STS_1 and FUNC_DIS_2 registers, however, are not aligned.
> This is fixed by splitting a common mapping on per register basis.
TLA collision.. I thought this was about performance monitor counters :/
next prev parent reply other threads:[~2015-07-06 19:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 14:28 [PATCH v3 0/5] x86: pmc_atom: Add Cherrytrail support Andy Shevchenko
2015-07-06 14:29 ` [PATCH v3 1/5] x86: pmc_atom: export accessors to PMC registers Andy Shevchenko
2015-07-06 16:34 ` [tip:x86/platform] x86/platform/intel/pmc_atom: Export " tip-bot for Andy Shevchenko
2015-07-06 14:29 ` [PATCH v3 2/5] x86: pmc_atom: print index of device in loop Andy Shevchenko
2015-07-06 16:34 ` [tip:x86/platform] x86/platform/intel/pmc_atom: Print " tip-bot for Andy Shevchenko
2015-07-06 14:29 ` [PATCH v3 3/5] x86: pmc_atom: supply register mappings via pmc object Andy Shevchenko
2015-07-06 16:35 ` [tip:x86/platform] x86/platform/intel/pmc_atom: Supply register mappings via PMC object tip-bot for Andy Shevchenko
2015-07-06 14:29 ` [PATCH v3 4/5] x86: pmc_atom: Add Cherrytrail PMC interface Andy Shevchenko
2015-07-06 15:44 ` Ingo Molnar
2015-07-06 15:47 ` Thomas Gleixner
2015-07-06 15:50 ` Ingo Molnar
2015-07-06 16:37 ` Andy Shevchenko
2015-07-06 16:39 ` Ingo Molnar
2015-07-06 16:35 ` [tip:x86/platform] x86/platform/intel/pmc_atom: " tip-bot for Kumar P Mahesh
2015-07-06 19:09 ` Peter Zijlstra [this message]
2015-07-07 6:55 ` Ingo Molnar
2015-07-06 16:51 ` tip-bot for Andy Shevchenko
2015-07-06 14:29 ` [PATCH v3 5/5] x86: pmc_atom: place it under arch/x86/platform/atom Andy Shevchenko
2015-07-06 16:35 ` [tip:x86/platform] x86/platform/intel/pmc_atom: Move the PMC-Atom code to arch/x86/platform/atom tip-bot for Andy Shevchenko
2015-07-06 16:51 ` tip-bot for Andy Shevchenko
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=20150706190917.GK3644@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=aubrey.li@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mahesh.kumar.p@intel.com \
--cc=mingo@kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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