From: Oliver Neukum <oneukum@suse.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Badhri Jagan Sridharan <badhri@google.com>,
Greg KH <gregkh@linuxfoundation.org>,
Bin Gao <bin.gao@linux.intel.com>,
Felipe Balbi <felipe.balbi@linux.intel.com>,
Guenter Roeck <linux@roeck-us.net>,
LKML <linux-kernel@vger.kernel.org>,
USB <linux-usb@vger.kernel.org>
Subject: Re: [PATHCv10 1/2] usb: USB Type-C connector class
Date: Wed, 16 Nov 2016 10:39:27 +0100 [thread overview]
Message-ID: <1479289167.2000.8.camel@suse.com> (raw)
In-Reply-To: <20161116093035.GA30235@kuha.fi.intel.com>
On Wed, 2016-11-16 at 11:30 +0200, Heikki Krogerus wrote:
> On Tue, Nov 15, 2016 at 04:19:10PM -0800, Badhri Jagan Sridharan wrote:
> > Is that too costly to have ?
>
> Greg, could you give your opinion. In this case we do have attribute
> files that the user space can poll. Data role is the USB data role, so
> host or device, and it can change for example if the partner executes
> a swap. The same can happen with the power role.
IMHO the uevent is cheaper. User space cannot just poll without further
infrastructure. A task needs to run to poll. A uevent can be handled
through established infrastructure.
Sure from a kernel level it is the heavier gun, but I think this is
the wrong angle of looking at this issue.
Regards
Oliver
next prev parent reply other threads:[~2016-11-16 9:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 11:16 [PATHCv10 0/2] USB Type-C Connector class Heikki Krogerus
2016-09-19 11:16 ` [PATHCv10 1/2] usb: USB Type-C connector class Heikki Krogerus
2016-11-14 9:51 ` Greg KH
2016-11-14 12:32 ` Heikki Krogerus
2016-11-14 14:11 ` Greg KH
2016-11-14 14:39 ` Heikki Krogerus
2016-11-14 15:08 ` Greg KH
2016-11-14 14:34 ` Guenter Roeck
2016-11-16 8:47 ` Oliver Neukum
2016-11-14 20:46 ` Guenter Roeck
2016-11-15 7:07 ` Greg KH
2016-11-15 9:25 ` Guenter Roeck
2016-11-16 0:19 ` Badhri Jagan Sridharan
2016-11-16 9:30 ` Heikki Krogerus
2016-11-16 9:39 ` Oliver Neukum [this message]
2016-11-16 9:49 ` Greg KH
2016-11-16 11:09 ` Heikki Krogerus
2016-11-16 11:27 ` Oliver Neukum
2016-11-16 14:30 ` Badhri Jagan Sridharan
2016-11-16 14:43 ` Heikki Krogerus
2016-11-16 15:20 ` Heikki Krogerus
2016-11-16 15:25 ` Badhri Jagan Sridharan
2016-11-16 15:31 ` Greg KH
2016-11-17 8:28 ` Heikki Krogerus
2016-09-19 11:16 ` [PATHCv10 2/2] usb: typec: add driver for Intel Whiskey Cove PMIC USB Type-C PHY Heikki Krogerus
2016-11-10 21:36 ` [PATHCv10 0/2] USB Type-C Connector class Guenter Roeck
2016-11-11 11:04 ` Heikki Krogerus
2016-11-14 7:46 ` Greg KH
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=1479289167.2000.8.camel@suse.com \
--to=oneukum@suse.com \
--cc=badhri@google.com \
--cc=bin.gao@linux.intel.com \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.