Hi Heikki, On Thu, Oct 28, 2021 at 12:36 AM Heikki Krogerus <heikki.krogerus@xxxxxxxxxxxxxxx> wrote: > > Hi, > > On Wed, Oct 27, 2021 at 06:03:08PM -0700, Prashant Malani wrote: > > Why is USBPDDEV_SUBMIT_MESSAGE different from USBPDDEV_SET_MESSAGE? > > Shouldn't "setting" a PDO or property automatically "submit" it (using TCPM > > or whatever interface is actually performing the PD messaging) if > > appropriate (e.g Source Caps?). Is there a situation where one would > > want to "set" a property but not "send" it? > > > > It seems to me that the two can be combined into 1 rather than having > > a separate command just for ports. > > USBPDDEV_SUBMIT_MESSAGE you use to send message directly to the partner. > > USBPDDEV_SET_MESSAGE is meant to be used to store the values to a > cached message that the port manager should use next time there is > communication, but it does not send the message to the partner. So you > can use it even when there is no connection with a port, for example, > to store the values like the initial USB mode that should be used by > setting the EUDO message. Maybe the ioctl should be named > USBPDDEV_STORE_MESSAGE... I used "set" because it is sort of a > counterpart to USBPDDEV_GET_MESSAGE. > > There is an explanation in include/uapi/linux/usb/pd_dev.h, please > check it. Thanks for the further clarification. I guess I still don't see enough need to differentiate SET/STORE from SUBMIT; is there a situation where one would want to store the source/sink caps for a port, but not send/submit them immediately? When a partner is not connected to a port, a set would automatically just update the cached values and not perform a "submit" (since there is nothing to submit to). Perhaps there are (situations which require separate store and submit), but I'm unable to come up with one on the spot. I'm curious also what you think about the idea with > USBPDDEV_CONFIGURE. It is indeed interesting. It seems like the specific interface for this needs to be fleshed out more (will we define a standard set of features which can be represented by the |flags| and made configurable?). At present I can't think of TCPM features which we'd want to toggle at runtime, but I'm looking at it from a Chrome OS perspective, so could be missing a bunch of use cases. BTW, does poll work with this character device? Best regards,
