[PATCH] x86/cpu: Add new Airmont variant to Intel family

From: "Luck, Tony" <tony.luck@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Rahul Tanwar <rahul.tanwar@linux.intel.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"bp@alien8.de" <bp@alien8.de>, "hpa@zytor.com" <hpa@zytor.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"Shevchenko, Andriy" <andriy.shevchenko@intel.com>,
	"alan@linux.intel.com" <alan@linux.intel.com>,
	"ricardo.neri-calderon@linux.intel.com" 
	<ricardo.neri-calderon@linux.intel.com>,
	"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Wu, Qiming" <qi-ming.wu@intel.com>,
	"Kim, Cheol Yong" <cheol.yong.kim@intel.com>,
	"Tanwar, Rahul" <rahul.tanwar@intel.com>
Subject: [PATCH] x86/cpu: Add new Airmont variant to Intel family
Date: Thu, 22 Aug 2019 13:35:44 -0700	[thread overview]
Message-ID: <20190822203544.GA10229@agluck-desk2.amr.corp.intel.com> (raw)
In-Reply-To: <20190822185347.GA8933@agluck-desk2.amr.corp.intel.com>

On Thu, Aug 22, 2019 at 11:53:47AM -0700, Luck, Tony wrote:
> On Thu, Aug 22, 2019 at 12:29:55PM +0200, Peter Zijlstra wrote:
> > On Wed, Aug 21, 2019 at 01:18:46PM -0700, Luck, Tony wrote:
> > > On Tue, Aug 20, 2019 at 04:57:35PM +0200, Peter Zijlstra wrote:
> > 
> > > As I mentioned above, there are some folks internally that think
> > > NP == Network Processor is too narrow a pigeonhole for this CPU.
> > > 
> > > But _NPAOS (Network Processor And Other Stuff) doesn't sound helpful.
> > 
> > So what is 'other stuff'; is there really no general term that describes
> > well what's been done to this SoC; or is it secret and we're in a catch
> > 22 here?
> 
> Since CPU model number is one of the early bits of disclosure
> in order to get support upstream in time for launch, safe to
> assume that some products will not want to advertise everything
> that far ahead.
> 
> > > > Note that for the big cores we added the NNPI thing, which was for
> > > > Neural Network Processing something.
> > > 
> > > I'm sure that we will invent all sorts of strings for the "OPTDIFF"
> > > part of the name (many of which will only be used once or twice).
> > 
> > That's a bit sad; because as shown by the patches just send out; there
> > really isn't _that_ much variation right now.
> > 
> > Anyway, lets just give the thing a name; _NP whatever, and we can
> > rename it if needed.
> 
> Your other patch series shows that you aren't afraid
> of a little churn. So sure, we can go with _NP for now
> and fix it up later.  It's not like some OEM is going
> to make a CPU selection based on the #define name that
> we gave it in Linux :-)

From: Tony Luck <tony.luck@intel.com>

One of the use cases for this processor is as a network
processor. So give it an "_NP" tag for now. Could be changed
later if it turns out to group with some other tag.

Signed-off-by: Tony Luck <tony.luck@intel.com>
---
 arch/x86/include/asm/intel-family.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/x86/include/asm/intel-family.h b/arch/x86/include/asm/intel-family.h
index 5c05b2d389c3..23ed388a3a56 100644
--- a/arch/x86/include/asm/intel-family.h
+++ b/arch/x86/include/asm/intel-family.h
@@ -95,6 +95,7 @@
 
 #define INTEL_FAM6_ATOM_AIRMONT		0x4C /* Cherry Trail, Braswell */
 #define INTEL_FAM6_ATOM_AIRMONT_MID	0x5A /* Moorefield */
+#define INTEL_FAM6_ATOM_AIRMONT_NP	0x75 /* Lightning Mountain */
 
 #define INTEL_FAM6_ATOM_GOLDMONT	0x5C /* Apollo Lake */
 #define INTEL_FAM6_ATOM_GOLDMONT_D	0x5F /* Denverton */
-- 
2.20.1

