From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=209.85.221.54 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1793109244; b=QcLfDg4w1yDyOGf6tNFf6R3RmXP1Z5/luIbNDwzPVO090OUGH5yLwmFfMpd0SMcisV29 jxwTYN/hnfoR7Vox9G91qoRO3Xr09Z0Kwi2XYAmaRDqVcCX355tv7rLfbB+coagHZasfJ Gd+2B0rHt57I2pXqXTNQpoV9oorwqoIZh5f/3/kOlEJDVaMSm1tgGD3ir+RCjnvdN1WFA JNZ+dhhECk4Shr+NMbChx46p3aTzNzDzXsMVj3e6S/Rd9h/FEIWo5Ev1WGTDGgH0ktP0m r7YIK0Cn3Uasu/l5uQwGvFEmzY3KInbxOuQnCGwwgR6Fh0Rv4qO4troUUwLsXyVJ6aQ== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1793109244; h=DMARC-Filter:Received:DKIM-Signature:X-Google-DKIM-Signature: X-Forwarded-Encrypted:X-Gm-Message-State:X-Gm-Gg:X-Received:Received: From:To:Cc:Subject:Date:Message-Id:X-Mailer:In-Reply-To:References: MIME-Version:Content-Type:Content-Transfer-Encoding; bh=CNwiH8WXKlzRpf9XA93ERiKn3IeKgsDSdg+szp0134I=; b=5Ki77biVjUg8Rk0f52X4gvdbiIZb3hnMHIxqYMrFZiFpECXm//q6v9jKaHsA9h8T7wcU /nNeMq/kDqJ2SiDNtOZklQ5YBjJmiDojijgHqAxcviwtAo4GFY+Cj+v3M1CICOy3bC1+4 dQKNF/hUATAl8mPD5HqFBgQE/YNI32mp7UK0W2nP3SMPD1nMA4KfVLh5RmcB/il3m34GM Cjt4+FfBUPAnGU+PODag2k2rZg+CQqvXIRI5pE9R+n+s399PUEtwMV3m7mNBekfYZuw5u DWeuj1WriIG0NL91QfGdlKtIBiIUtuIGbQQpNGiMl5F4smvVmR1WHzqDtgfSrVl8rpg== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20251104 header.b=fj4wjdw0; arc=none smtp.remote-ip=209.85.221.54 Received: from mail-wr1-f54.google.com (mail-wr1-f54.google.com [209.85.221.54]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E2CAA60A3814 for ; Tue, 27 Oct 2026 13:54:03 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org E2CAA60A3814 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key, unprotected) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20251104 header.b=fj4wjdw0 Received: by mail-wr1-f54.google.com with SMTP id ffacd0b85a97d-48e10a70540so2465215f8f.1 for ; Tue, 27 Oct 2026 06:54:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1793109242; x=1793714042; darn=vger.kernel.org; h=content-transfer-encoding:content-type:mime-version:references :in-reply-to:message-id:date:subject:cc:to:from:from:to:cc:subject :date:message-id:reply-to:content-type; bh=CNwiH8WXKlzRpf9XA93ERiKn3IeKgsDSdg+szp0134I=; b=fj4wjdw0D3xlsVKH89Axah6M1qST+GP/oHhvyXcuwD6enLr+rUKo2loUa8YsrcI0R7 wXT1e3nmLGw/mBrIq7Q4WzEGXqzaHDgmr98+K+ECoFxnYZYOEfSm/pz5X5n0PuBHU3ao BK7B1QZPO6DDZVd0h8KKTDh13A0X2+sJKWZKGb07oSaQlTI+xhDefU+4S644vpB45WLd L75VURnLN9vNsKLqr/+LrMNFsZUpW3plvCZM/vBOR+r+Aj6SGHhrLDG6QK09xgfHzliV JXjUlSFRJ1v12/LgnfZfbt7YN803n7kHe+OwlhLCN3jI6YbDThgrHE+tLciU1lXcgtKz PDPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1793109242; x=1793714042; h=content-transfer-encoding:content-type:mime-version:references :in-reply-to:message-id:date:subject:cc:to:from:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=CNwiH8WXKlzRpf9XA93ERiKn3IeKgsDSdg+szp0134I=; b=W/24mN2JigJ0y5V9nx4+LkGgBE/8ETF9NX+YzeHd0XveQ/c6F8BmFjmRMkoc7CCl15 Gh01rA25wuirmv2cZcah3i0FQSYGUFjiXcpmxVTHh0au2xt9sL6yrzaLQvfEKo3j2C3+ h7QcHqlOQtoyzVWVT+k8XfsM5CajJckjBU6nIiRd836WVrHM1RXXeH0aizw4Fgiysy28 +ESANGaUMMpKRRkty8mIJZ8wSwRVdgcvIZom7klgneibToq0hPXk9miqWYQl7GS8rW0Z Ugc4U3XB8zQoPc8SIHxxSnnHKZa2aJSudor5XloYxm9l1RS6x//ltczaxm0tcdm+R8jQ DHjQ== X-Forwarded-Encrypted: i=1; AKwUvByIJDmp5up2489Ko4G8Z2WDhJ0Imw9/luGBZIhcJjQ7UKI8wQev7iILOT3BF5SpmZEbZCOZ3VLMxBUK@vger.kernel.org X-Gm-Message-State: AFq9FYIyXHN6nVkSfvj6/B91dcdXvwsHE7VxEMle96EXeQyQjK+qpHBH 1ngNSl5amMmqGBUzbZlrvH7D2110jaugKW+/vDf6gcUjnZnk+T3QzrDr X-Gm-Gg: AYBFou3D/119rqWTDD9WtjJPa9xkWDZG0UpjnI8jG3WzYCCxpQqooh55N9sUlDvZH6L 2fY/pU204B9PIUmu87d8Wpa7RK04ghjlSyaL3FcprIPHilS5EWXrouW4/OKg2u/1mTAeFwk7EE9 C9EgOxTOo2y9TRKtHGZobpfw9jmMjvTK+8LDiPuOb9FLrmA6JWF3Ec5UeLl+xWtOSBsrGwwFCAW 90g7nh0o2Xrc8mbItk0qxj9xcUNs7XrVy6cgEgNxSPFF5dUyOlOyYSS1gHF1KZIs+WxJAgeXasc R0sI9NG4zz9TgtwKlwnlWfQsE2f2z+krgFR2MvaerlTTGcTqBxoDZ5C7kvqlNfq/0PiPI3SVJ8v xpf5yhBVJWIC1o+UnKk/MSLW0XfOi1MNsZZuMu7BmNDBtVDSWb8q5gEtwUkcfgwABRJkQUB0dIi kNFf2w4hPGIPLNZOpaBCRbTpbbTbE+3SaqDV/RhCdkzVM6qR/L6kyJSRSLF+s5LBcO/3M3aPp5q 738O9nUPlPW7QRfD6ubCId4zvC56f1RkSXlsy6ZQ6xSvI9NSTp1zCSUeJ47/CyBBKOElt+dUfCT zkqZYps= X-Received: by 2002:a05:6000:29d5:b0:48e:3d35:a18a with SMTP id ffacd0b85a97d-48e3eb98289mr9620502f8f.49.1793109242138; Tue, 27 Oct 2026 06:54:02 -0700 (PDT) Received: from ingenieria31.oficinasStQ.local ([79.117.46.175]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-48e3ebcb846sm23128058f8f.25.2026.10.27.06.54.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 27 Oct 2026 06:54:01 -0700 (PDT) From: =?UTF-8?q?M=C3=A0xim=20Pedraza=20Padilla?= To: Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Simona Vetter , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Ard Biesheuvel , Jonathan Corbet , Helge Deller , Peter Jones Cc: Francesco Valla , Jani Nikula , Mario Limonciello , Javier Martinez Canillas , Jocelyn Falempe , Sam Ravnborg , Ilias Apalodimas , Shuah Khan , Randy Dunlap , dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org, linux-efi@vger.kernel.org, linux-fbdev@vger.kernel.org, linux-doc@vger.kernel.org, linux-embedded@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v6 07/15] dt-bindings: display: add a boot logo node under /chosen Date: Tue, 27 Oct 2026 14:53:34 +0100 Message-Id: <20261027135342.2003632-8-maximpedraza@gmail.com> X-Mailer: git-send-email 2.39.5 In-Reply-To: <20261027135342.2003632-1-maximpedraza@gmail.com> References: <20261027135342.2003632-1-maximpedraza@gmail.com> X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Products built on the same board often differ only in branding. On UEFI systems the firmware hands the operating system its boot logo through the ACPI BGRT; a device tree system has no such table, so today the logo is built into the kernel, and each product needs its own kernel image. With U-Boot's Falcon mode the device tree is the only thing that reaches the kernel, so it is also the only place the logo can come from. Add a "logo" node, compatible "boot-logo", under /chosen. It lives there because a logo is configuration handed over by firmware rather than a description of the hardware, as simple-framebuffer nodes already are. The image is a BMP with 24 bits per pixel and no compression, the format of the BGRT image, so that one file serves the firmware splash, a BMP loaded as firmware and this node alike. It is carried either in a "logo-image" property, which dtc fills in from the file with /incbin/, or in a reserved memory region the bootloader loaded it into, named by "memory-region". Exactly one of the two must be present. "logo-position" takes -1 on an axis to mean centre on that axis, which is the only way to say it when the device tree does not know the image size, and "logo-offset" is added afterwards. "rotation" is the one of panel-common.yaml, degrees counter clockwise, but turns the image rather than the screen, so position and offset stay in screen pixels. The optional "background-color" goes with the image, since a logo designed for one background looks wrong on another. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Màxim Pedraza Padilla --- .../bindings/display/boot-logo.yaml | 156 ++++++++++++++++++ MAINTAINERS | 1 + 2 files changed, 157 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/boot-logo.yaml diff --git a/Documentation/devicetree/bindings/display/boot-logo.yaml b/Documentation/devicetree/bindings/display/boot-logo.yaml new file mode 100644 index 000000000000..9cd4b2565112 --- /dev/null +++ b/Documentation/devicetree/bindings/display/boot-logo.yaml @@ -0,0 +1,156 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/display/boot-logo.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Boot logo supplied by the device tree + +maintainers: + - Francesco Valla + - Màxim Pedraza Padilla + +description: | + An image for the operating system to show on the display while it boots, + handed over by the firmware together with where and how to show it. + + Products built on the same board often differ only in branding. Carrying + the logo in the device tree lets a single kernel image serve all of them, + each booting with its own device tree, and it works where the device tree + is the only thing that reaches the kernel, as with U-Boot's Falcon mode. + It plays the part the ACPI BGRT plays on UEFI systems. + + Since a logo is configuration rather than a description of the hardware, + the node lives under /chosen, next to the other things firmware hands to + the operating system. + + The image is a BMP file with a 40 byte BITMAPINFOHEADER, 24 bits per pixel + and no compression, the format of the BGRT image. It is carried either in + the node itself or in a reserved memory region the bootloader loaded it + into, never both. + +allOf: + - $ref: panel/panel-common.yaml# + +properties: + $nodename: + const: logo + + compatible: + const: boot-logo + + logo-image: + $ref: /schemas/types.yaml#/definitions/uint8-array + description: + The BMP file itself, byte for byte, which dtc can fill in from the file + with /incbin/. The device tree stays in memory for as long as the + system runs, and some architectures limit its size (arm64 to 2 MB), so + this is meant for small images; at three bytes per pixel, larger ones + belong in a reserved memory region. + + memory-region: + maxItems: 1 + description: | + Reserved memory region the bootloader loaded the BMP file into, starting + at the beginning of the region. The BMP header says how much of the + region is image. + + This keeps the image out of the device tree, so that it can be changed + without rebuilding the device tree, for instance by loading it from a + partition of its own that userspace can update. + + Memory keeps its contents across a reset, and may even across a short + power cycle, and the operating system cannot tell a stale image from a + fresh one. A bootloader that loads no image into the region therefore + disables the node (status = "disabled") or removes it. + + logo-position: + $ref: /schemas/types.yaml#/definitions/int32-array + description: + X and Y coordinates, in screen pixels, of the top left corner of the + image once it has been rotated. A value of -1 on an axis centres the + image on that axis instead, which is the only way to say it when the + device tree does not know the image size, as with a memory region. + Defaults to centring on both axes. + default: [-1, -1] + items: + - description: X coordinate, or -1 to centre horizontally + minimum: -1 + maximum: 65535 + - description: Y coordinate, or -1 to centre vertically + minimum: -1 + maximum: 65535 + + logo-offset: + $ref: /schemas/types.yaml#/definitions/int32-array + description: + X and Y displacement, in screen pixels, applied after the image has been + placed. Mostly useful together with a centred axis, to land the image + somewhere other than the middle of a panel whose visible area is not + the middle of the mode. Defaults to no displacement. + default: [0, 0] + items: + - description: X displacement + minimum: -65535 + maximum: 65535 + - description: Y displacement + minimum: -65535 + maximum: 65535 + + rotation: + description: + Rotation applied to the image as the screen is seen, in degrees counter + clockwise, as for the rotation property of panels. It turns the image + and not the screen; a panel mounted turned is described by its own + rotation property, which is made up for first, so this means the same + whichever way the panel is mounted. A quarter turn swaps how much room + the image takes up, but logo-position and logo-offset stay in pixels of + the screen as seen either way. Defaults to 0. + + background-color: + $ref: /schemas/types.yaml#/definitions/uint32 + description: + Colour of the rest of the screen, as 0xRRGGBB. When absent, the + operating system uses its own default. + maximum: 0xffffff + +required: + - compatible + +# The image lives either in the node or in a reserved memory region, +# never both and never neither. +oneOf: + - required: + - logo-image + - required: + - memory-region + +additionalProperties: false + +examples: + - | + // A 2x1 image, red and blue, centred and 120 pixels below the middle + / { + compatible = "foo"; + model = "foo"; + #address-cells = <1>; + #size-cells = <1>; + + chosen { + logo { + compatible = "boot-logo"; + /* Normally: logo-image = /incbin/("logo.bmp"); */ + logo-image = /bits/ 8 <0x42 0x4d 0x3e 0x00 0x00 0x00 0x00 0x00 + 0x00 0x00 0x36 0x00 0x00 0x00 0x28 0x00 + 0x00 0x00 0x02 0x00 0x00 0x00 0x01 0x00 + 0x00 0x00 0x01 0x00 0x18 0x00 0x00 0x00 + 0x00 0x00 0x08 0x00 0x00 0x00 0x13 0x0b + 0x00 0x00 0x13 0x0b 0x00 0x00 0x00 0x00 + 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 + 0xff 0xff 0x00 0x00 0x00 0x00>; + logo-position = <(-1) (-1)>; + logo-offset = <0 120>; + background-color = <0x1e1e28>; + }; + }; + }; diff --git a/MAINTAINERS b/MAINTAINERS index 321ecb9f5b5b..0d1decaedde0 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -9174,6 +9174,7 @@ M: Màxim Pedraza Padilla L: dri-devel@lists.freedesktop.org S: Maintained T: git https://gitlab.freedesktop.org/drm/misc/kernel.git +F: Documentation/devicetree/bindings/display/boot-logo.yaml F: drivers/gpu/drm/clients/drm_splash.c DRM TTM SUBSYSTEM -- 2.39.5