On 26/10/2021 03:47, Youngmin Nam wrote: >> If everyone added a new driver to avoid integrating with existing code, >> we would have huge kernel with thousands of duplicated solutions. The >> kernel also would be unmaintained. >> >> Such arguments were brought before several times - "I don't want to >> integrating with existing code", "My use case is different", "I would >> need to test the other cases", "It's complicated for me". >> >> Instead of pushing a new vendor driver you should integrate it with >> existing code. >> > Let me ask you one question. > If we maintain as one driver, how can people who don't have the new MCT test the new driver? I assume you talk about a case when someone else later changes something in the driver. Such person doesn't necessarily have to test it. The same as in all other cases (Exynos MCT is not special here): just ask for testing on platform one doesn't have. Even if you submit this as separate driver, there is the exact same problem. People will change the MCTv2 driver without access to hardware. None of these differ for Exynos MCT from other drivers, e.g. mentioned Samsung PMIC drivers, recently modified (by Will and Sam) the SoC clock drivers or the ChipID drivers (changed by Chanho). Best regards, Krzysztof
