From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 170E8757EA; Thu, 25 Dec 2025 08:57:38 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766653059; cv=none; b=qd9NQuMnBhGLa3uAE+zr+KTYFSZ7sn3W5nTnmBtkZIxNs0CSkiisMf1UkC5CQ3B1kOJ/LqkiKhvqs1cXX/9vLFtRca9HpYyIr7ZtDBLKDJEOl5i/5drpIMFZk96yV1R7phzqsvyBRYTNfHT03ZARpGOSf5R5Am+HfXIguaPQSZA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766653059; c=relaxed/simple; bh=JbAlLOSZ4lp2eqLIqN854RLD8F4hVgelu+B0u8PEklQ=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=IEtAidjCWKN+BdBIxyZ+Ay8+ICe5TD9X9x71rOOHNet/IJc/cAfhfD/ZapPtXFpJpy2wMeXj9wZlctJlNq1p7R8sGMMbBkMj1NIBgVu0cKJXWARVV53k7+j0RTvNTEGTSaOSJPAk+QmJfRvsjPY8mBHcSIH0FZCb03NFkXtCLzk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=lnfOTwU4; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="lnfOTwU4" Received: by smtp.kernel.org (Postfix) with ESMTPSA id B75CCC4CEF1; Thu, 25 Dec 2025 08:57:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1766653058; bh=JbAlLOSZ4lp2eqLIqN854RLD8F4hVgelu+B0u8PEklQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=lnfOTwU4+apIYrQlSwNee5D+OFUc0kyNaJ05pnV9yb/rrNk++IRoErqOxaNYxdZEa Ec47AbiAW7GQrAOPpJxhwUyFk3GwlFQEQRfhgssjeGhSVa6wLU6dwBw60W8FM84mVs yC8zVz72FqK43BBWTQVtMlie6qtYNv26lZmyti6L1jM68UsNjdv8TR7S+FJAVtnMRU J2NQ9Ww5JUohaY9eX0JlF3EXzJL3uDIU6lAvxuwzBAx5Jd67BAjgVB/99gI6165R20 zZg33ZqlOpxS9F+fIxawiBJlEPxthN07AQhbDtTL74uRxkodg76ILOdLMuqVRHNRnr qrSppllPQyGpQ== Date: Thu, 25 Dec 2025 09:57:34 +0100 From: Krzysztof Kozlowski To: joaopeixoto@osyx.tech Cc: linux-kernel@vger.kernel.org, ajd@linux.ibm.com, alex@ghiti.fr, aou@eecs.berkeley.edu, bagasdotme@gmail.com, catalin.marinas@arm.com, conor+dt@kernel.org, corbet@lwn.net, dan.j.williams@intel.com, davidmcerdeira@osyx.tech, devicetree@vger.kernel.org, dev@kael-k.io, gregkh@linuxfoundation.org, haren@linux.ibm.com, heiko@sntech.de, jose@osyx.tech, kever.yang@rock-chips.com, krzk+dt@kernel.org, linux-arm-kernel@lists.infradead.org, linux@armlinux.org.uk, linux-doc@vger.kernel.org, linux-riscv@lists.infradead.org, maddy@linux.ibm.com, mani@kernel.org, nathan@kernel.org, neil.armstrong@linaro.org, palmer@dabbelt.com, pjw@kernel.org, prabhakar.mahadev-lad.rj@bp.renesas.com, robh@kernel.org, will@kernel.org Subject: Re: [PATCH 1/5] dt-bindings: Add Bao IPC shared memory driver binding Message-ID: <20251225-translucent-radical-coot-d3f9ee@quoll> References: <20251224135217.25350-1-joaopeixoto@osyx.tech> <20251224135217.25350-2-joaopeixoto@osyx.tech> Precedence: bulk X-Mailing-List: linux-doc@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <20251224135217.25350-2-joaopeixoto@osyx.tech> On Wed, Dec 24, 2025 at 01:52:13PM +0000, joaopeixoto@osyx.tech wrote: > From: Jo=C3=A3o Peixoto >=20 > This patch adds a Device Tree binding for the Bao IPC shared memory > device, which provides a standardized description of the hardware > interface used for inter-VM communication in Bao-based systems. >=20 All you emails bounced as spam, so you need tofix your email setup. I found this only via lore. > The binding documents the following properties: >=20 > - compatible: "bao,ipcshmem" > - reg: Memory region for the shared memory device > - id: Unique device identifier > - read-channel: [offset, size] for reading from the shared memory > - write-channel: [offset, size] for writing to the shared memory > - interrupts: Interrupts used by the device Irrelevant. Drop. >=20 > This enables kernel drivers and userspace tools to correctly > instantiate and configure Bao IPC shared memory devices based > on the DT description, facilitating efficient communication > between VMs. >=20 Irrelevant. Describe hardware. > Signed-off-by: Jo=C3=A3o Peixoto > --- > .../devicetree/bindings/bao/ipcshmem.yaml | 99 +++++++++++++++++++ > .../devicetree/bindings/vendor-prefixes.yaml | 2 + > 2 files changed, 101 insertions(+) > create mode 100644 Documentation/devicetree/bindings/bao/ipcshmem.yaml Filename matching compatible. >=20 > diff --git a/Documentation/devicetree/bindings/bao/ipcshmem.yaml b/Docume= ntation/devicetree/bindings/bao/ipcshmem.yaml > new file mode 100644 > index 000000000000..398ac610c29f > --- /dev/null > +++ b/Documentation/devicetree/bindings/bao/ipcshmem.yaml > @@ -0,0 +1,99 @@ > +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause > +%YAML 1.2 > +--- > +$id: "http://devicetree.org/schemas/bao/ipcshmem.yaml#" > +$schema: "http://devicetree.org/meta-schemas/core.yaml#" > + > +title: Bao IPC Shared Memory Device > + > +maintainers: > + - Jos=C3=A9 Martins > + - David Cerdeira > + - Jo=C3=A3o Peixoto > + > +description: | > + Shared memory based communication device for Bao hypervisor guests. > + It allows the kernel to interface with guests running under > + the Bao hypervisor, providing a character device interface > + for exchanging data through dedicated shared-memory regions. > + > +properties: > + compatible: > + const: "bao,ipcshmem" > + > + reg: > + description: | > + Memory resource for the shared memory device. > + maxItems: 4 > + type: array > + items: > + type: integer Don't send us LLM junk. Nothing here is even close to proper bindings, which means: 1. You did not write it yourself, because it is impossible to come with syntax like that (just does not exist), 2. Did not even bother to test it. Best regards, Krzysztof