From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Mario.Limonciello@dell.com
Cc: yehezkel.bernat@intel.com, linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org, dvhart@infradead.org,
hughsient@gmail.com
Subject: Re: Fwd: [PATCH] Add driver to force WMI Thunderbolt controller power status
Date: Thu, 7 Sep 2017 09:36:07 +0300 [thread overview]
Message-ID: <20170907063607.GB2477@lahna.fi.intel.com> (raw)
In-Reply-To: <b74a2237da254faea0377fdcb93aa3e0@ausx13mpc120.AMER.DELL.COM>
On Wed, Sep 06, 2017 at 07:49:32PM +0000, Mario.Limonciello@dell.com wrote:
> > As this is a Thunderbolt specific function, maybe it's better to be
> > exposed from the Thunderbolt driver?
>
> I thought about this too, but the thunderbolt driver won't load if the
> controller doesn't exist in the first place, whereas this is a platform
> BIOS feature. I'll be interested to hear if Mika has a different perspective
> on if this should live in the TBT driver and the proper way to do it.
I think it makes sense to keep it separate from the Thunderbolt driver.
next prev parent reply other threads:[~2017-09-07 6:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 17:54 Mario Limonciello
[not found] ` <CA+CmpXt9EtzObijHT3gmm=xUwFDF3Ec=SFbNnPAk+oRdzAUADQ@mail.gmail.com>
2017-09-06 19:40 ` Fwd: " Bernat, Yehezkel
2017-09-06 19:46 ` Bernat, Yehezkel
2017-09-06 19:49 ` Fwd: " Mario.Limonciello
2017-09-06 20:09 ` Darren Hart
2017-09-06 20:26 ` Bernat, Yehezkel
2017-09-06 21:40 ` Mario.Limonciello
2017-09-06 22:27 ` Darren Hart
2017-09-06 22:34 ` Bernat, Yehezkel
2017-09-07 1:38 ` Mario.Limonciello
2017-09-06 21:43 ` Mario.Limonciello
2017-09-07 6:36 ` Mika Westerberg [this message]
2017-09-07 6:50 ` Mika Westerberg
2017-09-07 18:47 ` Mario.Limonciello
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=20170907063607.GB2477@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=Mario.Limonciello@dell.com \
--cc=dvhart@infradead.org \
--cc=hughsient@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=yehezkel.bernat@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
all inboxes | Powered by JetHome®