From: Mika Westerberg <mika.westerberg@intel.com>
To: Mario.Limonciello@dell.com
Cc: luto@kernel.org, amir.jer.levy@intel.com,
gregkh@linuxfoundation.org, andreas.noever@gmail.com,
bhelgaas@google.com, corbet@lwn.net,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
thunderbolt-linux@intel.com, tomas.winkler@intel.com,
xiong.y.zhang@intel.com
Subject: Re: [PATCH v8 3/8] thunderbolt: Communication with the ICM (firmware)
Date: Tue, 20 Dec 2016 10:09:16 +0200 [thread overview]
Message-ID: <20161220080916.GV1460@lahna.fi.intel.com> (raw)
In-Reply-To: <05d9c1db67af410981bbb9672071a237@ausx13mpc120.AMER.DELL.COM>
On Mon, Dec 19, 2016 at 05:21:39PM +0000, Mario.Limonciello@dell.com wrote:
> Dell - Internal Use - Confidential
>
> >
> > There is small problem, though. On non-Apple systems the host controller only
> > appears when something is connected to thunderbolt ports. So the char device
> > would not be there all the time. However, I think we can still notify the
> > userspace by sending an extra uevent when we detect there is a PCIe device or
> > inter-domain connection plugged in.
> >
>
> Why couldn't you just create it the first time a device is plugged into a Thunderbolt
> port and leave it until the module is cleaned up? If the host controller goes to sleep
> an event could be sent to the daemon to let it know it disappeared and not to expect
> data on the char device for now, but leave the node around.
We don't do that for USB memory sticks (or any other removable media)
either - once you disconnect the device the nodes are also removed. I
suppose same goes with USB network adapters, which is closest to
thunderbolt networking I can think of.
next prev parent reply other threads:[~2016-12-20 8:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 14:44 [PATCH v8 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking Amir Levy
2016-09-28 14:44 ` [PATCH v8 1/8] thunderbolt: Macro rename Amir Levy
2016-09-28 14:44 ` [PATCH v8 2/8] thunderbolt: Updating the register definitions Amir Levy
2016-09-28 14:44 ` [PATCH v8 3/8] thunderbolt: Communication with the ICM (firmware) Amir Levy
2016-12-02 1:21 ` Andy Lutomirski
2016-12-19 12:24 ` Mika Westerberg
2016-12-19 17:21 ` Mario.Limonciello
2016-12-20 8:09 ` Mika Westerberg [this message]
2016-09-28 14:44 ` [PATCH v8 4/8] thunderbolt: Networking state machine Amir Levy
2016-09-28 14:44 ` [PATCH v8 5/8] thunderbolt: Networking transmit and receive Amir Levy
2016-09-28 14:44 ` [PATCH v8 6/8] thunderbolt: Kconfig for Thunderbolt Networking Amir Levy
2016-09-28 14:44 ` [PATCH v8 7/8] thunderbolt: Networking doc Amir Levy
2016-09-28 14:44 ` [PATCH v8 8/8] thunderbolt: Adding maintainer entry Amir Levy
2016-09-30 5:55 ` [PATCH v8 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking David Miller
2016-09-30 6:30 ` Greg KH
2016-09-30 6:40 ` David Miller
2016-09-30 8:37 ` Levy, Amir (Jer)
2016-09-30 8:50 ` gregkh
2016-10-21 14:57 ` Mario.Limonciello
2016-10-27 15:51 ` Andreas Noever
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=20161220080916.GV1460@lahna.fi.intel.com \
--to=mika.westerberg@intel.com \
--cc=Mario.Limonciello@dell.com \
--cc=amir.jer.levy@intel.com \
--cc=andreas.noever@gmail.com \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=luto@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=thunderbolt-linux@intel.com \
--cc=tomas.winkler@intel.com \
--cc=xiong.y.zhang@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;
as well as URLs for NNTP newsgroup(s).