On 22/12/2022 12:48, AngeloGioacchino Del Regno wrote: > Some old MediaTek clock drivers are starting the clock count (so, the > clock ID) from one instead of zero and this is logically incorrect, > as we should start from 0. > During a cleanup an issue emerged due to that and the cleanest and > shortest way to keep devicetree backwards compatibility while still > performing the well deserved cleanup is to add a dummy clock where > needed, with ID 0. Unfortunately I do not understand at all why adding dummy (fake) ID cleans anything here. Unifying IDs to start from 0 is not an argument on DT bindings header IDs. Best regards, Krzysztof
