From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: avromanov@sberdevices.ru
Cc: u-boot@lists.denx.de, kernel@sberdevices.ru,
Neil Armstrong <neil.armstrong@linaro.org>,
mkorpershoek@baylibre.com, sjg@chromium.org, trini@konsulko.com,
narmstrong@baylibre.com, u-boot-amlogic@groups.io
Subject: Re: [PATCH v3 3/5] doc/usage: cmd: documentation for meson/sm command
Date: Wed, 4 Jan 2023 14:21:33 +0100 [thread overview]
Message-ID: <d3f7f072-dc75-9601-ab6f-7f01aedcbefd@gmx.de> (raw)
In-Reply-To: <d4b8016b-b47e-c101-d9f6-622bf166e4d9@linaro.org>
On 1/4/23 13:35, Neil Armstrong wrote:
> Le 22/12/2022 à 13:57, Alexey Romanov via groups.io a écrit :
>
> Please add a short description of the change in the commit message.
>
> With this added:
> Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
>
>> Signed-off-by: Alexey Romanov <avromanov@sberdevices.ru>
>> ---
>> doc/usage/cmd/sm.rst | 44 ++++++++++++++++++++++++++++++++++++++++++++
This lacks an addition to doc/usage/index.rst.
>> 1 file changed, 44 insertions(+)
>> create mode 100644 doc/usage/cmd/sm.rst
>>
>> diff --git a/doc/usage/cmd/sm.rst b/doc/usage/cmd/sm.rst
>> new file mode 100644
>> index 00000000000..3a70c137ec9
>> --- /dev/null
>> +++ b/doc/usage/cmd/sm.rst
>> @@ -0,0 +1,44 @@
>> +.. SPDX-License-Identifier: GPL-2.0+:
>> +
>> +Meson Security Monitor command
sm command
==========
We always use the actual command name here as it appears in the index.
You can mention the Meson Security Monitor in the text below.
Best regards
Heinrich
>> +==============================
>> +
>> +Synopis
>> +-------
>> +
>> +::
>> +
>> + sm serial <address>
>> + sm reboot_reason [name]
>> + sm efuseread <offset> <size> <address>
>> + sm efusewrite <offset> <size> <address>
>> + sm efusedump <offset> <size>
>> +
>> +Description
>> +-----------
>> +
>> +The sm command is used to request services from the secure monitor. User
>> +can call secure monitor to request special TEE function, for example
>> chip
>> +serial number info, reboot reason, etc.
>> +
>> +sm serial
>> + Retrieve chip unique serial number from sm and write it to memory on
>> + appropriate address.
>> +
>> +sm reboot_reason
>> + Print reboot reason to the console, if parameter [name] isn't
>> specified.
>> + If parameter specified, set reboot reason string to environment
>> variable
>> + with this name.
>> +
>> +sm efuseread
>> + Read <size> bytes starting from <offset> from efuse memory bank and
>> write
>> + result to the address <address>.
>> +
>> +sm efusewrite
>> + Write into efuse memory bank, starting from <offset>, the <size> bytes
>> + of data, located at address <address>.
>> +
>> +Configuration
>> +-------------
>> +
>> +To use the sm command you must specify CONFIG_CMD_MESON=y
>
next prev parent reply other threads:[~2023-01-04 13:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 12:57 [PATCH v3 0/5] arch-meson: introduce efusedump command Alexey Romanov
2022-12-22 12:57 ` [PATCH v3 1/5] asm/arch-meson: add missing meson_sm_write_efuse signature Alexey Romanov
2023-01-04 12:33 ` Neil Armstrong
2022-12-22 12:57 ` [PATCH v3 2/5] arm/mach-meson: move smc commands in cmd/meson Alexey Romanov
2023-01-04 12:34 ` Neil Armstrong
2022-12-22 12:57 ` [PATCH v3 3/5] doc/usage: cmd: documentation for meson/sm command Alexey Romanov
2023-01-04 12:35 ` Neil Armstrong
2023-01-04 13:21 ` Heinrich Schuchardt [this message]
2022-12-22 12:57 ` [PATCH v3 4/5] cmd/arm: meson: sm: introduce efusedump command Alexey Romanov
2023-01-04 12:34 ` Neil Armstrong
2022-12-22 12:57 ` [PATCH v3 5/5] doc/usage: cmd: sm: documentation efusedump cmd Alexey Romanov
2023-01-04 12:36 ` Neil Armstrong
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=d3f7f072-dc75-9601-ab6f-7f01aedcbefd@gmx.de \
--to=xypron.glpk@gmx.de \
--cc=avromanov@sberdevices.ru \
--cc=kernel@sberdevices.ru \
--cc=mkorpershoek@baylibre.com \
--cc=narmstrong@baylibre.com \
--cc=neil.armstrong@linaro.org \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot-amlogic@groups.io \
--cc=u-boot@lists.denx.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).