"--pdports" returns InvalidCommand

[SkaveRat]

FW13 - Intel 13gen

I get the following output in 0.6.1:

USB-C Port 0 (Right Back):
  Role:          Sink
  Charging Type: PD
  Voltage Now:   19.584 V, Max: 20.0 V
  Current Lim:   3000 mA, Max: 3000 mA
  Dual Role:     Charger
  Max Power:     60.0 W
USB-C Port 1 (Right Front):
  Role:          Source
  Charging Type: None
  Voltage Now:   5.0 V, Max: 0.0 V
  Current Lim:   0 mA, Max: 1500 mA
  Dual Role:     Charger
  Max Power:     0.0 W
USB-C Port 2 (Left Front):
  Role:          Source
  Charging Type: None
  Voltage Now:   5.0 V, Max: 0.0 V
  Current Lim:   0 mA, Max: 1500 mA
  Dual Role:     Charger
  Max Power:     0.0 W
USB-C Port 3 (Left Back):
  Role:          Disconnected
  Charging Type: None
  Voltage Now:   0.0 V, Max: 0.0 V
  Current Lim:   0 mA, Max: 1500 mA
  Dual Role:     Charger
  Max Power:     0.0 W

But this command breaks in 0.6.2:

USB-C Port 0:
[ERROR] EC Response Code: InvalidCommand
USB-C Port 1:
[ERROR] EC Response Code: InvalidCommand
USB-C Port 2:
[ERROR] EC Response Code: InvalidCommand
USB-C Port 3:
[ERROR] EC Response Code: InvalidCommand

Looking at the changelog, this happens due to the added --pdports-chromebook flag (which does work as expected), but I feel like this is a bit confusing, if you're not deep into the internals of framework and you know that there's a chromebook chip inside

[JohnAZoidberg]

Yeah i switched to a new host command that's not supported on every hardware.
I renamed the old --pdports command to --pdports-chromebook.
It returns misleading data, so I don't suggest to rely on it too much.

We don't have a "chromebook chip" inside, it's Chrome EC firmware. But our PD architecture is quite different, so their PD related host commands don't return all data.
That's why I switched to our custom command, which unfortuately is not (yet) supported on all generations.