.@gmail.com; yehezkel...@gmail.com
> Subject: Re: [PATCH v3] Add driver to force WMI Thunderbolt controller power
> status
>
> On Thu, Sep 14, 2017 at 05:59:19PM +0300, Mika Westerberg wrote:
> > On Thu, Sep 14, 2017 at 02:52:27PM +, mario.limoncie...@dell.com wrote:
On Thu, Sep 14, 2017 at 05:59:19PM +0300, Mika Westerberg wrote:
> On Thu, Sep 14, 2017 at 02:52:27PM +, mario.limoncie...@dell.com wrote:
> > > Looking at drivers/platform/x86/wmi.c:wmi_dev_uevent() it seems that
> > > a modalias consisting of "wmi:" followed by the GUID is sent to udevd.
> >
On Thu, Sep 14, 2017 at 05:59:19PM +0300, Mika Westerberg wrote:
> On Thu, Sep 14, 2017 at 02:52:27PM +, mario.limoncie...@dell.com wrote:
> > > Looking at drivers/platform/x86/wmi.c:wmi_dev_uevent() it seems that
> > > a modalias consisting of "wmi:" followed by the GUID is sent to udevd.
> >
On Thu, Sep 14, 2017 at 02:52:27PM +, mario.limoncie...@dell.com wrote:
> > Looking at drivers/platform/x86/wmi.c:wmi_dev_uevent() it seems that
> > a modalias consisting of "wmi:" followed by the GUID is sent to udevd.
> > For udevd to then load the module, I suspect you need to add a
> > MODU
ezkel...@gmail.com;
> mika.westerb...@linux.intel.com
> Subject: Re: [PATCH v3] Add driver to force WMI Thunderbolt controller power
> status
>
> On Thu, Sep 14, 2017 at 06:42:03AM +, mario.limoncie...@dell.com wrote:
> > > On Fri, Sep 08, 2017 at 10:23:11AM -0500, Mario Limon
On Thu, Sep 14, 2017 at 06:42:03AM +, mario.limoncie...@dell.com wrote:
> > On Fri, Sep 08, 2017 at 10:23:11AM -0500, Mario Limonciello wrote:
> > > +static const struct wmi_device_id intel_wmi_thunderbolt_id_table[] = {
> > > + { .guid_string = INTEL_WMI_THUNDERBOLT_GUID },
> > > + { },
> > >
esterberg
> Subject: Re: [PATCH v3] Add driver to force WMI Thunderbolt controller power
> status
>
> Sorry, late to the party.
>
> On Fri, Sep 08, 2017 at 10:23:11AM -0500, Mario Limonciello wrote:
> > + mode = hex_to_bin(buf[0]);
> > + if (mode == 0 || mod
Sorry, late to the party.
On Fri, Sep 08, 2017 at 10:23:11AM -0500, Mario Limonciello wrote:
> + mode = hex_to_bin(buf[0]);
> + if (mode == 0 || mode == 1) {
> + status = wmi_evaluate_method(INTEL_WMI_THUNDERBOLT_GUID, 0, 1,
> + &input,
> -Original Message-
> From: Darren Hart [mailto:dvh...@infradead.org]
> Sent: Monday, September 11, 2017 4:45 PM
> To: Limonciello, Mario
> Cc: LKML ; platform-driver-...@vger.kernel.org;
> Richard Hughes ; Yehezkel Bernat
> ; Mika Westerberg
> Subject: Re:
On Fri, Sep 08, 2017 at 10:23:11AM -0500, Mario Limonciello wrote:
> Current implementations of Intel Thunderbolt controllers will go
> into a low power mode when not in use.
>
> Many machines containing these controllers also have a GPIO wired up
> that can force the controller awake. This is of
(Now in plain text. Sorry about that.)
On Sat, Sep 9, 2017 at 10:09 AM, Mika Westerberg
wrote:
> On Fri, Sep 08, 2017 at 10:23:11AM -0500, Mario Limonciello wrote:
>> Current implementations of Intel Thunderbolt controllers will go
>> into a low power mode when not in use.
>>
>> Many machines con
On Fri, Sep 08, 2017 at 10:23:11AM -0500, Mario Limonciello wrote:
> Current implementations of Intel Thunderbolt controllers will go
> into a low power mode when not in use.
>
> Many machines containing these controllers also have a GPIO wired up
> that can force the controller awake. This is of
12 matches
Mail list logo
