Re: [PATCH v6 3/6] dt-bindings: mfd: aspeed,ast2x00-scu: allow #size-cells range
From: Krzysztof Kozlowski <krzk@kernel.org>
Date: 2025-10-22 08:07:31
Also in:
linux-aspeed, linux-devicetree, lkml
On 22/10/2025 09:05, Ryan Chen wrote:
quoted hunk ↗ jump to hunk
The #size-cells property in the Aspeed SCU binding is currently fixed to a constant value of 1. However, newer SoCs (ex. AST2700) may require two size cells to describe certain subregions or subdevices. This patch updates the schema to allow #size-cells values in the range of 1 to 2. This makes the binding more flexible while maintaining compatibility with existing platforms. It also resolves dt-binding validation warnings reported by `make dt_binding_check`. Signed-off-by: Ryan Chen <ryan_chen@aspeedtech.com> --- Documentation/devicetree/bindings/mfd/aspeed,ast2x00-scu.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)diff --git a/Documentation/devicetree/bindings/mfd/aspeed,ast2x00-scu.yaml b/Documentation/devicetree/bindings/mfd/aspeed,ast2x00-scu.yaml index da1887d7a8fe..ee7855845e97 100644 --- a/Documentation/devicetree/bindings/mfd/aspeed,ast2x00-scu.yaml +++ b/Documentation/devicetree/bindings/mfd/aspeed,ast2x00-scu.yaml@@ -38,7 +38,7 @@ properties: maximum: 2 '#size-cells': - const: 1 + enum: [1, 2]
I said no last time and now when we see the DTS it is visible it makes no sense. Please reply in the DTS patch in the EXACT place where this is being used. NAK Best regards, Krzysztof