From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: soc: samsung: s5pv210-chipid: add S5PV210 ChipID
Date: Fri, 1 Jul 2022 11:35:24 -0600 [thread overview]
Message-ID: <20220701173524.GA1185040-robh@kernel.org> (raw)
In-Reply-To: <20220629123543.94515-1-krzysztof.kozlowski@linaro.org>
On Wed, Jun 29, 2022 at 02:35:43PM +0200, Krzysztof Kozlowski wrote:
> Add bindings for the S5PV210 ChipID block.
Is this new or was undocumented?
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> .../bindings/soc/samsung/s5pv210-chipid.yaml | 30 +++++++++++++++++++
samsung,s5pv210-chipid.yaml
Surely there's other similar blocks. Can we start collecting in a
common directory?
> 1 file changed, 30 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/soc/samsung/s5pv210-chipid.yaml
>
> diff --git a/Documentation/devicetree/bindings/soc/samsung/s5pv210-chipid.yaml b/Documentation/devicetree/bindings/soc/samsung/s5pv210-chipid.yaml
> new file mode 100644
> index 000000000000..7c3f4ec47f7e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/soc/samsung/s5pv210-chipid.yaml
> @@ -0,0 +1,30 @@
> +# SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/soc/samsung/s5pv210-chipid.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Samsung S5PV210 SoC series Chipid driver
> +
> +maintainers:
> + - Krzysztof Kozlowski <krzk@kernel.org>
> +
> +properties:
> + compatible:
> + const: samsung,s5pv210-chipid
> +
> + reg:
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + chipid@e0000000 {
> + compatible = "samsung,s5pv210-chipid";
> + reg = <0xe0000000 0x1000>;
> + };
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2022-07-01 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 12:35 [PATCH] dt-bindings: soc: samsung: s5pv210-chipid: add S5PV210 ChipID Krzysztof Kozlowski
2022-07-01 17:35 ` Rob Herring [this message]
2022-07-03 18:11 ` Krzysztof Kozlowski
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=20220701173524.GA1185040-robh@kernel.org \
--to=robh@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@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;
as well as URLs for NNTP newsgroup(s).