[PATCH v3 1/2] dt-bindings: mfd: add Traverse Ten64 board controller

[Krzysztof Kozlowski]

On 21/08/2025 08:11, Mathew McBride wrote:
> Add device tree binding for the board (micro)controller on Ten64 family
> boards[1].
> 

Do not attach (thread) your patchsets to some other threads (unrelated
or older versions). This buries them deep in the mailbox and might
interfere with applying entire sets.

> The schema is simple and is (presently) only consumed by U-Boot, but it
> is possible that it could be consumed by nvmem or other type drivers in
> the future, as well as extended to future Traverse boards.
> 
> The categorisation as a "MFD" follows that of comparable devices such
> as "gw,gsc", "google,chros-ec" and "kontron,sl28cpld".

That is not MFD device. Google EC is for example, but you have only one
function. I think we will move all of them to some separate ec directory.

> 
> [1] https://ten64doc.traverse.com.au/hardware/microcontroller/
> 
> Signed-off-by: Mathew McBride <matt at traverse.com.au>
> ---
>  .../mfd/traverse,ten64-controller.yaml        | 45 +++++++++++++++++++
>  1 file changed, 45 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/mfd/traverse,ten64-controller.yaml
> 
> diff --git a/Documentation/devicetree/bindings/mfd/traverse,ten64-controller.yaml b/Documentation/devicetree/bindings/mfd/traverse,ten64-controller.yaml
> new file mode 100644
> index 0000000000000..4e2f2063605cd
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mfd/traverse,ten64-controller.yaml
> @@ -0,0 +1,45 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mfd/traverse,ten64-controller.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Traverse Ten64 board microcontroller
> +
> +maintainers:
> +  - Mathew McBride <matt at traverse.com.au>
> +
> +description: |
> +  The board microcontroller on the Ten64 board family is responsible for
> +  management of power sources on the board, as well as signalling the SoC
> +  to power on and reset.
> +
> +  Communication between the SoC and controller is via I2C, at a fixed address

Either you make it a schema or drop it.

> +  of 0x7e. While the controller firmware implements several functions, there
> +  are presently no parameters that are configurable by DT properties, except
> +  those that are required of an I2C bus endpoint.

This paragraph wasn't here before. It's completely redundant, drop.

Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski at linaro.org>

Best regards,
Krzysztof