On 11/02/2023 12:01, Sergio Paracuellos wrote: > On Sat, Feb 11, 2023 at 11:47 AM Arınç ÜNAL <arinc.unal@xxxxxxxxxx> wrote: >> >> On 11.02.2023 13:41, Sergio Paracuellos wrote: >>> On Sat, Feb 11, 2023 at 10:10 AM Arınç ÜNAL <arinc.unal@xxxxxxxxxx> wrote: >>>> >>>> Is this mediatek,sysctl property required after your changes on the >>>> watchdog code? >>> >>> I don't really understand the question :-) Yes, it is. Since we have >>> introduced a new phandle in the watchdog node to be able to access the >>> reset status register through the 'sysc' syscon node. >>> We need the bindings to be aligned with the mt7621.dtsi file and we >>> are getting the syscon regmap handler via >>> 'syscon_regmap_lookup_by_phandle()'. See PATCH 5 of the series, Arınç. >> >> I believe you need to put mediatek,sysctl under "required:". > > Ah, I understood your question now :-). You meant 'required' property. > I need more coffee, I guess :-). I am not sure if you can add > properties as required after bindings are already mainlined for > compatibility issues. The problem with this SoC is that drivers become > mainlined before the device tree was so if things are properly fixed > now this kind of issues appear. Let's see Krzysztof and Rob comments > for this. If your driver fails to probe without mediatek,sysctl, you already made it required (thus broke the ABI) regardless what dt-binding is saying. In such case you should update dt-binding to reflect reality. Now ABI break is different case. Usually you should not break it without valid reasons (e.g. it was never working before). Your commit msg suggests that you only improve the code, thus ABI break is not really justified. In such case - binding is correct, driver should be reworked to accept DTS without the new property. Best regards, Krzysztof
