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 CFA8733B96C for ; Fri, 31 Oct 2025 10:17:44 +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=1761905864; cv=none; b=WyMJhBgT0KrD1PEsW483CAFlh5gbc+TgonCcdLeoqxxBsqIKdF/SNgXwlwrzRKS2HHZcwfvCoNEqSPEE5XZxWoqm4jVpXa9Q0mQqWe+HBjVSgqfLb/j4JPAlHD8tUIZlI1Y/HXaqMkzDPoaEDqWwo/AUlBhx4KeOoxO1mGKy2ds= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1761905864; c=relaxed/simple; bh=FJrE0lSFQZBK043V/LtbxfzjWtZPDRbITX2KjEJ2uAA=; h=MIME-Version:References:In-Reply-To:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=hQEJvnuRwRR7hpv09SLUkHnyf8kr30zx05nmNrdFn0GhmDbD0lQ0hCbRrOu2P9Q8xkz5nf0rSqjl8PWOGkHMwVs9DgL/04ibBTa/nNUkE+X+xl++E4dTWXyL2puFe30PK59680tbr6IU7X6tXvcDrULpe3umOM0T2BEyXvI+I88= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=HWq0Skq7; 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="HWq0Skq7" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 74832C16AAE for ; Fri, 31 Oct 2025 10:17:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1761905864; bh=FJrE0lSFQZBK043V/LtbxfzjWtZPDRbITX2KjEJ2uAA=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=HWq0Skq7Rdp0rFhFtk5XOSD8PRfo2tD53ukMFgpYyV3F5wTbQfDHPdtSarM9g+6XG UlKUj/oddMtEdJ/NHkPOJQTg7jJaG5I3KKvhGCuthUfJkbXqqeM1KwC4v8YvyFpPSR Y5IG5yzdbFuLBMnGUDjn/lG91Ee9h6JchomBVixF7tgPkHb5omaL8Jil3t/kojLGQB P6NHnp8JwSSNk6bZNRTQ7I09xdrh7q1XZZmty1Dx8VWjZcxxcefPwKdFiMi2BYChtS ifpoD19Ra8mhtJIR/3c7vU8Hx4ksPl0QjGAnYJQXHYw9jm10ymnW6BPf5gQXpElf3H zTaPlC+sPCXTg== Received: by mail-lf1-f48.google.com with SMTP id 2adb3069b0e04-592f7733dd6so2311048e87.3 for ; Fri, 31 Oct 2025 03:17:44 -0700 (PDT) X-Forwarded-Encrypted: i=1; AJvYcCUD3nuE2+pLHl5aa1h/LNuytuGYw4pCbXI/zntNvc8F74dp59PB0oFSeBdmKj+7jI/iJIWqmF/Ftqw=@vger.kernel.org X-Gm-Message-State: AOJu0Yy0ZnmWDGSVIzcFDWdP/O8VHLYZvYut0R25R9v14n3h9air6jf1 VrR6KFU9l4ZR2yYpImW8irATOR9DKQ1u2nzgJFxca5oJ0x1jr+yp1HzRLZbQU5UQ1qytpHrQ4TF i8OObc4hYH8AzCIXjZ0en8SzaGNGl64k= X-Google-Smtp-Source: AGHT+IH1ZEHr87j2HoKj1XaUcVDdOsggjsFDOdzdoOlF9lh9gcHn+r8V9f88w7CAvAI41912p57YNIFruHCm8xaE6UY= X-Received: by 2002:a05:6512:3ca2:b0:591:ebc3:a682 with SMTP id 2adb3069b0e04-5941d540ba0mr1016268e87.39.1761905862858; Fri, 31 Oct 2025 03:17:42 -0700 (PDT) Precedence: bulk X-Mailing-List: linux-efi@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 References: <20251031084101.701159-1-adriana@arista.com> <20251031101009.704759-1-adriana@arista.com> In-Reply-To: <20251031101009.704759-1-adriana@arista.com> From: Ard Biesheuvel Date: Fri, 31 Oct 2025 11:17:31 +0100 X-Gmail-Original-Message-ID: X-Gm-Features: AWmQ_bkKjB1tG7deRtSl6aNw5JR9AFyZIvnTZ2CmZSskDiUBWY9B3XT6QmLog1c Message-ID: Subject: Re: [PATCH v4 0/2] DMI: Scan for DMI table from DTS info To: adriana Cc: ilias.apalodimas@linaro.org, trini@konsulko.com, robh@kernel.org, krzk@kernel.org, jdelvare@suse.com, frowand.list@gmail.com, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, vasilykh@arista.com, arm.ebbr-discuss@arm.com, boot-architecture@lists.linaro.org, linux-efi@vger.kernel.org, uefi-discuss@lists.uefi.org, linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="UTF-8" On Fri, 31 Oct 2025 at 11:10, adriana wrote: > > Some bootloaders like U-boot, particularly for the ARM architecture, > provide SMBIOS/DMI tables at a specific memory address. However, these > systems often do not boot using a full UEFI environment, which means the > kernel's standard EFI DMI scanner cannot find these tables. > > This series adds support for the kernel to find these tables by > reading the associated property from the Device Tree /chosen node. The > bootloader can specify the physical addresses using the property > "linux,smbios3-entrypoint". > > The first patch introduces the device tree binding documentation for this > new ABI, and the second patch implements the driver logic in dmi_scan.c. > > Changes in v4: > - Renamed linux,smbios3-table.yaml file, removed mention of ARM/ARM64 > (Patch 1/2). > - Drop the second definition of dmi_scan_from_dt() and fold checking > for CONFIG_OF (Patch 2/2). > - Drop unnecessary goto on the success case (Patch 2/2). > - Replace magic number for entrypoint size with SMBIOS3_ENTRY_POINT_SIZE > definition (Patch 2/2). > > Changes in v3: > - Removed linux,smbios-table property, only keep the SMBIOSv3 property > (Patch 1/2). > - Search DT for linux,smbios3-table only, removed the code searching > for the previous property (Patch 2/2). > > Changes in v2: > - Add missing Device Tree binding documentation (Patch 1/2). > - Split the original patch into a 2-part series (binding + driver). > - (No functional changes to the driver code in patch 2/2). > > adriana (2): > dt-bindings: firmware: Add binding for SMBIOS /chosen properties > drivers: firmware: dmi_scan: Add support for reading SMBIOS from DT > For the series, Reviewed-by: Ard Biesheuvel I can take the second patch, but bindings need to go in separately IIRC. Rob? > .../firmware/linux,smbios3-entrypoint.yaml | 25 +++++++++ > drivers/firmware/dmi_scan.c | 54 +++++++++++++++++++ > 2 files changed, 79 insertions(+) > create mode 100644 Documentation/devicetree/bindings/firmware/linux,smbios3-entrypoint.yaml > > -- > 2.51.0 >