Re: [PATCH v2] Add driver to force WMI Thunderbolt controller power status

From	Darren Hart <dvhart@infradead.org>
Newsgroups	linux.kernel
Subject	Re: [PATCH v2] Add driver to force WMI Thunderbolt controller power status
Date	2017-09-11 23:50 +0200
Message-ID	<uoEKB-rj-3@gated-at.bofh.it> (permalink)
References	(2 earlier) <untez-nf-31@gated-at.bofh.it> <unFpn-de-3@gated-at.bofh.it> <unI3U-25A-29@gated-at.bofh.it> <uotvP-19R-7@gated-at.bofh.it> <uotvP-19R-15@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Mon, Sep 11, 2017 at 12:46:14PM +0300, Mika Westerberg wrote:
> On Mon, Sep 11, 2017 at 02:39:55AM -0700, Darren Hart wrote:
> > Which device are you referring to? This attribute is bound to the device
> > identified by the WMI GUID, and should be independent from the controller or any
> > thunderbolt connected physical device.
> 
> I refer to "wdev->dev" whatever that is. That device has been created
> long time before this driver is probed and thus userspace already got
> the KOBJ_ADD uevent.
> 

Ah yes, I see - at the time of device_register. Thanks Mika.

-- 
Darren Hart
VMware Open Source Technology Center

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: [PATCH v2] Add driver to force WMI Thunderbolt controller power  status Darren Hart <dvhart@infradead.org> - 2017-09-11 11:50 +0200
  Re: [PATCH v2] Add driver to force WMI Thunderbolt controller power  status Mika Westerberg <mika.westerberg@linux.intel.com> - 2017-09-11 11:50 +0200
    Re: [PATCH v2] Add driver to force WMI Thunderbolt controller power  status Darren Hart <dvhart@infradead.org> - 2017-09-11 23:50 +0200

csiph-web