* Re: [PATCH v2] pinctrl: cherryview: limit Strago DMI workarounds to version 1.0
2018-05-22 20:47 [PATCH v2] pinctrl: cherryview: limit Strago DMI workarounds to version 1.0 Dmitry Torokhov
@ 2018-05-23 4:36 ` Mika Westerberg
2018-05-23 4:46 ` Guenter Roeck
` (2 subsequent siblings)
3 siblings, 0 replies; 6+ messages in thread
From: Mika Westerberg @ 2018-05-23 4:36 UTC (permalink / raw)
To: Dmitry Torokhov
Cc: Linus Walleij, Heikki Krogerus, Andy Shevchenko, Guenter Roeck,
linux-gpio, linux-kernel
On Tue, May 22, 2018 at 01:47:53PM -0700, Dmitry Torokhov wrote:
> As Google/Intel will fix the BIOS/Coreboot issues with hardcoding
> virtual interrupt numbers for keyboard/touchpad/touchscreen controllers
> in ACPI tables, they will also update BOARD version number from 1.0
> to 1.1. Let's limit the DMI quirks that try to preserve virtual IRQ
> numbers on Strago boards to those that still carry older BIOSes.
>
> Note that ideally not BOARD but BIOS version should have been updated.
> However the BIOS version used by Chrome devices has format of
> Google_BUILD.BRANCH.PATCH which is not well suited for DMI matching as
> we do not have "less than" match mode for DMI data.
>
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=197953
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [PATCH v2] pinctrl: cherryview: limit Strago DMI workarounds to version 1.0
2018-05-22 20:47 [PATCH v2] pinctrl: cherryview: limit Strago DMI workarounds to version 1.0 Dmitry Torokhov
2018-05-23 4:36 ` Mika Westerberg
@ 2018-05-23 4:46 ` Guenter Roeck
2018-05-23 8:54 ` Andy Shevchenko
2018-05-24 8:19 ` Linus Walleij
3 siblings, 0 replies; 6+ messages in thread
From: Guenter Roeck @ 2018-05-23 4:46 UTC (permalink / raw)
To: Dmitry Torokhov, Mika Westerberg, Linus Walleij
Cc: Heikki Krogerus, Andy Shevchenko, linux-gpio, linux-kernel
On 05/22/2018 01:47 PM, Dmitry Torokhov wrote:
> As Google/Intel will fix the BIOS/Coreboot issues with hardcoding
> virtual interrupt numbers for keyboard/touchpad/touchscreen controllers
> in ACPI tables, they will also update BOARD version number from 1.0
> to 1.1. Let's limit the DMI quirks that try to preserve virtual IRQ
> numbers on Strago boards to those that still carry older BIOSes.
>
> Note that ideally not BOARD but BIOS version should have been updated.
> However the BIOS version used by Chrome devices has format of
> Google_BUILD.BRANCH.PATCH which is not well suited for DMI matching as
> we do not have "less than" match mode for DMI data.
>
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=197953
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> ---
>
> v1->v2:
>
> - switch from matching on DMI_BIOS_VERSION to DMI_BOARD_VERSION
>
>
> drivers/pinctrl/intel/pinctrl-cherryview.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/pinctrl/intel/pinctrl-cherryview.c b/drivers/pinctrl/intel/pinctrl-cherryview.c
> index b1ae1618fefea..44133e6846303 100644
> --- a/drivers/pinctrl/intel/pinctrl-cherryview.c
> +++ b/drivers/pinctrl/intel/pinctrl-cherryview.c
> @@ -1527,6 +1527,7 @@ static const struct dmi_system_id chv_no_valid_mask[] = {
> .matches = {
> DMI_MATCH(DMI_SYS_VENDOR, "GOOGLE"),
> DMI_MATCH(DMI_PRODUCT_FAMILY, "Intel_Strago"),
> + DMI_MATCH(DMI_BOARD_VERSION, "1.0"),
> },
> },
> {
> @@ -1534,6 +1535,7 @@ static const struct dmi_system_id chv_no_valid_mask[] = {
> .matches = {
> DMI_MATCH(DMI_SYS_VENDOR, "HP"),
> DMI_MATCH(DMI_PRODUCT_NAME, "Setzer"),
> + DMI_MATCH(DMI_BOARD_VERSION, "1.0"),
> },
> },
> {
> @@ -1541,6 +1543,7 @@ static const struct dmi_system_id chv_no_valid_mask[] = {
> .matches = {
> DMI_MATCH(DMI_SYS_VENDOR, "GOOGLE"),
> DMI_MATCH(DMI_PRODUCT_NAME, "Cyan"),
> + DMI_MATCH(DMI_BOARD_VERSION, "1.0"),
> },
> },
> {
> @@ -1548,6 +1551,7 @@ static const struct dmi_system_id chv_no_valid_mask[] = {
> .matches = {
> DMI_MATCH(DMI_SYS_VENDOR, "GOOGLE"),
> DMI_MATCH(DMI_PRODUCT_NAME, "Celes"),
> + DMI_MATCH(DMI_BOARD_VERSION, "1.0"),
> },
> },
> {}
>
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [PATCH v2] pinctrl: cherryview: limit Strago DMI workarounds to version 1.0
2018-05-22 20:47 [PATCH v2] pinctrl: cherryview: limit Strago DMI workarounds to version 1.0 Dmitry Torokhov
2018-05-23 4:36 ` Mika Westerberg
2018-05-23 4:46 ` Guenter Roeck
@ 2018-05-23 8:54 ` Andy Shevchenko
2018-05-24 8:19 ` Linus Walleij
3 siblings, 0 replies; 6+ messages in thread
From: Andy Shevchenko @ 2018-05-23 8:54 UTC (permalink / raw)
To: Dmitry Torokhov, Mika Westerberg, Linus Walleij
Cc: Heikki Krogerus, Guenter Roeck, linux-gpio, linux-kernel
On Tue, 2018-05-22 at 13:47 -0700, Dmitry Torokhov wrote:
> As Google/Intel will fix the BIOS/Coreboot issues with hardcoding
> virtual interrupt numbers for keyboard/touchpad/touchscreen
> controllers
> in ACPI tables, they will also update BOARD version number from 1.0
> to 1.1. Let's limit the DMI quirks that try to preserve virtual IRQ
> numbers on Strago boards to those that still carry older BIOSes.
>
> Note that ideally not BOARD but BIOS version should have been updated.
> However the BIOS version used by Chrome devices has format of
> Google_BUILD.BRANCH.PATCH which is not well suited for DMI matching as
> we do not have "less than" match mode for DMI data.
>
Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=197953
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> ---
>
> v1->v2:
>
> - switch from matching on DMI_BIOS_VERSION to DMI_BOARD_VERSION
>
>
> drivers/pinctrl/intel/pinctrl-cherryview.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/pinctrl/intel/pinctrl-cherryview.c
> b/drivers/pinctrl/intel/pinctrl-cherryview.c
> index b1ae1618fefea..44133e6846303 100644
> --- a/drivers/pinctrl/intel/pinctrl-cherryview.c
> +++ b/drivers/pinctrl/intel/pinctrl-cherryview.c
> @@ -1527,6 +1527,7 @@ static const struct dmi_system_id
> chv_no_valid_mask[] = {
> .matches = {
> DMI_MATCH(DMI_SYS_VENDOR, "GOOGLE"),
> DMI_MATCH(DMI_PRODUCT_FAMILY,
> "Intel_Strago"),
> + DMI_MATCH(DMI_BOARD_VERSION, "1.0"),
> },
> },
> {
> @@ -1534,6 +1535,7 @@ static const struct dmi_system_id
> chv_no_valid_mask[] = {
> .matches = {
> DMI_MATCH(DMI_SYS_VENDOR, "HP"),
> DMI_MATCH(DMI_PRODUCT_NAME, "Setzer"),
> + DMI_MATCH(DMI_BOARD_VERSION, "1.0"),
> },
> },
> {
> @@ -1541,6 +1543,7 @@ static const struct dmi_system_id
> chv_no_valid_mask[] = {
> .matches = {
> DMI_MATCH(DMI_SYS_VENDOR, "GOOGLE"),
> DMI_MATCH(DMI_PRODUCT_NAME, "Cyan"),
> + DMI_MATCH(DMI_BOARD_VERSION, "1.0"),
> },
> },
> {
> @@ -1548,6 +1551,7 @@ static const struct dmi_system_id
> chv_no_valid_mask[] = {
> .matches = {
> DMI_MATCH(DMI_SYS_VENDOR, "GOOGLE"),
> DMI_MATCH(DMI_PRODUCT_NAME, "Celes"),
> + DMI_MATCH(DMI_BOARD_VERSION, "1.0"),
> },
> },
> {}
> --
> 2.17.0.441.gb46fe60e1d-goog
>
>
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [PATCH v2] pinctrl: cherryview: limit Strago DMI workarounds to version 1.0
2018-05-22 20:47 [PATCH v2] pinctrl: cherryview: limit Strago DMI workarounds to version 1.0 Dmitry Torokhov
` (2 preceding siblings ...)
2018-05-23 8:54 ` Andy Shevchenko
@ 2018-05-24 8:19 ` Linus Walleij
2018-05-24 16:01 ` Dmitry Torokhov
3 siblings, 1 reply; 6+ messages in thread
From: Linus Walleij @ 2018-05-24 8:19 UTC (permalink / raw)
To: Dmitry Torokhov
Cc: Mika Westerberg, Heikki Krogerus, Andy Shevchenko, Guenter Roeck,
open list:GPIO SUBSYSTEM, linux-kernel
On Tue, May 22, 2018 at 10:47 PM, Dmitry Torokhov
<dmitry.torokhov@gmail.com> wrote:
> As Google/Intel will fix the BIOS/Coreboot issues with hardcoding
> virtual interrupt numbers for keyboard/touchpad/touchscreen controllers
> in ACPI tables, they will also update BOARD version number from 1.0
> to 1.1. Let's limit the DMI quirks that try to preserve virtual IRQ
> numbers on Strago boards to those that still carry older BIOSes.
>
> Note that ideally not BOARD but BIOS version should have been updated.
> However the BIOS version used by Chrome devices has format of
> Google_BUILD.BRANCH.PATCH which is not well suited for DMI matching as
> we do not have "less than" match mode for DMI data.
>
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=197953
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> ---
>
> v1->v2:
>
> - switch from matching on DMI_BIOS_VERSION to DMI_BOARD_VERSION
Patch applied for fixes.
Should this also be tagged for stable?
Yours,
Linus Walleij
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [PATCH v2] pinctrl: cherryview: limit Strago DMI workarounds to version 1.0
2018-05-24 8:19 ` Linus Walleij
@ 2018-05-24 16:01 ` Dmitry Torokhov
0 siblings, 0 replies; 6+ messages in thread
From: Dmitry Torokhov @ 2018-05-24 16:01 UTC (permalink / raw)
To: Linus Walleij
Cc: Mika Westerberg, Heikki Krogerus, Andy Shevchenko, Guenter Roeck,
open list:GPIO SUBSYSTEM, linux-kernel
Hi Linus,
On Thu, May 24, 2018 at 10:19:55AM +0200, Linus Walleij wrote:
> On Tue, May 22, 2018 at 10:47 PM, Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
>
> > As Google/Intel will fix the BIOS/Coreboot issues with hardcoding
> > virtual interrupt numbers for keyboard/touchpad/touchscreen controllers
> > in ACPI tables, they will also update BOARD version number from 1.0
> > to 1.1. Let's limit the DMI quirks that try to preserve virtual IRQ
> > numbers on Strago boards to those that still carry older BIOSes.
> >
> > Note that ideally not BOARD but BIOS version should have been updated.
> > However the BIOS version used by Chrome devices has format of
> > Google_BUILD.BRANCH.PATCH which is not well suited for DMI matching as
> > we do not have "less than" match mode for DMI data.
> >
> > Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=197953
> > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > ---
> >
> > v1->v2:
> >
> > - switch from matching on DMI_BIOS_VERSION to DMI_BOARD_VERSION
>
> Patch applied for fixes.
>
> Should this also be tagged for stable?
No, I do not think so. The workaround being active does not cause any
issues on boxes with updated firmware, so there is no point in trying to
get the patch to older kernels. It is going forward that we want the
"proper" behavior, when possible.
Also, I am not quite sure when the new firmware version will get
qualified for release.
Thanks.
--
Dmitry
^ permalink raw reply [flat|nested] 6+ messages in thread