Thank you for your review, Krzysztof. I apologize for the delay in my response.
>> What is a connection ID and why it cannot be inferred from existing >> system API? The connection-id determines which hypervisor communication channel the guest should use to talk to the VMBus host. Reading from DeviceTree allows platforms to specify their preferred communication channel, making it more flexible (I will add this detail in the commit message). Presently, this value is hardcoded and there is no existing API to read it. >> There's a reason why you have here generic property - this is generic >> and/or discoverable and/or whatever software interface. Adding now more >> properties, just because you made it generic, is not the way. Presently the value is hardcoded and we want to provide a functionality to the user to specify their prefered communication channel. This is a virtualized hardware property for us. >> Drop | I will remove "|". >> Missing constraints, defaults, if this stays, but frankly speaking it >> looks really not appropriate, considering lack of any explanation in the >> binding or in commit msg. I will add constraints, and defaults. Please let me know if there are any other issues that I should fix with the next version of the patch and thank you again for the review. Regards, Hardik
