[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d60e9b7c-fdd5-2b5e-a449-d796718fb95f@linaro.org>
Date: Wed, 1 Feb 2023 18:15:23 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Saurabh Singh Sengar <ssengar@...ux.microsoft.com>,
Rob Herring <robh@...nel.org>
Cc: krzysztof.kozlowski+dt@...aro.org, kys@...rosoft.com,
haiyangz@...rosoft.com, wei.liu@...nel.org, decui@...rosoft.com,
daniel.lezcano@...aro.org, tglx@...utronix.de,
virtualization@...ts.linux-foundation.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-hyperv@...r.kernel.org, mikelley@...rosoft.com,
ssengar@...rosoft.com
Subject: Re: [PATCH v2 0/6] Device tree support for Hyper-V VMBus driver
On 01/02/2023 17:34, Saurabh Singh Sengar wrote:
>> Also see my comment on v1 about running DT validation on your dtb. I'm
>> sure running it would point out other issues. Such as the root level
>> comaptible string(s) need to be documented. You need cpu nodes,
>> interrupt controller, timers, etc. Those all have to be documented.
>
> I will be changing the parent node to soc node as suggested by Krzysztof
> in other thread.
>
> soc {
> #address-cells = <2>;
> #size-cells = <2>;
>
> vmbus@...000000 {
> #address-cells = <2>;
> #size-cells = <1>;
> compatible = "Microsoft,vmbus";
> ranges = <0x00 0x00 0x0f 0xf0000000 0x10000000>;
> };
> };
>
> This will be sufficient.
It will be ok for the example, but will not be ok for supporting your
use case. Please solve all the points from Rob's comment above. Where is
their documentation?
Best regards,
Krzysztof
Powered by blists - more mailing lists