[PATCH 2/5] dt-bindings: soc: canaan: Add top syscon for Canaan K230 SoC
Krzysztof Kozlowski
krzk at kernel.org
Mon Dec 29 23:39:19 PST 2025
On Tue, Dec 30, 2025 at 10:37:21AM +0800, Jiayu Du wrote:
> The Canaan K230 SoC top system controller provides register access
> to configure related modules. It includes a USB2 PHY and eMMC/SDIO PHY.
>
> Signed-off-by: Jiayu Du <jiayu.riscv at isrc.iscas.ac.cn>
> ---
> .../soc/canaan/canaan,k230-hisys-cfg.yaml | 68 +++++++++++++++++++
> 1 file changed, 68 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/soc/canaan/canaan,k230-hisys-cfg.yaml
>
> diff --git a/Documentation/devicetree/bindings/soc/canaan/canaan,k230-hisys-cfg.yaml b/Documentation/devicetree/bindings/soc/canaan/canaan,k230-hisys-cfg.yaml
> new file mode 100644
> index 000000000000..77875f2d4f48
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/soc/canaan/canaan,k230-hisys-cfg.yaml
> @@ -0,0 +1,68 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/soc/canaan/canaan,k230-hisys-cfg.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Canaan K230 HiSysConfig system controller
> +
> +maintainers:
> + - Jiayu Du <jiayu.riscv at isrc.iscas.ac.cn>
> +
> +description:
> + The Canaan K230 HiSysConfig system controller provides register access to
> + configure high-speed peripherals (e.g. eMMC/SDIO PHY tuning) and USB PHY
> + configuration.
> +
> +properties:
> + compatible:
> + items:
> + - const: canaan,k230-hisys-cfg
> + - const: syscon
> + - const: simple-mfd
> +
> + reg:
> + maxItems: 1
> +
> + "#address-cells":
> + const: 1
> +
> + "#size-cells":
> + const: 1
> +
> + usb-phy at 70:
> + $ref: schemas/phy/canaan,k230-usb-phy.yaml#
So that's why you did not have example there? But where did you explain
merging strategy/constraints/dependencies? How maintainers can now they
can apply this or not?
> + unevaluatedProperties: false
> +
> + usb-phy at 90:
> + $ref: schemas/phy/canaan,k230-usb-phy.yaml#
> + unevaluatedProperties: false
Anyway, these are not really real children. Defining child per phy,
where each such phy is just few registers, is way too granular. Instead
define one phy with phy-cells=2.
You also MUST make this device - hisys - binding complete. If you do
not, then my review is: fold the children here, because you do not have
any other resources for the parent.
> +
> +required:
> + - compatible
> + - reg
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + hi_sys_config: syscon at 91585000 {
> + compatible = "canaan,k230-hisys-cfg", "syscon", "simple-mfd";
> + reg = <0x91585000 0x400>;
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + usbphy0: usb-phy at 70 {
> + compatible = "canaan,k230-usb-phy";
> + reg = <0x70 0x1C>, <0xb0 0x8>;
> + clocks = <&sysclk K230_HS_USB0_AHB_GATE>;
You never bothered to test your code. Community is not a testing
service. It's your job to TEST IT before sending.
Best regards,
Krzysztof
More information about the linux-riscv
mailing list