From: Krzysztof Kozlowski <krzk@kernel.org>
To: dj76.yang@samsung.com,
"jesper.nilsson@axis.com" <jesper.nilsson@axis.com>,
"lars.persson@axis.com" <lars.persson@axis.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"lee.jones@linaro.org" <lee.jones@linaro.org>
Cc: "javierm@redhat.com" <javierm@redhat.com>,
"bjorn.andersson@linaro.org" <bjorn.andersson@linaro.org>,
"linux-arm-kernel@axis.com" <linux-arm-kernel@axis.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Moon-Ki Jun <moonki.jun@samsung.com>,
Sang Min Kim <hypmean.kim@samsung.com>,
Wangseok Lee <wangseok.lee@samsung.com>
Subject: Re: [PATCH 1/4] dt-bindings: firmware: Add bindings for Samsung smc
Date: Wed, 13 Jul 2022 09:04:45 +0200 [thread overview]
Message-ID: <c403edcf-0c33-225c-8bbd-3a49e90a9a73@kernel.org> (raw)
In-Reply-To: <20220713045357epcms1p8ccfe1c489edfd066d0e41ff928c0af71@epcms1p8>
On 13/07/2022 06:53, Dongjin Yang wrote:
> Add an devicetree bindings for Samsung secure monitor call service.
> This driver is used for SoCs produced by Samsung Foundry to provide
> SMC call. This patch supports register read/write request to secure
> monitor. Also, SMC call request which uses shared memory to exchange
> the data between kernel and secure monitor.
>
> Signed-off-by: Dongjin Yang <dj76.yang@samsung.com>
> ---
> .../bindings/firmware/samsung,smccc-svc.yaml | 31 ++++++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 32 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/firmware/samsung,smccc-svc.yaml
>
> diff --git a/Documentation/devicetree/bindings/firmware/samsung,smccc-svc.yaml b/Documentation/devicetree/bindings/firmware/samsung,smccc-svc.yaml
> new file mode 100644
> index 000000000000..427c42a6cd75
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/firmware/samsung,smccc-svc.yaml
> @@ -0,0 +1,31 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/firmware/samsung,smccc-svc.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Samsung Secure Monitor call service
> +
> +maintainers:
> + - Jesper Nilsson <jesper.nilsson@axis.com>
> +
> +description: |
> + The file documents device tree bindings of Samsung secure monitor
> + call service.
> +
> +properties:
> + compatible:
Please add SoC comaptible followed by generic samsung,smccc-svc (so you
need items with an enum and const).
> + const: samsung,smccc-svc
> +
> +required:
> + - compatible
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> +
No need for blank line.
> + samsung-svc {
Generic node names, e.g. smc.
> + compatible = "samsung,smccc-svc";
> + };
> +...
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 20133dcd8ce9..6763746c349f 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1862,6 +1862,7 @@ M: Jesper Nilsson <jesper.nilsson@axis.com>
> M: Lars Persson <lars.persson@axis.com>
> L: linux-arm-kernel@axis.com
> S: Maintained
> +F: Documentation/devicetree/bindings/firmware/samsung,smccc-svc.yaml
Does not look related to Artpec. Shouldn't this be under Samsung Exynos?
> F: Documentation/devicetree/bindings/pinctrl/axis,artpec6-pinctrl.txt
> F: arch/arm/boot/dts/artpec6*
> F: arch/arm/mach-artpec
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-07-13 7:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220713045357epcms1p8ccfe1c489edfd066d0e41ff928c0af71@epcms1p8>
2022-07-13 4:53 ` [PATCH 1/4] dt-bindings: firmware: Add bindings for Samsung smc Dongjin Yang
2022-07-13 7:04 ` Krzysztof Kozlowski [this message]
[not found] ` <CGME20220713045357epcms1p8ccfe1c489edfd066d0e41ff928c0af71@epcms1p3>
2022-07-25 23:55 ` Dongjin Yang
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=c403edcf-0c33-225c-8bbd-3a49e90a9a73@kernel.org \
--to=krzk@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dj76.yang@samsung.com \
--cc=hypmean.kim@samsung.com \
--cc=javierm@redhat.com \
--cc=jesper.nilsson@axis.com \
--cc=krzk+dt@kernel.org \
--cc=lars.persson@axis.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moonki.jun@samsung.com \
--cc=robh+dt@kernel.org \
--cc=wangseok.lee@samsung.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 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 NNTP newsgroup(s).