From: Hans de Goede <hdegoede@redhat.com>
To: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>, Lee Jones <lee.jones@linaro.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] Intel PMIC: Intel PMIC mfd and OPRegion drivers must be built in
Date: Wed, 22 Mar 2017 12:29:18 +0100 [thread overview]
Message-ID: <20170322112923.20200-1-hdegoede@redhat.com> (raw)
Hi All,
Here is a series enforcing Intel PMIC mfd and OPRegion drivers to be built
in, this is necessary so that the OPRegion handlers are registered before
other drivers try to enter D0 which may require these OPRegion handlers.
Note patches 4 & 5 are for drivers which have been submitted but not
yet accepted in -next, so theoretically they could be squashed into
the original patches, but I believe it is good to keep them as separate
commits to have a git history which documents why these are builtin.
The patches span both the mfd and ACPI subsystems but can me merged
independently of each other I'm posting this as a single series as
both sides are part of fixing the same issue.
Regards,
Hans
next reply other threads:[~2017-03-22 11:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 11:29 Hans de Goede [this message]
2017-03-22 11:29 ` [PATCH 1/5] ACPI / PMIC: Stop xpower OPRegion handler relying on IIO Hans de Goede
2017-03-22 11:29 ` [PATCH 2/5] mfd: intel_soc_pmic: Select designware i2c-bus driver Hans de Goede
2017-03-22 12:53 ` Andy Shevchenko
2017-03-23 16:46 ` Lee Jones
2017-03-23 22:31 ` Hans de Goede
2017-03-22 11:29 ` [PATCH 3/5] mfd: axp20c-i2c: Select designware i2c-bus driver on x86 Hans de Goede
2017-03-22 11:29 ` [PATCH 4/5] mfd: intel_soc_pmic_chtwc: This driver must always be builtin when enabled Hans de Goede
2017-03-22 11:29 ` [PATCH 5/5] ACPI / PMIC: mfd: intel_pmic_chtwc: This driver must always be builtin Hans de Goede
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=20170322112923.20200-1-hdegoede@redhat.com \
--to=hdegoede@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=lee.jones@linaro.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).