Hi Krzysztof, On Fri, Jan 24, 2025 at 2:40 PM Krzysztof Kozlowski <krzk@xxxxxxxxxx> wrote: > On 24/01/2025 14:24, Biju Das wrote: > >>>>> config K3_RTI_WATCHDOG > >>>>> tristate "Texas Instruments K3 RTI watchdog" > >>>>> depends on ARCH_K3 || COMPILE_TEST > >>>> > >>>> Dependency on ARCH. > >>>> > >>>> Do you understand the difference between ARCH and SoC (ARCH_R9A09G47 > >>>> is the SoC - individual or family)? > >>> > >>> ARCH_R9A09G47 --> Is a SoC (RZ/G3E) > >>> ARCH_R9A09G57 --> Is a SoC (RZ/V2H) > >>> > >>> 90%of IP between these SoCs are same. So can't this belongs to same family of SoCs(eg: > >> ARCH_RZ_G3E_V2H family)? > >> > >> > >> We do not discuss what these SoCs belong to. How does it matter if you create > >> ARCH_RZ_ONE_TWO_THREE_SOCS? Your dependency is ARCH, so unified kernel image will be easier to create. > >> This is not helping in unified image and Greg was talking about this *multiple times*. > > > Renesas needs to finally start integrating the drivers and treating your > SoCs in unified way leading to unified kernel image. You have four How does this prevent creating a unified kernel image? None of these ARCH_*-symbols are mutually-exclusive. (out-of-tree[1]) renesas_defconfig supports all Renesas ARM64 SoCs. The standard arm64 defconfig should work, too. > watchdog drivers, which look like could be combined into two drivers (so > each pair of drivers could be combined). For entire Qualcomm family All of them can be combined into a unified kernel image. > supporting more SoCs than Renesas there is only one driver. Different watchdog hardware, different drivers... [1] https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git/log/?h=topic/renesas-defconfig Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
