| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <c779d973-2f3e-44b5-91e0-1ad0910fa016@linaro.org>
Date: Fri, 20 Oct 2023 08:50:22 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Jyan Chou <jyanchou@...ltek.com>, adrian.hunter@...el.com,
jh80.chung@...sung.com, ulf.hansson@...aro.org
Cc: riteshh@...eaurora.org, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
asutoshd@...eaurora.org, p.zabel@...gutronix.de,
linux-mmc@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, arnd@...db.de,
briannorris@...omium.org, doug@...morgal.com,
tonyhuang.sunplus@...il.com, abel.vesa@...aro.org,
william.qiu@...rfivetech.com
Subject: Re: [PATCH V3][4/4] dt-bindings: mmc: Add dt-bindings for realtek mmc
driver
On 20/10/2023 05:49, Jyan Chou wrote:
> Document the device-tree bindings for Realtek SoCs mmc driver.
>
> Signed-off-by: Jyan Chou <jyanchou@...ltek.com>
>
> ---
> v2 -> v3:
> - Modify dt-bindings' content and description.
> - Fix coding style.
> - Update the list of maintainers.
>
> v0 -> v2:
> - Add dt-bindings.
> ---
> ---
> .../bindings/mmc/realtek-dw-mshc.yaml | 150 ++++++++++++++++++
> 1 file changed, 150 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mmc/realtek-dw-mshc.yaml
>
> diff --git a/Documentation/devicetree/bindings/mmc/realtek-dw-mshc.yaml b/Documentation/devicetree/bindings/mmc/realtek-dw-mshc.yaml
> new file mode 100644
> index 000000000000..b1e37fb37be9
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mmc/realtek-dw-mshc.yaml
Filename matching compatible.
BTW, before you respond, be sure you have fixed your email client. In
your last response everything was not properly wrapped (not matching
mailing list discussion style).
> @@ -0,0 +1,150 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mmc/realtek-dw-mshc.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Realtek designware mobile storage host controller
DesignWare
> +
> +description:
> + Realtek uses the Synopsys designware mobile storage host controller
DesignWare
> + to interface a SoC with storage medium. This file documents the Realtek
> + specific extensions.
> +
> +allOf:
> + - $ref: synopsys-dw-mshc-common.yaml#
> +
> +maintainers:
> + - Jyan Chou <jyanchou@...ltek.com>
> +
> +properties:
> + compatible:
> + enum:
> + - realtek,rtd-dw-cqe-emmc
Compatibles should have SoC-specific part. It does not look like you
have one here.
Missing blank line
> + reg:
> + maxItems: 2
You need to describe the items.
> +
> + reg-names:
> + maxItems: 2
You need to describe the items.
> +
> + interrupts:
> + maxItems: 1
> +
> + cqe:
> + maxItems: 1
Looks like some custom property. If it is a generic one, where is it
documented? If it is custom, missing vendor prefix and description.
Detailed description.
> +
> + clocks:
> + minItems: 2
> + maxItems: 4
No. This is variable. You need fixed number of items (because why
exactly the same device would have different number of clocks?) and you
need to describe them.
> +
> + clock-names:
> + minItems: 2
> + maxItems: 4
You need to describe the items.
> +
> + clock-freq-min-max:
> + description:
> + Clk frequency should be in the interval.
No, drop property.
> +
> + resets:
> + maxItems: 1
> +
> + reset-names:
> + const: reset
And here you describe the item? The only place when it is not needed?
Drop entierly.
> +
> + speed-step:
> + maxItems: 1
Drop.
> +
> + pinctrl-0:
> + description:
> + should contain default/high speed pin ctrl.
> + maxItems: 1
> +
> + pinctrl-1:
> + description:
> + should contain sdr50 mode pin ctrl.
> + maxItems: 1
> +
> + pinctrl-2:
> + description:
> + should contain ddr50 mode pin ctrl.
> + maxItems: 1
> +
> + pinctrl-3:
> + description:
> + should contain hs200 speed pin ctrl.
> + maxItems: 1
> +
> + pinctrl-4:
> + description:
> + should contain hs400 speed pin ctrl.
> + maxItems: 1
> +
> + pinctrl-5:
> + description:
> + should contain tune0 pin ctrl.
> + maxItems: 1
> +
> + pinctrl-6:
> + description:
> + should contain tune1 pin ctrl.
> + maxItems: 1
> +
> + pinctrl-7:
> + description:
> + should contain tune2 pin ctrl.
> + maxItems: 1
> +
> + pinctrl-8:
> + description:
> + should contain tune3 pin ctrl.
> + maxItems: 1
> +
> + pinctrl-9:
> + description:
> + should contain tune4 pin ctrl.
> + maxItems: 1
> +
> + pinctrl-names:
> + maxItems: 10
> +
> +required:
> + - compatible
> + - reg
> + - reg-names
> + - interrupts
> + - clocks
> + - clock-names
> + - pinctrl-names
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + emmc: mmc@...00 {
> + compatible = "realtek,rtd-dw-cqe-emmc";
> + reg = <0x00012000 0x00600>,
> + <0x00012180 0x00060>;
> + reg-names = "emmc", "cqhci";
> + interrupts = <0 42 4>;
> + clocks = <&cc 22>, <&cc 26>, <&cc 121>, <&cc 122>;
> + clock-names = "biu", "ciu", "vp0", "vp1";
> + clock-freq-min-max = <300000 400000000>;
> + clock-frequency = <400000>;
> + vmmc-supply = <®_vcc1v8>;
> + resets = <&rst 20>;
> + reset-names = "reset";
> + speed-step = <3>;
> + cqe = <1>;
> + pinctrl-names = "default", "sdr50", "ddr50", "hs200", "hs400",
> + "tune0", "tune1", "tune2", "tune3", "tune4";
> + pinctrl-0 = <&emmc_pins_sdr50>;
> + pinctrl-1 = <&emmc_pins_sdr50>;
> + pinctrl-2 = <&emmc_pins_ddr50>;
> + pinctrl-3 = <&emmc_pins_hs200>;
> + pinctrl-4 = <&emmc_pins_hs400>;
> + pinctrl-5 = <&emmc_pins_tune0>;
> + pinctrl-6 = <&emmc_pins_tune1>;
> + pinctrl-7 = <&emmc_pins_tune2>;
> + pinctrl-8 = <&emmc_pins_tune3>;
> + pinctrl-9 = <&emmc_pins_tune4>;
> + };
Fix indentation.
Best regards,
Krzysztof
Powered by blists - more mailing lists