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

[Mathew McBride]

This is a rework of a binding I submitted a while ago (2023)[1].

Because the nature of the device-tree binding was very simple (it is an I2C
device with no configuration parameters apart from the I2C endpoint address),
I had submitted it as a "trivial" device.  I now understand that is not the
right approach.

I have categorised the controller as a MFD device, following devices of
a similar nature, such as "gw,gsc", "google,chros-ec" and "kontron,sl28cpld".

Unlike these devices, there are currently no child "MFD" features available,
but it is possible there could be bindings for nvmem or other functions in the future.

[1] https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20230501064727.8921-2-matt@traverse.com.au/

Signed-off-by: Mathew McBride <matt at traverse.com.au>
---
Changes in v2 (2025):
  - Create dt-binding yaml file and categorise as an 'mfd' device
  - Removed the unrelated MMC controller fix, which will be submitted separately
  at another time

Changes in v3:
  - Fix typos and style issues in yaml and commit message
---
Mathew McBride (2):
  dt-bindings: mfd: add Traverse Ten64 board controller
  arm: dts: freescale: ten64: add board controller binding

 .../mfd/traverse,ten64-controller.yaml        | 45 +++++++++++++++++++
 .../boot/dts/freescale/fsl-ls1088a-ten64.dts  |  4 ++
 2 files changed, 49 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/mfd/traverse,ten64-controller.yaml

-- 
2.45.1