On Thu, Feb 29, 2024 at 10:24:33AM +0100, Geert Uytterhoeven wrote: > On Wed, Feb 28, 2024 at 9:02 PM Chris Packham > <Chris.Packham@xxxxxxxxxxxxxxxxxxx> wrote: > > On 29/02/24 03:04, Rob Herring wrote: > > > On Wed, Feb 28, 2024 at 10:22:42AM +1300, Chris Packham wrote: ... > > > How does one know which GPIO is which segment? > > > > I've expanded the description in v3. > > > > + An array of GPIOs one per segment. The first GPIO corresponds to the A > > + segment the last GPIO corresponds to the G segment. > > > > Do you think that's sufficient or do I need to add more? In the driver > > itself I've put a little ascii art diagram of the segments. > > Given users are reading the bindings rather than the driver source, > I would move the diagram to the bindings. +1 here. We have a diagram already in UAPI headers, but that won't be (quickly) visible for the real users, duplicating in the code doesn't add any value, but adding it to DT description will be beneficial. -- With Best Regards, Andy Shevchenko
