From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Badhri Jagan Sridharan <badhri@google.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
USB <linux-usb@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] typec: tcpm: Do not disconnect link for self powered devices
Date: Fri, 14 Sep 2018 12:54:40 +0300 [thread overview]
Message-ID: <20180914095440.GF19329@kuha.fi.intel.com> (raw)
In-Reply-To: <CAPTae5JVv0F_9mrXSTxmB2n9A9fJvcakwC0AKV6GbB+6Y79rGg@mail.gmail.com>
Hi,
On Thu, Sep 13, 2018 at 04:16:08PM -0700, Badhri Jagan Sridharan wrote:
> > > You do need to introduce a new device property already. Then read the
>
> This would be part of usb-connector binding. right ?
Yes, that is probable the correct place for that. It's not tcpm/tcpci
specific.
But I don't think it's Type-C specific either. Perhaps it should
go under "Optional Properties" instead of "Optional properties for
usb-c-connector"?
Thanks,
--
heikki
prev parent reply other threads:[~2018-09-14 9:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 2:11 [PATCH 1/2] typec: tcpm: Do not disconnect link for self powered devices Badhri Jagan Sridharan
2018-09-13 2:11 ` [PATCH 2/2] typec: tcpm: Add option to maintain current limit at Vsafe5V Badhri Jagan Sridharan
2018-09-13 6:39 ` Jack Pham
2018-09-13 13:43 ` Badhri Jagan Sridharan
2018-09-13 13:45 ` Badhri Jagan Sridharan
2018-09-13 17:07 ` Jack Pham
2018-09-13 23:38 ` Badhri Jagan Sridharan
2018-09-14 18:42 ` Jack Pham
2018-09-28 22:44 ` Badhri Jagan Sridharan
2018-09-13 13:24 ` [PATCH 1/2] typec: tcpm: Do not disconnect link for self powered devices Heikki Krogerus
2018-09-13 17:51 ` Guenter Roeck
2018-09-13 23:16 ` Badhri Jagan Sridharan
2018-09-14 9:54 ` Heikki Krogerus [this message]
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=20180914095440.GF19329@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=badhri@google.com \
--cc=gregkh@linuxfoundation.org \
--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 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).