From: Guenter Roeck <linux@roeck-us.net>
To: Aiden Isik <aidenisik@protonmail.com>
Cc: sashiko-reviews@lists.linux.dev,
Aiden Isik <aidenisik@member.fsf.org>,
devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v2 2/2] watchdog: s3c2410_wdt: Add exynos5515-wdt compatible data
Date: Tue, 18 Aug 2026 12:07:46 -0700 [thread overview]
Message-ID: <e634117e-57be-4c74-973d-3b13cbcaa640@roeck-us.net> (raw)
In-Reply-To: <M_lNzXuQ5wi3MVyFU1JstH_dxQWKDdPGje5yyVFO9lvJsz1H4USWNtew1040JtG4p17UrpWTWoohByvy_x7Nc5dvBh0LuONKNmPZPNMImdg=@protonmail.com>
On 8/18/26 10:56, Aiden Isik wrote:
> Hi Guenter,
>
>> Aiden,
>>
>> On 8/18/26 08:53, sashiko-bot@kernel.org wrote:
>>> Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
>>> - [High] The `drv_data_exynos5515` variant includes `QUIRK_HAS_PMU_AUTO_DISABLE` but fails to define `.disable_reg`, resulting in PMU register corruption at offset 0x0.
>>> - [High] The `drv_data_exynos5515` variant uses an INT_EN register for masking but fails to set `.mask_reset_inv = true`, inverting the watchdog masking logic.
>>> --
>>>
>> Please either address or explain why those are non-issues.
>>
>
> For the 'disable_reg' issue Sashiko flagged, downstream says this:
>
>> /* PMU registers are changed.
>> * MASK_RESET register was replaced by CLUSTERx_NONCPU_INT_TYPE register.
>> * DISABLE register was removed and its value was always fixed by 0.
>> */
>
> Which is why I omitted disable_reg. It no longer exists.
>
What is "downstream" ? I do not see this comment in the patch, not
in linux-next as of next-20260817.
Guenter
next prev parent reply other threads:[~2026-08-18 19:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 15:44 [PATCH v2 0/2] watchdog: Add Exynos5515 watchdog timer support Aiden Isik via B4 Relay
2026-08-18 15:44 ` [PATCH v2 1/2] dt-bindings: watchdog: samsung-wdt: Add exynos5515-wdt compatible Aiden Isik via B4 Relay
2026-08-18 15:56 ` sashiko-bot
2026-08-18 15:44 ` [PATCH v2 2/2] watchdog: s3c2410_wdt: Add exynos5515-wdt compatible data Aiden Isik via B4 Relay
2026-08-18 15:53 ` sashiko-bot
2026-08-18 16:43 ` Guenter Roeck
2026-08-18 17:56 ` Aiden Isik
2026-08-18 19:07 ` Guenter Roeck [this message]
2026-08-18 19:32 ` Aiden Isik
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=e634117e-57be-4c74-973d-3b13cbcaa640@roeck-us.net \
--to=linux@roeck-us.net \
--cc=aidenisik@member.fsf.org \
--cc=aidenisik@protonmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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