summaryrefslogtreecommitdiff
path: root/Documentation/devicetree/bindings/pinctrl/nvidia,tegra194-pinmux.yaml
AgeCommit message (Collapse)AuthorFilesLines
2022-11-21dt-bindings: pinctrl: tegra194: Separate instancesThierry Reding1-20/+215
Tegra194 has two separate instances of the pin controller, one called AON (in the always-on domain) and another called "main". Instead of treating them as a single pin controller, split them up into two separate controllers. Doing so allows the mapping between the pinmux and GPIO controllers to be trivial identity mappings and more cleanly separates the AON from the main IP blocks. Note that while this changes the DT node in an incompatible way, this doesn't have any practical implications for backwards-compatibility. The reason for this is that device trees have only reconfigured a very narrow subset of pins of the main controller, so the new driver will remain backwards-compatible with old device trees. Reviewed-by: Rob Herring <robh@kernel.org> Signed-off-by: Thierry Reding <treding@nvidia.com>
2022-11-21dt-bindings: pinctrl: tegra: Convert to json-schemaThierry Reding1-0/+89
Convert the NVIDIA Tegra pinmux controller bindings from the free-form text format to json-schema. Reviewed-by: Rob Herring <robh@kernel.org> Signed-off-by: Thierry Reding <treding@nvidia.com>