On Fri, Jul 01, 2022 at 03:17:08PM -0600, Rob Herring wrote: > On Fri, Jul 01, 2022 at 05:04:58PM +0200, Thierry Reding wrote: [...] > > +additionalProperties: > > + description: | > > + Tegra's pin configuration nodes act as containers for an arbitrary number of subnodes. Each of > > + these subnodes represents some desired configuration for a pin, a group, or a list of pins or > > + groups. This configuration can include the mux function to select on those pin(s)/group(s), and > > + various pin configuration parameters, such as pull-up, tristate, drive strength, etc. > > + > > + The name of each subnode is not important; all subnodes should be enumerated and processed > > + purely based on their content. > > + > > + Each subnode only affects those parameters that are explicitly listed. In other words, a > > + subnode that lists a mux function but no pin configuration parameters implies no information > > + about any pin configuration parameters. Similarly, a pin subnode that describes a pullup > > + parameter implies no information about e.g. the mux function or tristate parameter. For this > > + reason, even seemingly boolean values are actually tristates in this binding: unspecified, off, > > + or on. Unspecified is represented as an absent property, and off/on are represented as integer > > + values 0 and 1. > > + > > + See the TRM to determine which properties and values apply to each pin/group. Macro values for > > + property values are defined in include/dt-binding/pinctrl/pinctrl-tegra.h. > > + type: object > > + patternProperties: > > + "^pinmux(-[a-z0-9-_]+)?$": > > type: object Looks like this fell through the cracks. I've fixed in in v3 locally, but I'll hold off on resending the whole series to avoid the churn. Thierry
Attachment:
signature.asc
Description: PGP signature
