From: Jonathan Cameron <jic23@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
linux-iio@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sascha Weisenberger <sascha.weisenberger@siemens.com>
Subject: Re: [PATCH] iio: adc: Add support for TI ADC1x8s102
Date: Sat, 20 May 2017 17:26:30 +0100 [thread overview]
Message-ID: <e224532c-260c-a2df-23be-35e5b3243151@kernel.org> (raw)
In-Reply-To: <20170519160133.ukkne2emubfbrrvg@sirena.org.uk>
On 19/05/17 17:01, Mark Brown wrote:
> 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.
Thanks Mark,
Just to clarify what do we do here, where a regulator is providing a
reference voltage and there appears to be no information on it in ACPI?
Right now we are just going with a fixed value that matches the board
someone has, but that's hardly sustainable.
Jonathan
>
next prev parent reply other threads:[~2017-05-20 16:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 19:28 [PATCH] iio: adc: Add support for TI ADC1x8s102 Jan Kiszka
2017-04-24 20:05 ` Andy Shevchenko
2017-04-24 20:10 ` Andy Shevchenko
2017-04-24 20:37 ` Jan Kiszka
2017-04-24 20:32 ` Jan Kiszka
2017-04-24 21:25 ` Andy Shevchenko
2017-04-25 5:44 ` Jan Kiszka
2017-04-25 9:42 ` Andy Shevchenko
2017-04-25 10:53 ` Jan Kiszka
2017-04-25 11:27 ` Andy Shevchenko
2017-04-25 11:35 ` Mika Westerberg
2017-04-25 12:17 ` Jan Kiszka
2017-04-25 12:30 ` Mika Westerberg
2017-04-25 13:47 ` Jan Kiszka
2017-04-25 16:12 ` Jan Kiszka
2017-04-26 9:01 ` Mika Westerberg
2017-04-27 6:01 ` Jonathan Cameron
2017-04-27 6:04 ` Jonathan Cameron
2017-05-19 16:01 ` Mark Brown
2017-05-20 16:26 ` Jonathan Cameron [this message]
2017-05-22 10:06 ` Mark Brown
2017-04-25 6:06 ` Jan Kiszka
2017-04-25 7:31 ` Peter Meerwald-Stadler
2017-04-25 9:20 ` Andy Shevchenko
2017-04-25 9:32 ` Jan Kiszka
2017-04-25 11:23 ` Andy Shevchenko
2017-04-25 12:20 ` Mika Westerberg
2017-04-26 5:37 ` Jan Kiszka
2017-04-26 10:21 ` Andy Shevchenko
2017-04-27 6:14 ` Jonathan Cameron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e224532c-260c-a2df-23be-35e5b3243151@kernel.org \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=broonie@kernel.org \
--cc=jan.kiszka@siemens.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=pmeerw@pmeerw.net \
--cc=sascha.weisenberger@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).