mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jean DELVARE <jdelvare@suse.com>
To: Crag Wang <crag0715@gmail.com>
Cc: dell.client.kernel@dell.com, crag.wang@dell.com,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] firmware: dmi-id: add product_family to modalias as pf
Date: Mon, 22 Dec 2025 11:03:21 +0100	[thread overview]
Message-ID: <5d87f4c294be78dc7a4bc39de9883779aba6fa9e.camel@suse.com> (raw)
In-Reply-To: <20250814064443.1278029-1-crag0715@gmail.com>

Hi Crag,

On Thu, 2025-08-14 at 14:44 +0800, Crag Wang wrote:
> Some devices require product_family information to trigger
> conditional actions when the value matches a predefined criterion
> 
> $ cat /sys/class/dmi/id/product_family
> Dell Pro Max Desktops
> 
> $ udevadm info -q all --path=/sys/class/dmi/id | grep MODALIAS
> E: MODALIAS=dmi:bvnDellInc.:bvr0.59.39:bd12/16/2024:br0.59:efr0.0:svnDellInc.:pfDellProMaxDesktops:pnDellProMaxMicroFCM2250:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr:sku0D14:
> 
> $ cat /sys/class/dmi/id/modalias
> dmi:bvnDellInc.:bvr0.59.39:bd12/16/2024:br0.59:efr0.0:svnDellInc.:pfDellProMaxDesktops:pnDellProMaxMicroFCM2250:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr:sku0D14:
> 
> Signed-off-by: Crag Wang <crag0715@gmail.com>
> ---
>  drivers/firmware/dmi-id.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/firmware/dmi-id.c b/drivers/firmware/dmi-id.c
> index d19c78a78ae3..284652d75cc7 100644
> --- a/drivers/firmware/dmi-id.c
> +++ b/drivers/firmware/dmi-id.c
> @@ -87,6 +87,7 @@ static ssize_t get_modalias(char *buffer, size_t buffer_size)
>  		{ "br",  DMI_BIOS_RELEASE },
>  		{ "efr", DMI_EC_FIRMWARE_RELEASE },
>  		{ "svn", DMI_SYS_VENDOR },
> +		{ "pf",  DMI_PRODUCT_FAMILY },
>  		{ "pn",  DMI_PRODUCT_NAME },
>  		{ "pvr", DMI_PRODUCT_VERSION },
>  		{ "rvn", DMI_BOARD_VENDOR },

For consistency, I'd rather add it between DMI_PRODUCT_VERSION and
DMI_BOARD_VENDOR.

That's simple enough, so why not. Out of curiosity, which udev rule
(and/or driver) needs this?

-- 
Jean Delvare
SUSE L3 Support

      reply	other threads:[~2025-12-22 10:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-14  6:44 Crag Wang
2025-12-22 10:03 ` Jean DELVARE [this message]

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=5d87f4c294be78dc7a4bc39de9883779aba6fa9e.camel@suse.com \
    --to=jdelvare@suse.com \
    --cc=crag.wang@dell.com \
    --cc=crag0715@gmail.com \
    --cc=dell.client.kernel@dell.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®