From: <Mario.Limonciello@dell.com>
To: <dvhart@infradead.org>, <andy.shevchenko@gmail.com>
Cc: <srinivas.pandruvada@linux.intel.com>, <alex.hung@canonical.com>,
<andy@infradead.org>, <platform-driver-x86@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <rjw@rjwysocki.net>
Subject: Re: [PATCH v2] platform/x86: intel-hid: Add support for Device Specific Methods
Date: Sat, 7 Jul 2018 03:48:54 +0000 [thread overview]
Message-ID: <1530935335264.5774@Dell.com> (raw)
In-Reply-To: <20180706235907.GE3041@fury>
>I strongly advocate for vendors to have more control over their drivers,
>but this scenario really frustrates me. I don't think I can justify this
>to Linus as a fix. But before we just say "no" (because hey, I want
>these fixes available as early as possible too), let's ask Rafael if he
>has an opinion or if there is precedent for this in his experience with
>ACPI drivers in general:
Full disclosure - an updated FW has since been rolled out that reverted this
behavior back to previous FW behavior due to lack of Linux support for the
new _DSM. There is desire to use the new interface (as it did fix actual
problems with the old one) so at some point it may return. When that happens
it would be ideal that people who are (for example) running an LTS kernel
or distro kernel that tracks stable can pick it up too.
next prev parent reply other threads:[~2018-07-07 3:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 18:19 [PATCH v2] platform/x86: intel-hid: Add support for Device Specific Methods Srinivas Pandruvada
2018-06-29 16:44 ` Mario.Limonciello
2018-06-29 18:41 ` Srinivas Pandruvada
2018-07-02 12:41 ` Andy Shevchenko
2018-07-02 13:51 ` Mario.Limonciello
2018-07-02 14:06 ` Andy Shevchenko
2018-07-06 23:59 ` Darren Hart
2018-07-07 3:48 ` Mario.Limonciello [this message]
2018-07-07 16:24 ` Andy Shevchenko
2018-07-07 23:37 ` Srinivas Pandruvada
2018-07-08 17:53 ` Andy Shevchenko
2018-07-07 13:43 ` Srinivas Pandruvada
2018-07-09 4:38 ` Mario.Limonciello
2018-07-09 21:06 ` Darren Hart
2018-07-09 21:08 ` Mario.Limonciello
2018-07-09 23:17 ` Darren Hart
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=1530935335264.5774@Dell.com \
--to=mario.limonciello@dell.com \
--cc=alex.hung@canonical.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
/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).