> diff --git a/drivers/i2c/busses/i2c-nvidia-gpu.c
> b/drivers/i2c/busses/i2c-nvidia-gpu.c
> index 1c8f708f212b..9d347583f8dc 100644
> --- a/drivers/i2c/busses/i2c-nvidia-gpu.c
> +++ b/drivers/i2c/busses/i2c-nvidia-gpu.c
> @@ -175,6 +175,7 @@ static int gpu_i2c_master_xfer(struct i2c_adapter *adap
> + /* runtime resume ccgx client so that it can see for any
> + * connector change event. Old ccg firmware has known
> + * issue of not triggering interrupt when a device is
> + * connected to runtime resume the controller.
> + */
Check coding style for comments.
BTW how
Thanks to the new firmware and its more meaningful Sense Key, I finally
realized that the hard-drive was simply "locked" as in the BIOS Hard-
Disk Password Lock feature.
Therefore this is not a bug, the UAS driver is working fine with the
HDD enclosure and the issue was simply a matter of unlockin
