Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965759AbbD0V5R (ORCPT ); Mon, 27 Apr 2015 17:57:17 -0400 Received: from mga09.intel.com ([134.134.136.24]:52670 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965261AbbD0V5O (ORCPT ); Mon, 27 Apr 2015 17:57:14 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.11,660,1422950400"; d="scan'208";a="701769834" Message-ID: <553EB0B3.5000707@linux.intel.com> Date: Mon, 27 Apr 2015 14:57:07 -0700 From: sathyanarayanan kuppuswamy Reply-To: sathyanarayanan.kuppuswamy@linux.intel.com Organization: Intel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Octavian Purdila CC: Jonathan Cameron , Lars-Peter Clausen , Peter Meerwald , Robert Moore , Rafael J Wysocki , lenb@kernel.org, linux-api@vger.kernel.org, lkml , "linux-iio@vger.kernel.org" , "linux-acpi@vger.kernel.org" Subject: Re: [RFC PATCH 3/3] iio: derive the mounting matrix from ACPI _PLD objects References: <1430146908-27919-1-git-send-email-octavian.purdila@intel.com> <1430146908-27919-4-git-send-email-octavian.purdila@intel.com> <64714.10.254.87.235.1430149342.squirrel@linux.intel.com> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1614 Lines: 39 Hi On 04/27/2015 08:54 AM, Octavian Purdila wrote: > On Mon, Apr 27, 2015 at 6:42 PM, Kuppuswamy Sathyanarayanan > wrote: >> Since Acpi framework already exports this info to user space, Why not do >> this derivation in user space code ? Why do we need new ABI, if the same >> can be derived from existing one. >> > The ABI was added in the previous patch so that we can present the > sensor orientation information to userspace even in the case of device > tree. If the main reason for implementing a new ABI is to support DT platforms, Why not implement a version of _PLD for device tree ? Don't you think it would be much better than adding a new ABI to export redundant information ? Also the location information of the device is not just specific to iio drivers. You should consider that we would have similar requirements for devices implemented as input or platform drivers. > > The purpose of this patch is to provide a consistent ABI to userspace, > i.e. to avoid doing one thing in the ACPI case and another thing in > the case of device tree. > -- > To unsubscribe from this list: send the line "unsubscribe linux-acpi" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- Sathyanarayanan Kuppuswamy Android kernel developer -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/