On Tue, Jan 31, 2023 at 02:27:51PM -0600, Rob Herring wrote: > On Tue, Jan 31, 2023 at 12:10 PM Saurabh Sengar > <ssengar@xxxxxxxxxxxxxxxxxxx> wrote: > > > > This set of patches expands the VMBus driver to include device tree > > support. > > > > The first two patches enable compilation of Hyper-V APIs in a non-ACPI > > build. > > > > The third patch converts the VMBus driver from acpi to more generic > > platform driver. > > > > Further to add device tree documentation for VMBus, it needs to club with > > other virtualization driver's documentation. For this rename the virtio > > folder to more generic hypervisor, so that all the hypervisor based > > devices can co-exist in a single place in device tree documentation. The > > fourth patch does this renaming. > > > > The fifth patch introduces the device tree documentation for VMBus. > > > > The sixth patch adds device tree support to the VMBus driver. Currently > > this is tested only for x86 and it may not work for other archs. > > I can read all the patches and see *what* they do. You don't really > need to list that here. I'm still wondering *why*. That is what the > cover letter and commit messages should answer. Why do you need DT > support? How does this even work on x86? FDT is only enabled for > CE4100 platform. HI Rob, Thanks for your comments. We are working on a solution where kernel is booted without ACPI tables to keep the overall system's memory footprints slim and possibly faster boot time. We have tested this by enabling CONFIG_OF for x86. I can add this info in cover letter in next version. Regards, Saurabh > > Rob
