From: Takashi Iwai <tiwai@suse.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
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 13:01:41 +0200 [thread overview]
Message-ID: <s5hefs3amsq.wl-tiwai@suse.de> (raw)
In-Reply-To: <s5ho9r7aohj.wl-tiwai@suse.de>
On Tue, 22 Aug 2017 12:25:12 +0200,
Takashi Iwai wrote:
>
> On Tue, 22 Aug 2017 11:58:35 +0200,
> Andy Shevchenko wrote:
> >
> > On Tue, 2017-08-22 at 07:57 +0200, Takashi Iwai wrote:
> > > This patch adds the opregion driver for Dollar Cove TI PMIC on Intel
> > > Cherry Trail devices. The patch is based on the original work by
> > > Intel, found at:
> > > https://github.com/01org/ProductionKernelQuilts
> > > with many cleanups and rewrites.
> > >
> > > The driver is currently provided only as built-in to follow other
> > > PMIC opregion drivers convention.
> > >
> > > The re-enumeration of devices at probe is required for fixing the
> > > issues on HP x2 210 G2. See bug#195689.
> > >
> > >
> >
> > > +static int dc_ti_pmic_get_raw_temp(struct regmap *regmap, int reg)
> > > +{
> > > + int temp_l, temp_h;
> > > +
> > > + if (regmap_read(regmap, reg, &temp_l) ||
> > > + regmap_read(regmap, reg - 1, &temp_h))
> > > + return -EIO;
> > > +
> > > + return temp_l | (temp_h & 0x3) << 8;
> > > +}
> >
> > I'm not sure I understand this "- 1" part along with choice of l and h
> > suffixes.
> >
> > 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.
thanks,
Takashi
next prev parent reply other threads:[~2017-08-22 11:01 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 [this message]
2017-08-22 11:37 ` Andy Shevchenko
2017-08-22 12:06 ` Takashi Iwai
2017-08-22 12:08 ` Andy Shevchenko
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=s5hefs3amsq.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=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 \
/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