Hi Mark, Rob
Thank you for your feedback
for example, test-cpu : silent Component, silent DAI test-cpu-vn : verbose Component, silent DAI test-cpu-nv : silent Component, verbose DAI test-cpu-vv : verbose Component, verbose DAI
Should these be runtime rather than binding options? Or at least properties rather than something that's part of the compatible. It doesn't feel right to have flags like that in the compatible at any rate, and if we're making fixed DTs for test purposes (eg, to run in qemu as part of a testsuite) it's no more difficult to use properties.
I'm not sure if Rob has thoughts on the base concept of such virtual for test bindings but they do seem like something that might be useful.
I'm assuming that "verbose" version will be used for test/debug purpose, and it is needed for boot-time too. Thus, switching it runtime is unfortunately not good.
I'm OK to use flag property for it if DT rule/maintainer was OK.
Thank you for your help !!
Best regards --- Kuninori Morimoto