From: <Mario.Limonciello@dell.com>
To: <andy.shevchenko@gmail.com>
Cc: <dvhart@infradead.org>, <linux-kernel@vger.kernel.org>,
<platform-driver-x86@vger.kernel.org>,
<mika.westerberg@intel.com>
Subject: RE: [PATCH] platform/x86: intel-wmi-thunderbolt: Add dynamic debugging
Date: Wed, 26 Sep 2018 17:03:45 +0000 [thread overview]
Message-ID: <72af799dd45442e6bd35082e1579013a@ausx13mpc120.AMER.DELL.COM> (raw)
In-Reply-To: <CAHp75VeGQTEZOrMbNsbsxSb4RcN1y=gAZuZ5Z6FawuU-e0+qcg@mail.gmail.com>
>
> On Wed, Sep 26, 2018 at 7:11 PM Mario Limonciello
> <mario.limonciello@dell.com> wrote:
> >
> > Some users have been reporting issues with thunderbolt being turned off
> > before fully initialized. This is suspected to be caused by userspace
> > turning off the Thunderbolt controller using intel-wmi-thunderbolt
> > prematurely.
> >
>
> > Details are available here:
> > https://bugzilla.kernel.org/show_bug.cgi?id=201227
> > https://bugzilla.kernel.org/show_bug.cgi?id=199631
>
> BugLink: ... ?
> BugLink: ... ?
>
> I can do it myself if you are okay with this format.
>
> The patch itself LGTM.
Sure, thank you.
>
> >
> > Userspace has already made some mitigiations for this situation:
> > https://github.com/hughsie/fwupd/commit/ef6f1d76983c9b66
> > https://github.com/hughsie/fwupd/commit/c07ce5b4889a5384
> >
> > To allow easier debugging of this situation add output that can be turned
> > on with dynamic debugging to better root cause this problem.
> >
> > Suggested-by: Mika Westerberg <mika.westerberg@intel.com>
> > Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
> > ---
> > drivers/platform/x86/intel-wmi-thunderbolt.c | 6 +++++-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/platform/x86/intel-wmi-thunderbolt.c
> b/drivers/platform/x86/intel-wmi-thunderbolt.c
> > index c2257bd..ce5fbf0 100644
> > --- a/drivers/platform/x86/intel-wmi-thunderbolt.c
> > +++ b/drivers/platform/x86/intel-wmi-thunderbolt.c
> > @@ -38,12 +38,16 @@ static ssize_t force_power_store(struct device *dev,
> > input.length = sizeof(u8);
> > input.pointer = &mode;
> > mode = hex_to_bin(buf[0]);
> > + dev_dbg(dev, "force_power: storing %#x\n", mode);
> > if (mode == 0 || mode == 1) {
> > status = wmi_evaluate_method(INTEL_WMI_THUNDERBOLT_GUID, 0, 1,
> > &input, NULL);
> > - if (ACPI_FAILURE(status))
> > + if (ACPI_FAILURE(status)) {
> > + dev_dbg(dev, "force_power: failed to evaluate ACPI method\n");
> > return -ENODEV;
> > + }
> > } else {
> > + dev_dbg(dev, "force_power: unsupported mode\n");
> > return -EINVAL;
> > }
> > return count;
> > --
> > 2.7.4
> >
>
>
> --
> With Best Regards,
> Andy Shevchenko
next prev parent reply other threads:[~2018-09-26 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 16:10 [PATCH] platform/x86: intel-wmi-thunderbolt: Add dynamic debugging Mario Limonciello
2018-09-26 17:02 ` Andy Shevchenko
2018-09-26 17:03 ` Mario.Limonciello [this message]
2018-09-26 17:10 ` Andy Shevchenko
2018-09-26 18:34 ` Mika Westerberg
2018-09-26 19:25 ` Andy Shevchenko
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=72af799dd45442e6bd35082e1579013a@ausx13mpc120.AMER.DELL.COM \
--to=mario.limonciello@dell.com \
--cc=andy.shevchenko@gmail.com \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@intel.com \
--cc=platform-driver-x86@vger.kernel.org \
/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).