Add value name "USB-C" for value 0x1b of VCP code 0x60 (input source)

[aryoda]

My Dell U3818DW supports DisplayPort over USB-C as input source value 0x1b but the input source is not yet known to ddcutil:

   Feature:  0x60 (Input Source)
      Values:
         0x0f: DisplayPort-1
         0x11: HDMI-1
         0x12: HDMI-2
         0x1b: (null)

I am not sure if this is DELL specific...

@ALL Can users of other displays please confirm (or reject) my observation that 0x1b is the standard value for (DisplayPort over) USB-C?

Does anybody know an official name for this value?

Next step would be to add a name for this value to ddcutil, "USB-C" or "DP over USB-C" or "DP over USB"...

[rockowitz]

It will indeed be interesting to see if this is a common usage.  It may well be Dell specific.  I will be surprised if there is cross-manufacturer agreement on the use of this code.

This may be a good use for user supplied feature definitions. Release 0.9.3 reworked the ddcutil internals to allow for them. It also incorporated required API changes, so that hopefully when the facility is fleshed out any additional changes will be upward compatible.   I had thought of the facility as a way to provide complete definitions for features in the manufacturer specific range.  At this point it's not possible to add a single value definition, the entire description of feature x60 would have to be replaced.   If you want to play with it I can send you details.

On 12/29/18 4:49 AM, aryoda wrote:

My Dell U3818DW supports DisplayPort over USB-C as input source value 0x1b but the input source is not yet known to ddcutil:

|Feature: 0x60 (Input Source) Values: 0x0f: DisplayPort-1 0x11: HDMI-1 0x12: HDMI-2 0x1b: (null) |

I am not sure if this is DELL specific...

Can users of other display please confirm (or reject) my observation that |0x1b| is the standard value for (DisplayPort over) |USB-C|?

Does anybody know an official name for this value?

Next step would be to add a name for this value to |ddcutil|, "USB-C" or "DP over USB-C" or "DP over USB"...

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/rockowitz/ddcutil/issues/70, or mute the thread https://github.com/notifications/unsubscribe-auth/ANhsbnlIQWUaCeLX8cxNuUVBdHKxgHogks5u9zrBgaJpZM4ZkgLu.

[aryoda]

Using the user-supplied feature definitions of v0.9.3 or higher is a very good use case for that.

I am currently doing my "homework" (example implementation of a C++ ddcutil API...) but two weeks of school holidays are melting like snow - esp. with C++ ;-)

I will examine v0.9.3 after that (currently I am using a "pinned" git submodule with v0.9.2).

[prototux]

On my U2419HC (so, one generation newer) it's also using 0x1B for the USB-C input source, so, i don't know if it's consistent across OEMs, but at least, it seems to be consistent between dell monitor generations.

[rockowitz]

Thanks for taking the time to let me know.

Sanford

On 09/07/2019 07:53 PM, Jason F. wrote:

On my U2419HC (so, one generation newer) it's also using 0x1B for the USB-C input source, so, i don't know if it's consistent across OEMs, but at least, it seems to be consistent between dell monitor generations.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rockowitz/ddcutil/issues/70?email_source=notifications&email_token=ADMGY3W5TLB2I46CSFEKYFDQIQ5G3A5CNFSM4GMSALXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6FEOYQ#issuecomment-529155938, or mute the thread https://github.com/notifications/unsubscribe-auth/ADMGY3U4TNRQRYUU27N4LZDQIQ5G3ANCNFSM4GMSALXA.

[SumDum]

Hi Sanford, On a ViewSonic VP3881 USB-C is 0x17

   Feature: 60 (Input Source)
      Values:
         0f: DisplayPort-1
         11: HDMI-1`
         12: HDMI-2
         17: Unrecognized value

So unfortunately no, not common usage.

[rockowitz]

Thanks for posting this information.

On 4/18/20 8:16 AM, SumDum wrote:

Hi Sanford, On a ViewSonic VP3881 USB-C is 0x17

|Feature: 60 (Input Source) Values: 0f: DisplayPort-1 11: HDMI-1` 12: HDMI-2 17: Unrecognized value |

So unfortunately no, not common usage.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rockowitz/ddcutil/issues/70#issuecomment-615856610, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADMGY3SILP3MUBSL4AD7OUTRNGK2PANCNFSM4GMSALXA.

[madmalkav]

On a Lenovo Thinkvision P44W-10 , 0x14 is for the port labeled USB Type-C 10G (DP 1.4 Alternate Mode compatible) and 0x13 for the port labeled USB Type-C 5G (DP 1.2 Alternate Mode compatible).

[attah]

My Dell P3222QE also uses 0x1b for USB-C. But my Asus MB16AC calls its single UCB-C input 0x11, aka HDMI-1 :( Thanks for this great tool!

[rockowitz]

For those unaware of it, the User Defined Features facility can be used to address variations like these.

[aryoda]

I'd suggest to close this issue (perhaps incl. an attached example user-defined features file to "solve" the issue)...

[bbkr]

On a ViewSonic VP2785-4K USB-C is 0x17.