Re: [PATCH 1/6] dt-bindings: Add Bao IPC shared memory driver binding
Krzysztof Kozlowski <[email protected]>
| Newsgroups | org.infradead.lists.linux-riscv,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-doc,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On 07/08/2026 09:41, João Peixoto wrote: >>> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml >>> index c7591b2aec2a..c047fbd6b91a 100644 >>> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml >>> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml >>> @@ -223,6 +223,8 @@ patternProperties: >>> description: Shenzhen AZW Technology Co., Ltd. >>> "^baikal,.*": >>> description: BAIKAL ELECTRONICS, JSC >>> + "^bao,.*": >>> + description: Bao Hypervisor >> Vendor prefixes are for companies. What is the company here? What is >> stock ticker or website? >> >> >>> "^bananapi,.*": >>> description: BIPAI KEJI LIMITED >>> "^beacon,.*": > "bao" is the Bao Project, an open-source static-partitioning hypervisor > (https://github.com/bao-project), not a single company - analogous to the > existing "qemu" and "virtio" prefixes, which likewise name a software > interface rather than a vendor. I have updated the vendor-prefixes entry > accordingly. If you would rather namespace this under the maintaining Software components do not get bindings, so entire binding is not applicable really. You control your hypervisor and driver so use fully SW communication channels instead of embedding SW into DT. Best regards, Krzysztof _______________________________________________ linux-riscv mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-riscv