From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: "Shah, Nehal-bakulchandra" <nehal-bakulchandra.shah@amd.com>
Cc: linux-iio <linux-iio@vger.kernel.org>, linux-usb@vger.kernel.org
Subject: Re: ucsi and DRD controller interaction
Date: Tue, 21 Apr 2020 10:43:53 +0300 [thread overview]
Message-ID: <20200421074353.GE3768833@kuha.fi.intel.com> (raw)
In-Reply-To: <26823688-3b9c-5869-bcb6-4d6e5dcd77bc@amd.com>
Adding linux-usb mailing list.
On Mon, Apr 20, 2020 at 07:09:17PM +0530, Shah, Nehal-bakulchandra wrote:
> Hi Heikki ,
>
> I need some pointer from you, so in a system where I have UCSI driver for DRD
> Controller, then how call stack will be?
>
> I am unable to comprehend the flow from UCSI infrastructure to DRD controller
> code base.
Do you need to tell the negotiated data role to your USB controller
driver from the UCSI driver? For that we would need to know which USB
controller, or more precisely, which USB port is connected to the
USB Type-C connector in question.
That would require ACPI tables to be able to describe the connection
between the USB Type-C connector and the USB port (and the connection
between DisplayPort and the USB Type-C connector etc.). Unfortunately
there is currently no documented way of doing that, however, there is
a proposal for a document the defines how the USB Type-C connectors
should be described in ACPI in general. The proposal does consider
this problem as well. For this the solution is to use _DSD device
properties "usb2-port" and "usb3-port" that have references to the
correct USB port nodes as values.
Which USB controller are you using btw?
thanks,
--
heikki
next prev parent reply other threads:[~2020-04-21 7:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 13:39 ucsi and DRD controller interaction Shah, Nehal-bakulchandra
2020-04-21 7:43 ` Heikki Krogerus [this message]
2020-04-21 13:53 ` Shah, Nehal-bakulchandra
2020-04-22 11:00 ` Heikki Krogerus
2020-04-22 13:07 ` Shah, Nehal-bakulchandra
2020-04-22 14:28 ` Heikki Krogerus
2020-04-22 14:53 ` Shah, Nehal-bakulchandra
2020-04-27 12:00 ` Heikki Krogerus
2020-04-27 14:15 ` Shah, Nehal-bakulchandra
2020-04-29 12:43 ` Heikki Krogerus
2020-04-29 13:03 ` Heikki Krogerus
2020-04-29 20:02 ` Shah, Nehal-bakulchandra
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=20200421074353.GE3768833@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nehal-bakulchandra.shah@amd.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