From: Krzysztof Kozlowski <krzk@kernel.org>
To: Markuss Broks <markuss.broks@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Ivaylo Ivanov <ivo.ivanov.ivanov1@gmail.com>,
Maksym Holovach <nergzd@nergzd723.xyz>
Subject: Re: [PATCH 1/3] dt-bindings: soc: samsung: exynos-speedy: Document SPEEDY host controller bindings
Date: Fri, 13 Dec 2024 08:40:33 +0100 [thread overview]
Message-ID: <207354ad-e363-4156-ba6b-86dbaa13ab95@kernel.org> (raw)
In-Reply-To: <20241212-speedy-v1-1-544ad7bcfb6a@gmail.com>
On 12/12/2024 22:09, Markuss Broks wrote:
> Add the schema for the Samsung SPEEDY serial bus host controller.
> The bus has 4 bit wide addresses for addressing devices
> and 8 bit wide register addressing. Each register is also 8
> bit long, so the address can be 0-f (hexadecimal), node name
> for child device follows the format: node_name@[0-f].
This wasn't tested so limited review.
A nit, subject: drop second/last, redundant "bindings". The
"dt-bindings" prefix is already stating that these are bindings.
See also:
https://elixir.bootlin.com/linux/v6.7-rc8/source/Documentation/devicetree/bindings/submitting-patches.rst#L18
>
> Co-developed-by: Maksym Holovach <nergzd@nergzd723.xyz>
> Signed-off-by: Maksym Holovach <nergzd@nergzd723.xyz>
> Signed-off-by: Markuss Broks <markuss.broks@gmail.com>
> ---
> .../bindings/soc/samsung/exynos-speedy.yaml | 78 ++++++++++++++++++++++
Filename must match compatible.
> 1 file changed, 78 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/soc/samsung/exynos-speedy.yaml b/Documentation/devicetree/bindings/soc/samsung/exynos-speedy.yaml
> new file mode 100644
> index 0000000000000000000000000000000000000000..304b322a74ea70f23d8c072b44b6ca86b7cc807f
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/soc/samsung/exynos-speedy.yaml
> @@ -0,0 +1,78 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/soc/samsung/exynos-speedy.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Samsung Exynos SPEEDY serial bus host controller
Speedy or SPEEDY?
> +
> +maintainers:
> + - Markuss Broks <markuss.broks@gmail.com>
> +
> +description:
> + Samsung SPEEDY is a proprietary Samsung serial 1-wire bus.
1-wire? But not compatible with w1 (onwire)?
> + It is used on various Samsung Exynos chips. The bus can
> + address at most 4 bit (16) devices. The devices on the bus
> + have 8 bit long register line, and the registers are also
> + 8 bit long each. It is typically used for communicating with
> + Samsung PMICs (s2mps17, s2mps18, ...) and other Samsung chips,
> + such as RF parts.
> +
> +properties:
> + compatible:
> + - items:
> + - enum:
> + - samsung,exynos9810-speedy
> + - const: samsung,exynos-speedy
Drop last compatible and use only SoC specific.
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> + clock-names:
> + - const: pclk
Drop clock-names, not needed for one entry.
> +
> + interrupts:
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> + - "#address-cells"
> + - "#size-cells"
You do not have them in the properties, anyway required goes before
additionalProperties
> +
> +patternProperties:
> + "^[a-z][a-z0-9]*@[0-9a-f]$":
That's odd regex. Look at other bus bindings.
> + type: object
> + additionalProperties: true
> +
> + properties:
> + reg:
> + maxItems: 1
maximum: 15
> +
> + required:
> + - reg
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + speedy0: speedy@141c0000 {
Drop unused label.
> + compatible = "samsung,exynos9810-speedy",
> + "samsung-exynos-speedy";
> + reg = <0x141c0000 0x2000>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
No resources? No clocks? No interrupts?
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-12-13 7:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 21:09 [PATCH 0/3] Add Samsung SPEEDY serial bus host controller driver Markuss Broks
2024-12-12 21:09 ` [PATCH 1/3] dt-bindings: soc: samsung: exynos-speedy: Document SPEEDY host controller bindings Markuss Broks
2024-12-12 22:30 ` Rob Herring (Arm)
2024-12-13 7:40 ` Krzysztof Kozlowski [this message]
2024-12-13 9:47 ` Markuss Broks
2024-12-12 21:09 ` [PATCH 2/3] soc: samsung: Add a driver for Samsung SPEEDY host controller Markuss Broks
2024-12-13 7:49 ` Krzysztof Kozlowski
2024-12-13 9:42 ` Markuss Broks
2024-12-13 13:55 ` Krzysztof Kozlowski
2024-12-14 12:06 ` Markuss Broks
2024-12-14 14:43 ` Markus Elfring
2024-12-17 17:31 ` Markuss Broks
2024-12-14 15:52 ` Christophe JAILLET
2024-12-17 17:28 ` Markuss Broks
2024-12-12 21:09 ` [PATCH 3/3] MAINTAINERS: Add entry for the Samsung Exynos " Markuss Broks
2024-12-13 8:42 ` [PATCH 0/3] Add Samsung SPEEDY serial bus host controller driver 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=207354ad-e363-4156-ba6b-86dbaa13ab95@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ivo.ivanov.ivanov1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=markuss.broks@gmail.com \
--cc=nergzd@nergzd723.xyz \
--cc=robh@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