Currently it's just "dontcare/yes"...

Ideally you'd be able as an integrator to use something like:

 logo = no;

or

 logo = yes;

And have the correct validation happen. Currently validation only checks yes cases.

By default features should be left "unset", e.g. it's not important for the build, any default is good. Meaning that whether tinyconfig is included or not is likely to make features default to no, and conversely if not enabled, likely to default to enabled.

Some systems may want to force enable or force disable features. E.g. debug features, framebuffer consoles, in end-user products (even if somewhat user hostile to do so).