[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170515110103.59765-1-mika.westerberg@linux.intel.com>
Date: Mon, 15 May 2017 14:01:00 +0300
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: Linus Walleij <linus.walleij@...aro.org>,
Jean Delvare <jdelvare@...e.com>
Cc: Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Wei Yongjun <weiyongjun1@...wei.com>, bbaude@...hat.com,
mildred-bug.kernel@...dred.fr, barnacs@...tletit.be,
lvuksta@...il.com,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org
Subject: [PATCH 0/3] pinctrl: cherryview: Extend the DMI quirk to Intel_Strago systems
Hi,
It turned out that there are bunch of other Chromebooks that need the DMI
quirk as well. Most of these are based on Intel_Strago reference design so
we can identify them by using DMI_PRODUCT_FAMILY introduced in this series.
The systems without the family string we add them separately.
Related bugzilla entry:
https://bugzilla.kernel.org/show_bug.cgi?id=194945
I'm including fix from Yongjun as well because I did not find it in
v4.12-rc1 possibly because it just was forgotten.
Mika Westerberg (2):
firmware: dmi: Add DMI_PRODUCT_FAMILY identification string
pinctrl: cherryview: Extend the Chromebook DMI quirk to Intel_Strago systems
Wei Yongjun (1):
pinctrl: cherryview: Add terminate entry for dmi_system_id tables
drivers/firmware/dmi-id.c | 2 ++
drivers/firmware/dmi_scan.c | 1 +
drivers/pinctrl/intel/pinctrl-cherryview.c | 26 +++++++++++++++++++++-----
include/linux/mod_devicetable.h | 1 +
4 files changed, 25 insertions(+), 5 deletions(-)
--
2.11.0
Powered by blists - more mailing lists