linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shah, Nehal-bakulchandra" <nehal-bakulchandra.shah@amd.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: linux-iio <linux-iio@vger.kernel.org>,
	linux-usb@vger.kernel.org, Jagadish.Hadimani@amd.com
Subject: Re: ucsi and DRD controller interaction
Date: Mon, 27 Apr 2020 19:45:07 +0530	[thread overview]
Message-ID: <b139b18c-0452-d717-856e-14b9dd03910a@amd.com> (raw)
In-Reply-To: <20200427120032.GA2351955@kuha.fi.intel.com>

Hi Heikki,

On 4/27/2020 5:30 PM, Heikki Krogerus wrote:
> On Wed, Apr 22, 2020 at 08:23:54PM +0530, Shah, Nehal-bakulchandra wrote:
>>> Can you still influence what goes to your ACPI tables, or are we
>>> talking about products that are already on the market?
>> Yes still it is in development phase so i can work out with BIOS team for the same. When you say description of connection ,something like this should be part of _DSD method right? (i.e from below dts
>> to _DSD of ACPI)
>>
>>  usb_con: connector {
>> compatible = "usb-c-connector";
>>  label = "USB-C";
>>  data-role = "dual";
>>  power-role = "dual";
>>  try-power-role = "sink";
>>  source-pdos = <PDO_FIXED(5000, 500, PDO_FIXED_USB_COMM)>;
>>  sink-pdos = <PDO_FIXED(5000, 500, PDO_FIXED_USB_COMM)
>>  PDO_VAR(5000, 5000, 1000)>;
>>  op-sink-microwatt = <10000000>;
>>  };
> Here's how the ASL for the _DSD should look like. I don't know how
> are all these components placed on your platform, so I'm just assuming
> that your I2C host is under PCI0, as well as your DWC3 controller.
> It's just an example, but hopefully you get the point from it:
>
> /*
>  * I2C1 is the I2C host, and PDC1 is the USB PD Controller (I2C slave device).
>  */
> Scope (\_SB.PCI0.I2C1.PDC1)
> {
>         /* Each connector should have its own ACPI device entry (node). */
>         Device (CON0)
>         {
>                 Name (_ADR, 0)
>
>                 Name (_DSD, Package () {
>                     ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
>                     Package() {
>                         Package () {"usb-role-switch", \_SB.PCI0.DWC3},
>                     }
>                 })
>         }
> }
>
> So that property "usb-role-switch" has reference to the DWC3 node as
> its value. That's what we are after here. If you have that property,
> the subsystem will find the USB controller for you.
>
> If you need for example the properties for the roles, then the _DSD
> would look like this:
>
> Name (_DSD, Package () {
>     ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
>     Package() {
>         Package () {"usb-role-switch", \_SB.PCI0.DWC3},
>         Package () {"power-role", "dual"},
>         Package () {"data-role", "dual"},
>     }
> })
>
> and so on...
>
>
> Thanks,

Thanks for the details so this will enable the role switch  for drd controller. Now for UCSI driver to call the role make functions it needs the reference of the same switch reference,

so for that do i have to use device_get_named_child_node(dev,"CON0"), in UCSI Driver?

Thanks

Nehal Shah




  reply	other threads:[~2020-04-27 14:15 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
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 [this message]
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=b139b18c-0452-d717-856e-14b9dd03910a@amd.com \
    --to=nehal-bakulchandra.shah@amd.com \
    --cc=Jagadish.Hadimani@amd.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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).