All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: adriana <adriana@arista.com>
Cc: krzk@kernel.org, jdelvare@suse.com, frowand.list@gmail.com,
	linux-arm-kernel@lists.infradread.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	vasilykh@arista.com
Subject: Re: [PATCH v2 0/2] DMI: Scan for DMI table from DTS info
Date: Wed, 22 Oct 2025 15:19:53 -0500	[thread overview]
Message-ID: <20251022201953.GA206947-robh@kernel.org> (raw)
In-Reply-To: <20251022114527.618908-1-adriana@arista.com>

On Wed, Oct 22, 2025 at 04:45:25AM -0700, 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.

I thought u-boot is a pretty complete UEFI implementation now. If 
there's standard way for UEFI to provide this, then that's what we 
should be using. I know supporting this has been discussed in context of 
EBBR spec, but no one involved in that has been CC'ed here.
 
> This series adds support for the kernel to find these tables by
> reading properties from the Device Tree /chosen node. The bootloader
> can specify the physical addresses using "linux,smbios-table" and
> "linux,smbios3-table".

/chosen node entries go in chosen.yaml schema in dtschema repository. 
But first, I need to see some agreement this is how we want to support 
this.

Rob

  parent reply	other threads:[~2025-10-22 20:19 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22  8:21 [PATCH 1/1] DMI: Scan for DMI table from DTS info adriana
2025-10-22  9:56 ` Krzysztof Kozlowski
2025-10-22 11:45   ` [PATCH v2 0/2] " adriana
2025-10-22 11:45     ` [PATCH v2 1/2] dt-bindings: firmware: Add binding for SMBIOS /chosen properties adriana
2025-10-22 11:45     ` [PATCH v2 2/2] drivers: firmware: dmi_scan: Add support for reading SMBIOS from DT adriana
2025-10-22 20:19     ` Rob Herring [this message]
2025-10-23  2:20       ` [PATCH v2 0/2] DMI: Scan for DMI table from DTS info Adriana Nicolae
2025-10-23  8:21         ` Ard Biesheuvel
2025-10-23 13:34           ` Adriana Nicolae
2025-10-23 13:53             ` Ard Biesheuvel
2025-10-23 14:47               ` Adriana Nicolae
2025-10-24  9:49                 ` Ard Biesheuvel
2025-10-24 11:07                   ` Ilias Apalodimas
2025-10-24 18:07                     ` Tom Rini
2025-10-31  8:51                       ` Adriana Nicolae
2025-10-31  8:40     ` [PATCH v3 " adriana
2025-10-31  8:41       ` [PATCH v3 1/2] dt-bindings: firmware: Add binding for SMBIOS /chosen properties adriana
2025-10-31  8:52         ` Ard Biesheuvel
2025-10-31  9:05           ` Ard Biesheuvel
2025-10-31  8:41       ` [PATCH v3 2/2] drivers: firmware: dmi_scan: Add support for reading SMBIOS from DT adriana
2025-10-31  9:05         ` Ard Biesheuvel
2025-10-31  9:31         ` Ilias Apalodimas
2025-10-31 10:10       ` [PATCH v4 0/2] DMI: Scan for DMI table from DTS info adriana
2025-10-31 10:10         ` [PATCH v4 1/2] dt-bindings: firmware: Add binding for SMBIOS /chosen properties adriana
2025-10-31 11:15           ` Rob Herring
2025-10-31 11:43             ` Rob Herring
2025-10-31 12:31               ` Adriana Nicolae
2025-10-31 10:10         ` [PATCH v4 2/2] drivers: firmware: dmi_scan: Add support for reading SMBIOS from DT adriana
2025-10-31 10:17         ` [PATCH v4 0/2] DMI: Scan for DMI table from DTS info Ard Biesheuvel
2025-10-31 11:03           ` Ilias Apalodimas
2025-10-31 11:59         ` [PATCH v5 0/1] " adriana
2025-10-31 11:59           ` [PATCH v5 1/1] drivers: firmware: dmi_scan: Add support for reading SMBIOS from DT adriana
2025-10-31 14:19           ` [PATCH v5 0/1] DMI: Scan for DMI table from DTS info Conor Dooley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251022201953.GA206947-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=adriana@arista.com \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=jdelvare@suse.com \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradread.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vasilykh@arista.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.