Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754767AbcCAQFm (ORCPT ); Tue, 1 Mar 2016 11:05:42 -0500 Received: from mga14.intel.com ([192.55.52.115]:28863 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753747AbcCAQFk (ORCPT ); Tue, 1 Mar 2016 11:05:40 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,523,1449561600"; d="scan'208";a="898544565" From: "Moore, Robert" To: Toshi Kani , "rjw@rjwysocki.net" , "Williams, Dan J" CC: "Zheng, Lv" , "elliott@hpe.com" , "linux-nvdimm@lists.01.org" , "linux-acpi@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "devel@acpica.org" Subject: RE: [PATCH v2 1/3] ACPI/NFIT: Update Control Region Structure to comply ACPI 6.1 Thread-Topic: [PATCH v2 1/3] ACPI/NFIT: Update Control Region Structure to comply ACPI 6.1 Thread-Index: AQHRbbRts80XXzttYEOOULqVyeHP1J9Evf0wgACeKgD//2/VAA== Date: Tue, 1 Mar 2016 16:03:07 +0000 Message-ID: <94F2FBAB4432B54E8AACC7DFDE6C92E37E44D6E1@ORSMSX110.amr.corp.intel.com> References: <1456178130-26468-1-git-send-email-toshi.kani@hpe.com> <1456178130-26468-2-git-send-email-toshi.kani@hpe.com> <94F2FBAB4432B54E8AACC7DFDE6C92E37E44D64B@ORSMSX110.amr.corp.intel.com> <1456850284.15454.23.camel@hpe.com> In-Reply-To: <1456850284.15454.23.camel@hpe.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiM2Q1ODFhZDYtY2E5Ni00NzI0LWJlMjYtYmUxNjA4ZGFiMzdkIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6InFMWDZrRE9ENkpyY1RjTzhtOTU3d1FvU0ZxcjhOWHNOcEViWkJIYytvVkU9In0= x-ctpclassification: CTP_IC x-originating-ip: [10.22.254.140] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id u21G5kSE000356 Content-Length: 2042 Lines: 49 We have a bunch of macros in include/acmacros.h -- like this: ACPI_MOVE_16_TO_16(d, s) > -----Original Message----- > From: Toshi Kani [mailto:toshi.kani@hpe.com] > Sent: Tuesday, March 01, 2016 8:38 AM > To: Moore, Robert; rjw@rjwysocki.net; Williams, Dan J > Cc: Zheng, Lv; elliott@hpe.com; linux-nvdimm@lists.01.org; linux- > acpi@vger.kernel.org; linux-kernel@vger.kernel.org; devel@acpica.org > Subject: Re: [PATCH v2 1/3] ACPI/NFIT: Update Control Region Structure to > comply ACPI 6.1 > > On Tue, 2016-03-01 at 15:13 +0000, Moore, Robert wrote: > > > > > -----Original Message----- > > > From: Toshi Kani [mailto:toshi.kani@hpe.com] > > > Sent: Monday, February 22, 2016 1:55 PM > > > To: rjw@rjwysocki.net; Williams, Dan J > > > Cc: Moore, Robert; Zheng, Lv; elliott@hpe.com; > > > linux-nvdimm@lists.01.or g; linux-acpi@vger.kernel.org; > > > linux-kernel@vger.kernel.org; devel@acpica.org; Toshi Kani > > > Subject: [PATCH v2 1/3] ACPI/NFIT: Update Control Region Structure > > > to comply ACPI 6.1 > > > > > > ACPI 6.1, Table 5-133, updates NVDIMM Control Region Structure as > > > follows. > > >  - Valid Fields, Manufacturing Location, and Manufacturing Date > > >    are added from reserved range.  No change in the structure size. > > >  - IDs defined as SPD values are arrays of bytes.  The spec > > >    clarified that they need to be represented as arrays of bytes > > >    as well. > > > > > > This patch makes the following changes to support this update. > > >  - Change 'struct acpi_nfit_control_region' to reflect the update. > > >    SPD IDs are defined as arrays of bytes, so that they can be > > >    treated in the same way regardless of CPU endianness and are > > >    not miss-treated as little-endian numeric values. > > > > > > I don't think we are going to start changing the ACPI tables defined > > in the ACPICA headers because of this. We do in fact have macros for > > this purpose. > > Can you elaborate what macros you suggest to use for this purpose? > > Thanks, > -Toshi