[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <171830931400.2391260.17890560707264408523.robh@kernel.org>
Date: Thu, 13 Jun 2024 14:08:37 -0600
From: "Rob Herring (Arm)" <robh@...nel.org>
To: Frank Li <Frank.Li@....com>
Cc: linux-kernel@...r.kernel.org, Shawn Guo <shawnguo@...nel.org>,
Ulf Hansson <ulf.hansson@...aro.org>,
linux-arm-kernel@...ts.infradead.org,
Conor Dooley <conor+dt@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, linux-mmc@...r.kernel.org,
devicetree@...r.kernel.org, imx@...ts.linux.dev
Subject: Re: [PATCH v5 1/3] dt-bindings: mmc: mmc-spi-slot: Change
voltage-ranges to uint32-matrix
On Thu, 13 Jun 2024 10:32:05 -0400, Frank Li wrote:
> According to common mmc core, voltages-ranges should be matrix.
>
> Signed-off-by: Frank Li <Frank.Li@....com>
>
> ---
> Change from v4 to v5
> - Change maxItems to 1
>
> Not sure why it impact other mmc yaml's voltage-ranges.
> Rob's answer:
>
> It's a quirk of the tools. When decoding properties, the tools only know
> all possible types. Types are global, not per binding. Sometimes it can
> be figured out, but cases like this cannot be.
> ---
> Documentation/devicetree/bindings/mmc/mmc-spi-slot.yaml | 16 +++++++++-------
> 1 file changed, 9 insertions(+), 7 deletions(-)
>
Reviewed-by: Rob Herring (Arm) <robh@...nel.org>
Powered by blists - more mailing lists