From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-kernel@vger.kernel.org, Lee Jones <lee.jones@linaro.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Johannes Stezenbach <js@sig21.net>,
linux-input@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH 3/3] ACPI / PMIC: Add opregion driver for Intel Dollar Cove TI PMIC
Date: Tue, 22 Aug 2017 15:08:27 +0300 [thread overview]
Message-ID: <1503403707.25945.54.camel@linux.intel.com> (raw)
In-Reply-To: <1503401841.25945.51.camel@linux.intel.com>
On Tue, 2017-08-22 at 14:37 +0300, Andy Shevchenko wrote:
> On Tue, 2017-08-22 at 13:01 +0200, Takashi Iwai wrote:
> > On Tue, 22 Aug 2017 12:25:12 +0200,
> > Takashi Iwai wrote:
> > > > Does it mean the register is big endian?
> > >
> > > Good point, I need to check the original code and the values.
> >
> > It's really big-endian, the order is hi:lo.
> >
> > But, admittedly, the temperature code hasn't been tested, and it's
> > possibly missing something. So I'm fine to drop that part in the
> > first version, too.
>
> I don't know if regmap allows you to define registers with different
> sizes for same chip, perhaps it would make sense to start register
> from
> hi part (and not doing non-intuitive "- 1", or maybe "+ 1" instead)
> and
> mark it in comment that is BE16.
I have just checked datasheet, so, there are 4 pairs of BE16 registers.
VBAT (Hi:Lo) 0x54
DIETEMP 0x56
BPTHERM 0x58
GPADC 0x5a
So, I would create a separate address mapping for them, dropping out
that _LOW suffix and put a comment that they are BE16 since ADC has 10-
bit resolution.
Or even do a separate ADC driver under drivers/iio/adc for PMIC(s).
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-08-22 12:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 5:57 [PATCH 0/3] Dollar Cove TI PMIC support for Intel Cherry Trail Takashi Iwai
2017-08-22 5:57 ` [PATCH 1/3] mfd: Add support for Cherry Trail Dollar Cove TI PMIC Takashi Iwai
2017-08-22 9:37 ` Andy Shevchenko
2017-08-22 10:27 ` Takashi Iwai
2017-08-22 5:57 ` [PATCH 2/3] input/keyboard: Add support for Dollar Cove TI power button Takashi Iwai
2017-08-22 9:42 ` Andy Shevchenko
2017-08-22 10:58 ` Takashi Iwai
2017-08-22 17:25 ` Johannes Stezenbach
2017-08-31 18:33 ` Dmitry Torokhov
2017-08-31 20:34 ` Takashi Iwai
2017-09-01 11:09 ` Andy Shevchenko
2017-09-01 12:12 ` Takashi Iwai
2017-08-22 5:57 ` [PATCH 3/3] ACPI / PMIC: Add opregion driver for Intel Dollar Cove TI PMIC Takashi Iwai
2017-08-22 9:58 ` Andy Shevchenko
2017-08-22 10:25 ` Takashi Iwai
2017-08-22 11:01 ` Takashi Iwai
2017-08-22 11:37 ` Andy Shevchenko
2017-08-22 12:06 ` Takashi Iwai
2017-08-22 12:08 ` Andy Shevchenko [this message]
2017-08-22 12:26 ` Takashi Iwai
2017-08-22 13:26 ` Andy Shevchenko
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=1503403707.25945.54.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=js@sig21.net \
--cc=lee.jones@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
--cc=tiwai@suse.de \
/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).