[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <68ad47a7-ac6f-0a1b-0892-850bb95c002b@linux.intel.com>
Date: Fri, 16 Aug 2019 11:22:16 +0800
From: "Tanwar, Rahul" <rahul.tanwar@...ux.intel.com>
To: Borislav Petkov <bp@...en8.de>, Tony Luck <tony.luck@...el.com>
Cc: tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
x86@...nel.org, andriy.shevchenko@...el.com, alan@...ux.intel.com,
ricardo.neri-calderon@...ux.intel.com, rafael.j.wysocki@...el.com,
linux-kernel@...r.kernel.org, qi-ming.wu@...el.com,
cheol.yong.kim@...el.com, rahul.tanwar@...el.com
Subject: Re: [PATCH 2/3] x86: cpu: Add new Intel Atom CPU type
Hi Boris,
Well noted, will have Tony in loop from now on. Thanks.
Regards,
Rahul
On 15/8/2019 8:22 PM, Borislav Petkov wrote:
> On Thu, Aug 15, 2019 at 05:46:46PM +0800, Rahul Tanwar wrote:
>> This patch adds a new variant of Intel Atom Airmont CPU model used in a
>> network processor SoC named Lightning Mountain.
>>
>> Signed-off-by: Rahul Tanwar <rahul.tanwar@...ux.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 0278aa66ef62..cbbb8250370f 100644
>> --- a/arch/x86/include/asm/intel-family.h
>> +++ b/arch/x86/include/asm/intel-family.h
>> @@ -73,6 +73,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_X 0x5F /* Denverton */
>> --
> Also, in addition to what Thomas said, due to the fact that all the
> different groups within Intel are sending patches with model names,
> please synchronize that model naming and patch sending with Tony from
> now on:
>
> https://git.kernel.org/tip/5ed1c835ed8b522ce25071cc2d56a9a09bd5b59e
>
> He'll document the naming scheme and pay attention to what goes where so
> make sure you CC him, talk to him or have him in the loop, in general.
>
> Thx.
>
Powered by blists - more mailing lists