[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170519160133.ukkne2emubfbrrvg@sirena.org.uk>
Date: Fri, 19 May 2017 17:01:33 +0100
From: Mark Brown <broonie@...nel.org>
To: Jonathan Cameron <jic23@...nel.org>
Cc: Mika Westerberg <mika.westerberg@...ux.intel.com>,
Jan Kiszka <jan.kiszka@...mens.com>,
Peter Meerwald-Stadler <pmeerw@...erw.net>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Andy Shevchenko <andy.shevchenko@...il.com>,
linux-iio@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Sascha Weisenberger <sascha.weisenberger@...mens.com>
Subject: Re: [PATCH] iio: adc: Add support for TI ADC1x8s102
On Thu, Apr 27, 2017 at 07:01:07AM +0100, Jonathan Cameron wrote:
> Somewhat of a pain to basically use a random value as the default going
> forward. Presumably this isn't the first ever ACPI table to need to
> tell use about a reference voltage...
> Mark, seen anything similar?
> I see https://www.kernel.org/doc/Documentation/arm64/arm-acpi.txt suggests
> that mapping to regulators isn't expected to ever happen...
There's multiple different camps trying to use ACPI for very different
things. There's the server people on both x86 and ARM who want to use
standard ACPI and nothing but with the power management all hidden in
the AML but there's also the embedded x86 people who have the same needs
as DT platforms but find themselves unable to use DT so have to map all
the DT support into ACPI. This has been accepted in areas that clearly
don't overlap with areas where there are existing ACPI bindings for
things, power management is one area where there are clear bindings
though.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists