| Message ID | 20210526184839.2937899-1-robh@kernel.org |
|---|---|
| Headers | show |
| Series | dt-bindings: Convert mux bindings to schema | expand |
On Wed, May 26, 2021 at 01:48:33PM -0500, Rob Herring wrote: > This series converts the mux-controller and some i2c mux bindings to DT > schema. This was a rabbit hole of trying to fix undocumented (by schema) > compatibles (enabled by setting DT_CHECKER_FLAGS=-m). So this is mux > bindings, and then a few others that are used in the mux binding > examples. So, I assume this should all go via your tree? That would be fine with me. Maybe Peter has some more comments, but for the procedure, here is my ack for the I2C parts of this series: Acked-by: Wolfram Sang <wsa@kernel.org>
On 2021-05-28 10:45, Wolfram Sang wrote: > On Wed, May 26, 2021 at 01:48:33PM -0500, Rob Herring wrote: >> This series converts the mux-controller and some i2c mux bindings to DT >> schema. This was a rabbit hole of trying to fix undocumented (by schema) >> compatibles (enabled by setting DT_CHECKER_FLAGS=-m). So this is mux >> bindings, and then a few others that are used in the mux binding >> examples. > > So, I assume this should all go via your tree? That would be fine with > me. Maybe Peter has some more comments, but for the procedure, here is > my ack for the I2C parts of this series: Hi Rob, Thanks for converting these! I can't call what I have done a review, because the details escape me, and I don't have time to spend at the moment. However, from where I'm looking, it all looks splendid. Ignorance is bliss! So, for patches 3-5 (where I'm the maintainer) you have my Acked-by: Peter Rosin <peda@axentia.se> Interesting times, being a maintainer of things I don't understand. I need to fix that... The main worry I have is the comment from Laurent about the intermediate "i2c-mux" node, which also applies to i2c-gate which has been converted to yaml before and to i2c-arb which is still in .txt format. I don't remember exactly what the issue was that made me add the optional level, but hopefully it is as you say, and that it is only MFD-type devices that need them and that those can specify the intermediate level themselves. My vision was to always have the intermediate level, since I thought the bindings looked clearer that way. But that's just a personal opinion, and it doesn't really matter... However, I also worry that the information needed by future authors of MFD bindings is lost and that they will have no readily available source of the information that the intermediate nodes should be called i2c-mux, i2c-arb or i2c-gate. The info was removed in the i2c-gate.txt -> .yaml conversion. But that problem is not present in this series, since the info is preserved in i2c-mux.txt -> .yaml conversion. So, please go ahead with this series. Thanks again! Cheers, Peter
On Wed, 26 May 2021, Rob Herring wrote: > The ti,j721e-system-controller binding does not follow the standard mux > controller node name 'mux-controller' and the example is incomplete. Fix > these to avoid schema errors before the mux controller binding is > converted to schema. > > Cc: Lee Jones <lee.jones@linaro.org> > Cc: Kishon Vijay Abraham I <kishon@ti.com> > Signed-off-by: Rob Herring <robh@kernel.org> > --- > .../mfd/ti,j721e-system-controller.yaml | 19 +++++++++++++------ > 1 file changed, 13 insertions(+), 6 deletions(-) Acked-by: Lee Jones <lee.jones@linaro.org> -- Lee Jones [李琼斯] Senior Technical Lead - Developer Services Linaro.org │ Open source software for Arm SoCs Follow Linaro: Facebook | Twitter | Blog