Linux Watchdog driver development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
	Guenter Roeck <linux@roeck-us.net>,
	"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	"biju.das.au" <biju.das.au@gmail.com>,
	"linux-renesas-soc@vger.kernel.org"
	<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 3/5] watchdog: Make RZV2HWDT driver depend on ARCH_R9A09G47
Date: Fri, 24 Jan 2025 14:40:39 +0100	[thread overview]
Message-ID: <18000fea-223b-4e53-8f00-05cad6ceaa75@kernel.org> (raw)
In-Reply-To: <TY3PR01MB113467480CA16AED12555117D86E32@TY3PR01MB11346.jpnprd01.prod.outlook.com>

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
watchdog drivers, which look like could be combined into two drivers (so
each pair of drivers could be combined). For entire Qualcomm family
supporting more SoCs than Renesas there is only one driver.

Best regards,
Krzysztof

  reply	other threads:[~2025-01-24 13:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-15 10:38 [PATCH 0/5] Add support for RZ/G3E WDT Biju Das
2025-01-15 10:38 ` [PATCH 1/5] dt-bindings: watchdog: renesas,wdt: Document RZ/G3E support Biju Das
2025-01-18 15:51   ` Krzysztof Kozlowski
2025-01-23 10:15   ` Geert Uytterhoeven
2025-01-15 10:38 ` [PATCH 3/5] watchdog: Make RZV2HWDT driver depend on ARCH_R9A09G47 Biju Das
2025-01-15 14:55   ` Guenter Roeck
2025-01-15 17:17     ` Biju Das
2025-01-18 15:51   ` Krzysztof Kozlowski
2025-01-24 10:20     ` Biju Das
2025-01-24 10:34       ` Krzysztof Kozlowski
2025-01-24 10:57         ` Biju Das
2025-01-24 12:41           ` Krzysztof Kozlowski
2025-01-24 12:55             ` Biju Das
2025-01-24 13:00               ` Krzysztof Kozlowski
2025-01-24 13:10                 ` Biju Das
2025-01-24 13:20                   ` Krzysztof Kozlowski
2025-01-24 13:24                     ` Biju Das
2025-01-24 13:40                       ` Krzysztof Kozlowski [this message]
2025-01-24 13:51                         ` Biju Das
2025-01-24 13:56                         ` Geert Uytterhoeven
2025-01-19 14:28 ` [PATCH 0/5] Add support for RZ/G3E WDT Tommaso Merciai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=18000fea-223b-4e53-8f00-05cad6ceaa75@kernel.org \
    --to=krzk@kernel.org \
    --cc=biju.das.au@gmail.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=geert+renesas@glider.be \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=wim@linux-watchdog.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox