RE: [PATCH 3/5] watchdog: Make RZV2HWDT driver depend on ARCH_R9A09G47

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Krzysztof Kozlowski,

> -----Original Message-----
> From: Krzysztof Kozlowski <krzk@xxxxxxxxxx>
> Sent: 24 January 2025 10:35
> Subject: Re: [PATCH 3/5] watchdog: Make RZV2HWDT driver depend on ARCH_R9A09G47
> 
> On 24/01/2025 11:20, Biju Das wrote:
> >>
> >>> +	depends on ARCH_R9A09G047 || ARCH_R9A09G057 || COMPILE_TEST
> >>
> >> But this is just wrong. You are supposed to depend on renesas ARHC,
> >> not your individual SoC (and this is what you called here "ARCH_R9A...").
> >>
> >> Greg many times gave strong opinion that even full ARCH is wrong and
> >> we managed to convince him that it has a meaning (or he did not want
> >> to keep discussing). But restricting it per soc is pointless and impossible to defend in
> discussion.
> >
> > Currently for building RZ/G3E WDT, I need to always have RZ/V2H SoC config.
> > which is pointless. May be ARCH_RENESAS should ok in this case??
> Assuming ARCH_RENESAS covers your individual SoCs above, yes, that's the way for driver to limit
> themselves to usable family.

ARCH_RENESAS has ARM, ARM64 and RISC based SoCs.

Currently it covers ARCH_RCAR_GEN1, ARCH_RCAR_GEN2,
 ARCH_RCAR_GEN3, ARCH_RCAR_GEN4, ARCH_RMOBILE, ARCH_RZG2L, ARCH_RZN1
Family SOCs and rest of the individual SoCs such as RZ/V2H abnd RZ/g3E.

Since most of IP's in RZ/V2H and RZ/G3E are identical we could introduce 
a new family SoC ARCH_RZG3E_RZV2H to cover both or top level ARCH_RENESAS??

Cheers,
Biju

	




[Index of Archives]     [Linux Samsung SOC]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux