alt Hacker NewsIt sure is. You can just spec it to require a USB-C 7.5W/15W source and then you can gate the operation behind a simple analog circuit and Bob's your uncle. No such way with microUSB until you implement BC1.2, which you don't have to support with USB-C (though it's certainly nice when you do).
> but then you'd be wrong
Not at all, it would just miss signaling it's not compatible with, just like with all sorts of proprietary signaling protocols out there. The point is that with microUSB you have no other way, you have to implement BC1.2 (or some proprietary spec) which is often more complex than a comparator on CC line.
Yes, that way your type-c device will also be refusing to work with many sources that can provide enough power, that is with anything advertising USB default power.
For proper detection of actually underpowered source without awful lot of false negative results, you always need BC1.2. You're just adding type-c CC pins circuitry on top maybe to detect what power is availabe in non-default-usb-power scenarios. If you just use CC pins for detection, a lot of your users will not like you, and will not understand why they can't charge your type-c port featuring smartphone or whatever with a perfectly capable 2.1A/5V charger connected via USB A-C cable.
Been there done that.