From: Oliver Neukum <oneukum@suse.com>
To: Guenter Roeck <groeck@chromium.org>
Cc: Felipe Balbi <felipe.balbi@linux.intel.com>,
Bin Gao <bin.gao@intel.com>,
Chandra Sekhar Anagani <chandra.sekhar.anagani@intel.com>,
Pranav Tipnis <pranav.tipnis@intel.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
Bruce Ashfield <bruce.ashfield@windriver.com>
Subject: Re: [RFC PATCH v2 0/4] Type-C Port Manager
Date: Thu, 18 Aug 2016 09:43:15 +0200 [thread overview]
Message-ID: <1471506195.2157.3.camel@suse.com> (raw)
In-Reply-To: <1471471476-53251-1-git-send-email-groeck@chromium.org>
On Wed, 2016-08-17 at 15:04 -0700, Guenter Roeck wrote:
> The following series of patches implements a USB Type-C Port Manager
> using the pending USB Type-C class code as basis. The code is still
> WIP,
> but I think it is important to get feedback from the community at this
> point.
Hi,
a question on design. What happens if the system wants to suspend while
we are in the middle of a power negotiation?
Regards
Oliver
next prev parent reply other threads:[~2016-08-18 7:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 22:04 [RFC PATCH v2 0/4] Type-C Port Manager Guenter Roeck
2016-08-17 22:04 ` [RFC PATCH v2 1/4] usb: typec: Do not check if connected when setting roles Guenter Roeck
2016-08-17 22:04 ` [RFC PATCH v2 2/4] usb: typec: Do not update modes in class driver Guenter Roeck
2016-08-17 22:04 ` [RFC PATCH v2 3/4] usb: typec: USB Type-C Port Manager (tcpm) Guenter Roeck
2016-08-17 22:04 ` [RFC PATCH v2 4/4] usb: typec: Type-C Port Controller Interface driver (tcpci) Guenter Roeck
2016-08-18 7:43 ` Oliver Neukum [this message]
2016-08-18 13:17 ` [RFC PATCH v2 0/4] Type-C Port Manager Guenter Roeck
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=1471506195.2157.3.camel@suse.com \
--to=oneukum@suse.com \
--cc=bin.gao@intel.com \
--cc=bruce.ashfield@windriver.com \
--cc=chandra.sekhar.anagani@intel.com \
--cc=felipe.balbi@linux.intel.com \
--cc=groeck@chromium.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pranav.tipnis@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 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.