Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1435050AbdDZJDJ (ORCPT ); Wed, 26 Apr 2017 05:03:09 -0400 Received: from mga03.intel.com ([134.134.136.65]:24935 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934607AbdDZJCE (ORCPT ); Wed, 26 Apr 2017 05:02:04 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.37,253,1488873600"; d="scan'208";a="961232674" Date: Wed, 26 Apr 2017 12:01:58 +0300 From: Mika Westerberg To: Jan Kiszka Cc: Peter Meerwald-Stadler , Andy Shevchenko , Andy Shevchenko , Jonathan Cameron , linux-iio@vger.kernel.org, Linux Kernel Mailing List , Sascha Weisenberger Subject: Re: [PATCH] iio: adc: Add support for TI ADC1x8s102 Message-ID: <20170426090158.GV7152@lahna.fi.intel.com> References: <38f562f3-69d2-67d0-ecc2-4b44d67286e2@siemens.com> <08d40bf0-4e68-d763-af99-be1f60e369fc@siemens.com> <1493119630.24567.192.camel@linux.intel.com> <20170425113513.GQ7152@lahna.fi.intel.com> <2a116105-0046-bcc1-b560-f6986220fb4b@siemens.com> <20170425123029.GS7152@lahna.fi.intel.com> <32803199-239f-821c-7942-748436d53261@siemens.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <32803199-239f-821c-7942-748436d53261@siemens.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.7.1 (2016-10-04) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 676 Lines: 18 On Tue, Apr 25, 2017 at 06:12:12PM +0200, Jan Kiszka wrote: > Now, do you also a suggestion where to put that 5 V reference voltage > value that is hard-coded (via wiring) on the target boards for the ADC? > That is now device-specific, not a controller parameter. Is there an > ACPI-way to express such a parameter? You may put it into device property using _DSD (as long as you don't try to represent regulators or so). > How would that be done for DTs? I don't know but you may look under Documentation/devicetree/bindings if there is anything. > Plan B would be hard-coding in the code for now, waiting for a second, > non-ACPI user to address it. Sounds reasonable.