lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 16 Apr 2017 21:28:01 +0200
From:   Mats Karrman <mats.dev.list@...il.com>
To:     Heikki Krogerus <heikki.krogerus@...ux.intel.com>
Cc:     Guenter Roeck <linux@...ck-us.net>,
        Felipe Balbi <felipe.balbi@...ux.intel.com>,
        linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: usb: typec: Missing link for altmode active store

Hello Heikki,

I'm working with the new typec class code and have run into a problem.
The struct typec_capability defines a callback function as:

int (*activate_mode)(const struct typec_capability *, int mode, int activate);

 From the capability I can get to the corresponding port/plug/partner private
data and to the svid's registered for that device.
The mode argument tells me which of the modes registered for a svid that is to
be (de)activated.
However, as far as I can tell there is no way for activate_mode() to find out
which svid is in question without an additional argument, e.g. "u16 svid".

Please correct me if I'm wrong.

BR,
Mats

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ