From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wm2-f12.google.com (mail-wm2-f12.google.com [74.125.225.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1475744160D for ; Wed, 23 Sep 2026 20:10:58 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=74.125.225.140 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790194267; cv=none; b=AtxjvMtb4xWdOOaxXD4klpLtgc1QEhjgEn4IjNu2v8sXDhGoWWmK2ddxGoUuRSTBExw8Oi2ueGJERCZuon7rgluqTnPE7H1gMfkRGhnyqJV8LKRfH0GPt0FwBACyYeKKuaxd8rXPUU/m3W6k4aHC8U7N2VTVdt7b2ubj1RoCOTg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790194267; c=relaxed/simple; bh=zt6hSECodB5WF8/06/9r9WG9bP75OayoZGseUD1mFAM=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version; b=HBp/QGCsn2Rq8QEeLtvT/Ue4OcoYrONmoYf90ku/WN8zESTJLieDlyfaWcjNO2aIhSxHhJidrm9bYCWP3ZqclZZxRAMLzXAH2MVxioKhi653l+prACBSGX5kyPNxWVgm4arDWmolPz3F9EYmcPy2okbcM1O3Az0IAzsFM1Az/hY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=FP/hOT9t; arc=none smtp.client-ip=74.125.225.140 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) header.d=gmail.com header.i=@gmail.com header.b="FP/hOT9t" Received: by mail-wm2-f12.google.com with SMTP id 5b1f17b1804b1-49d097b4939so7408965e9.0 for ; Wed, 23 Sep 2026 13:10:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1790194255; x=1790799055; darn=vger.kernel.org; h=content-transfer-encoding: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=Z5ud7C6Q7hzdhSrMZ0UnmI/lSmzd22+sOaMu+2pIMXc=; b=FP/hOT9t6AENCmlVY+cwKC4aAhbgY1oTXmFtvmbMalrBfTFIwSYrWTjC3mmyp5fMDG sfd152MN9mHGHdxNrUcry6+dxCZGE2qOjXtYzt1dRQFIoguCn2BvHTvccqGHHOERy3WL Qx1OWyrN74/exQ73vnY2PFK7qKDsB2o/NChi/Bpgseiub/O/V1v7eDgY8p8NJc9hktFW 8JSl5ZsG8oRUTWGwSU6cWNj3FAqkJsgARvHL82vtzYp/cD8acdnKA2B49UngI3XAEr95 QYxgwLnl1+IKPzu5yD5t7Y5gwxbXhaWjz6kobA1+DDv9SnVdnd1FUHpoHysY/3r8hKEH nyVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1790194255; x=1790799055; h=content-transfer-encoding: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=Z5ud7C6Q7hzdhSrMZ0UnmI/lSmzd22+sOaMu+2pIMXc=; b=T4FxRWVsFczfi/t2rKbm4TXoH2ue2yCPHEaXuKlQTE09/lANt99vxix3pMLHzM3R4S SrRaFWhUhOpy8rtOMDkTNZxp7+R1ojmkZtVbziy2USUGvY/ff2uHqBv0+4YOOWVkobfX W0xTMoJ8T2zn8LcnVoCcnc86WePmEGz/VwCs0hAHTw16dCY8+vb/UUgO8XLhC1Si0jsf KMkc7pbYb5G38W4wEN2sdg+fGyhhH1PNfrSt/Z9xXmmMI+d0RYCPB/fp0g+yk631ikNq nT0My1ZAmLALzdRCEkIOyupZdgemO9I+1wuxcTX9+ucK0bKpvvKrDNjYGXu78dYD+wBl GlpQ== X-Gm-Message-State: AFuF++lpTZrH0mG74IHPbX0Y7UIdF6zLXBugPy977BRcgW+/yASPXtzu U81wGL0U4t6s2JPQhDIeKJZo54L6DZ/fEqGpBJsgMNbvBF3k1D6tMyFY X-Gm-Gg: AYBFou3J8e5dJ2asHpHG2zG4jmpx3Wz3Sb1qfTB+bIDVGGBNiUsYi4PlSBiJ0di/qRy BrVG8rpKAP4/IMJKefLmqwJdgjsrsXcNexh/+oMFgLPAXl/NRtmJd94KjzUvgR8DGvXpR6qn3fD vJMi/aGRAlFp1ZJUI7/FFi5G2rejOLiV6nzhFjkf6geG30uB4Db+yqgqFLhm9vSWcUBeqbUuoqI WTJMcTBhCZZpeqXjCmIn3EyGxH6XP5m0CoVLAzPeVGuU3ohNaxzccGPSSziU1KifuKbGZuUhVjD JuwE1TRWKKTiY9IQ0OH8/oEbw0TypDVm9+M24m8w7tNSyl1M8roSldAKcgmmkrcl9l05svonGeh oxcPd7cEiASL5zbnKXCmSydONotPdBbfBwQnbixIg8sXSxVyq6HQs263W3VOCHKLnkJb1oQ7tc6 cRrjNAA7ML6zwEqsQG2jQv95Dn9ubWpUDNcEYhrUv0mJfdRfIS2Y7k4upKjgBWRCmtOykVYJJq1 UJViNA6qXLn5a5XIWCV75Rm X-Received: by 2002:a05:600c:4fc7:b0:49e:799e:c1c3 with SMTP id 5b1f17b1804b1-49fe66f1444mr4525325e9.17.1790194255204; Wed, 23 Sep 2026 13:10:55 -0700 (PDT) Received: from ingenieria31.oficinasStQ.local ([79.112.15.218]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-49fe5cd4c8dsm13559295e9.3.2026.09.23.13.10.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 23 Sep 2026 13:10:54 -0700 (PDT) From: Max Pedraza To: Helge Deller , Thomas Zimmermann , Simona Vetter , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Maxime Ripard Cc: linux-fbdev@vger.kernel.org, devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Max Pedraza Subject: [PATCH v3 2/7] dt-bindings: display: add a device tree supplied boot logo Date: Wed, 23 Sep 2026 22:10:30 +0200 Message-Id: <20260923201035.51007-3-maximpedraza@gmail.com> X-Mailer: git-send-email 2.39.5 In-Reply-To: <20260923201035.51007-1-maximpedraza@gmail.com> References: <20260923201035.51007-1-maximpedraza@gmail.com> Precedence: bulk X-Mailing-List: linux-fbdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Embedded products frequently need a product specific boot logo. Today that means pointing CONFIG_LOGO_LINUX_CLUT224_FILE at a different image, which bakes it into the kernel image: a change of branding, or a second product sharing the same board support package, requires a separate kernel build, and requalifying that kernel for what is a cosmetic change. Add a binding for a "boot-logo-clut224" node, which carries the logo in the same paletted format the built-in CLUT224 logos already use, plus a few optional properties describing where on the screen it is drawn. The node lives under /chosen because a logo is configuration handed over by firmware rather than a description of the hardware. Open Firmware, which the device tree descends from, carried a boot logo in the same spirit as the oem-logo variable under /options, and simple-framebuffer nodes live under /chosen today for the same reason. The palette size is derived from the length of the "clut" property rather than spelled out separately, and "data" holds plain palette indices; the 32 entry offset the frame buffer layer reserves for the console is an implementation detail and is applied by the kernel, not by the binding. "logo-position" takes -1 on an axis to mean centre on that axis rather than carrying a separate boolean for it. A boolean can only centre both axes or neither, and next to explicit coordinates it would have to override them silently when a device tree gave both. A rotation turns the logo, not the screen. "logo-position" and "logo-offset" are screen pixels whatever "logo-rotation" says, and a quarter turn only changes how much room the logo takes up. Placing the logo in a frame that turns with it would make the same pair of coordinates mean different places on the same panel, decided by a property that is meant to describe the image. Every coordinate is bounded. The kernel clamps them anyway, since it cannot trust a device tree, but a value that cannot possibly be meant is worth catching in dtbs_check rather than on the panel. Signed-off-by: Max Pedraza --- .../bindings/display/boot-logo-clut224.yaml | 135 ++++++++++++++++++ MAINTAINERS | 1 + 2 files changed, 136 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/boot-logo-clut224.yaml diff --git a/Documentation/devicetree/bindings/display/boot-logo-clut224.yaml b/Documentation/devicetree/bindings/display/boot-logo-clut224.yaml new file mode 100644 index 0000000000..9dc3471763 --- /dev/null +++ b/Documentation/devicetree/bindings/display/boot-logo-clut224.yaml @@ -0,0 +1,135 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/display/boot-logo-clut224.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Boot logo supplied by the device tree + +maintainers: + - Max Pedraza + +description: | + Embedded systems commonly need a product specific boot logo. Today that + means pointing CONFIG_LOGO_LINUX_CLUT224_FILE at a different image, which + bakes it into the kernel image: changing the logo means building and + deploying a new kernel. + + This node lets the boot logo be described by the device tree instead, so that + a single kernel image can serve several products, or several revisions of the + same product, that only differ in branding. + + 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. Open Firmware, which the device tree descends from, carried + a boot logo in the same spirit as the oem-logo variable under /options. + + The image is stored in the same paletted format the in-kernel CLUT224 logos + use: a palette of at most 224 RGB entries plus one palette index per pixel. + +properties: + $nodename: + const: logo + + compatible: + const: boot-logo-clut224 + + width: + $ref: /schemas/types.yaml#/definitions/uint32 + description: Logo width in pixels. + minimum: 1 + maximum: 65535 + + height: + $ref: /schemas/types.yaml#/definitions/uint32 + description: Logo height in pixels. + minimum: 1 + maximum: 65535 + + clut: + $ref: /schemas/types.yaml#/definitions/uint8-array + description: + Colour lookup table, as consecutive red, green and blue bytes per entry. + The number of entries is derived from the property length and must not + exceed 224. + minItems: 3 + maxItems: 672 + + data: + $ref: /schemas/types.yaml#/definitions/uint8-array + description: + One byte per pixel, left to right and top to bottom, each byte being an + index into the colour lookup table. The property length must be equal to + width multiplied by height. + + logo-position: + $ref: /schemas/types.yaml#/definitions/int32-array + description: + X and Y coordinates, in pixels, of the top left corner of the logo. + A value of -1 on an axis centres the logo on that axis instead. + Defaults to the top left corner of the screen. + 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 logo has been + placed. + Mostly useful together with a centred axis, to land the logo somewhere + other than the middle of a panel whose usable area is not its centre. + items: + - description: X displacement + minimum: -65535 + maximum: 65535 + - description: Y displacement + minimum: -65535 + maximum: 65535 + + logo-rotation: + $ref: /schemas/types.yaml#/definitions/string + description: + Rotation applied to the logo before it is drawn. It turns the logo and + not the screen, so a quarter turn swaps how much room the logo takes + up, but logo-position and logo-offset stay in screen pixels either + way. + enum: [none, cw, ccw, ud] + default: none + +required: + - compatible + - width + - height + - clut + - data + +additionalProperties: false + +examples: + - | + // A 4x2 logo using three colours, centred on both axes. + / { + compatible = "foo"; + model = "foo"; + #address-cells = <1>; + #size-cells = <1>; + + chosen { + logo { + compatible = "boot-logo-clut224"; + width = <4>; + height = <2>; + clut = /bits/ 8 <0xff 0x00 0x00 + 0x00 0xff 0x00 + 0x00 0x00 0xff>; + data = /bits/ 8 <0x00 0x01 0x01 0x00 + 0x02 0x00 0x00 0x02>; + logo-position = <(-1) (-1)>; + }; + }; + }; diff --git a/MAINTAINERS b/MAINTAINERS index c241444789..804a48e9bc 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -10339,6 +10339,7 @@ L: dri-devel@lists.freedesktop.org S: Maintained Q: http://patchwork.kernel.org/project/linux-fbdev/list/ T: git git://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev.git +F: Documentation/devicetree/bindings/display/boot-logo-clut224.yaml F: Documentation/fb/ F: drivers/video/ F: include/linux/fb.h -- 2.39.5