From: Bean Huo <huobean@gmail.com>
To: Jens Wiklander <jens.wiklander@linaro.org>
Cc: avri.altman@wdc.com, avri.altman@sandisk.com, bvanassche@acm.org,
alim.akhtar@samsung.com, jejb@linux.ibm.com,
martin.petersen@oracle.com, can.guo@oss.qualcomm.com,
ulf.hansson@linaro.org, beanhuo@micron.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 3/3] scsi: ufs: core: Add OP-TEE based RPMB driver for UFS devices
Date: Thu, 23 Oct 2025 17:09:25 +0200 [thread overview]
Message-ID: <9f3d1d277b0d102b5d912b533be21ed78103e142.camel@gmail.com> (raw)
In-Reply-To: <CAHUa44FfQAPWGgVbfrCnZfF9HkGwW=fgUhV-y9RKrUQf1V6yNg@mail.gmail.com>
On Thu, 2025-10-23 at 15:53 +0200, Jens Wiklander wrote:
> > + device_id = kasprintf(GFP_KERNEL, "%04X-%04X-%s-%s-%04X-%04X",
> > + dev_info->wmanufacturerid, dev_info-
> > >wspecversion,
> > + dev_info->model, serial_hex, device_version,
> > + manufacture_date);
>
>
> The device ID is part of the ABI with the secure world or the firmware
> we're serving. It might be worth adding a comment so the format isn't
> changed without understanding the consequences.
>
> Cheers,
> Jens
Jens,
I can add, do you have suggestion for this reminder message, for example:
/*
* WARNING: This device ID format is part of the stable ABI between
* the kernel and secure world (OP-TEE). Any changes to this format
* must be coordinated with firmware updates to avoid breaking
* communication with the secure world.
*/
or
/* Device ID format is ABI with secure world - do not change without firmware
coordination */
or ?
Kind regards,
Bean
next prev parent reply other threads:[~2025-10-23 15:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 12:42 [PATCH v5 0/3] " Bean Huo
2025-10-21 12:42 ` [PATCH v5 1/3] scsi: ufs: core: Convert string descriptor format macros to enum Bean Huo
2025-10-21 12:42 ` [PATCH v5 2/3] scsi: ufs: core: fix incorrect buffer duplication in ufshcd_read_string_desc() Bean Huo
2025-10-21 12:42 ` [PATCH v5 3/3] scsi: ufs: core: Add OP-TEE based RPMB driver for UFS devices Bean Huo
2025-10-23 13:53 ` Jens Wiklander
2025-10-23 15:09 ` Bean Huo [this message]
2025-10-23 17:30 ` Jens Wiklander
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=9f3d1d277b0d102b5d912b533be21ed78103e142.camel@gmail.com \
--to=huobean@gmail.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@sandisk.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=can.guo@oss.qualcomm.com \
--cc=jejb@linux.ibm.com \
--cc=jens.wiklander@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ulf.hansson@linaro.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®