On 15:59-20240202, Roger Quadros wrote: > > > On 02/02/2024 14:18, Nishanth Menon wrote: > > On 12:13-20240202, Roger Quadros wrote: > > [..] > >>>> > >>>> As DTS and driver will be merged by separate maintainers I thought it > >>>> would be easier for maintainers this way. > >>> > >>> dts and driver might be merged by different people, but dt-bindings and > >>> drivers are merged by the same people. This is a bindings patch, not a > >> > >> If we do that then I get a bunch of dtbs_check warnings > >> > >> dwc3-usb@f900000: reg: [[0, 261095424, 0, 2048], [0, 261128192, 0, 1024]] is too long > > > > Just my 2 cents: If the binding (and driver) change was truly backward > > compatible (which it should be - for example: errata can only be > > applied if the second property is described), then you want to control > > that reg property to add minItems? - thatm I think will allow the dts > > change to come in at the next cycle once the binding has been merged. > > > > Thanks for the hint. > Please drop patches 4 and 5 in case you pick this series. > > I'll send patch 4 along with the driver series v2. > Patch 5, I'll send after the DT binding has been merged. I suggest to resubmit requisite series (with patches +- or what ever) specific to appropriate maintainers (I don't typically like folks sending driver change along with dts change in a single series without indicating to driver maintainer that dts is something they shouldn't be picking) and avoid any confusion ;) -- Regards, Nishanth Menon Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
