From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: unlisted-recipients:; (no To-header on input)
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
linux-acpi@vger.kernel.org, Len Brown <lenb@kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Lee Jones <lee.jones@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: [PATCH 0/2] Solve a few issues with intel_pmic_chtdc_ti.c
Date: Tue, 12 May 2020 07:51:55 +0200 [thread overview]
Message-ID: <cover.1589262490.git.mchehab+huawei@kernel.org> (raw)
While doing some tests with a device that I'm using to work with the
atomisp driver (an Asus T101HA), I noticed some warnings produced
by the i915 driver.
The first one is that building intel_pmic_chtdc_ti as a module is too
late, as fbcon driver (and i915) will need it earlier.
The second one is that the thermal I2C OpRegion needed by the i915
is not registered.
Those patches address the issues I detected.
Mauro Carvalho Chehab (2):
ACPI / PMIC: Add i2c address for thermal control
mfd: Kconfig: change INTEL_SOC_PMIC_CHTDC_TI to bool
drivers/acpi/pmic/intel_pmic_chtdc_ti.c | 1 +
drivers/mfd/Kconfig | 6 +++++-
2 files changed, 6 insertions(+), 1 deletion(-)
--
2.26.2
next reply other threads:[~2020-05-12 5:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 5:51 Mauro Carvalho Chehab [this message]
2020-05-12 5:51 ` [PATCH 1/2] ACPI / PMIC: Add i2c address for thermal control Mauro Carvalho Chehab
2020-05-12 7:45 ` Hans de Goede
2020-05-12 8:48 ` Mika Westerberg
2020-05-12 9:14 ` Andy Shevchenko
2020-05-15 16:28 ` Rafael J. Wysocki
2020-05-18 7:22 ` Hans de Goede
2020-05-18 8:18 ` Mauro Carvalho Chehab
2020-05-18 11:06 ` Rafael J. Wysocki
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=cover.1589262490.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=lee.jones@linaro.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@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;
as well as URLs for NNTP newsgroup(s).