linux-kernel - Re: Fwd: [PATCH] Add driver to force WMI Thunderbolt controller power status

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 7 Sep 2017 09:36:07 +0300
From:   Mika Westerberg <mika.westerberg@...ux.intel.com>
To:     Mario.Limonciello@...l.com
Cc:     yehezkel.bernat@...el.com, linux-kernel@...r.kernel.org,
        platform-driver-x86@...r.kernel.org, dvhart@...radead.org,
        hughsient@...il.com
Subject: Re: Fwd: [PATCH] Add driver to force WMI Thunderbolt controller
 power status

On Wed, Sep 06, 2017 at 07:49:32PM +0000, Mario.Limonciello@...l.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.