Hacker News Reader

IMHO it would be better to capitalize the OTG structure field names according to the standard. This would turn "avalidoven" into "AvalidOvEn", which makes much more sense: it's the "A-side session valid override enable bit", which allows the software to override the "Avalid" signal with the value from AvalidOvVal.

Also, this needs a (2017) tag.

View on HN

>which allows the software to override the "Avalid" signal with the value from AvalidOvVal.

How is "Avalid" any more meaningful though?

"The AValid signal is used to indicate if the session for an A-peripheral is valid. This signal is 1b when Vbus is above 2V"

They could use some better naming.

How is your comment even remotely relevant to the post topic?

The post discusses bit-fields in the context of implementing some part of the USB OTG specification. Author makes a joke about USB having bits for “a valid oven”.

Read the article. At the end the author says

> By the way it's nice to know that the USB protocol has a bit to indicate "a valid oven". I wonder when that is used.

The bit fields he uses as an example related to USB protocol implementation.

Reply on news.ycombinator.com