From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sangwook Shin <sw617.shin@samsung.com>,
alim.akhtar@samsung.com, wim@linux-watchdog.org,
linux@roeck-us.net
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
Kyunghwan Seo <khwan.seo@samsung.com>
Subject: Re: [PATCH v2] watchdog: s3c2410_wdt: Fix PMU register bits for ExynosAutoV920 SoC
Date: Tue, 18 Mar 2025 08:19:39 +0100 [thread overview]
Message-ID: <658c00e2-e8ef-4997-bb91-9620e97bafae@kernel.org> (raw)
In-Reply-To: <20250318004411.695786-1-sw617.shin@samsung.com>
On 18/03/2025 01:44, Sangwook Shin wrote:
> From: Kyunghwan Seo <khwan.seo@samsung.com>
>
> Fix the PMU register bits for the ExynosAutoV920 SoC.
> This SoC has different bit information compared to its previous
> version, ExynosAutoV9, and we have made the necessary adjustments.
>
> rst_stat_bit:
> - ExynosAutoV920 cl0 : 0
> - ExynosAutoV920 cl1 : 1
>
> cnt_en_bit:
> - ExynosAutoV920 cl0 : 8
> - ExynosAutoV920 cl1 : 8
>
> Signed-off-by: Kyunghwan Seo <khwan.seo@samsung.com>
> Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> Reviewed-by: Alim Akhtar <alim.akhtar@samsung.com>
> Signed-off-by: Sangwook Shin <sw617.shin@samsung.com>
> ---
> v1 -> v2: Restore previous email history and tags.
>
Why do you send patches which were applied?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-18 7:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250226072535epcas2p46d41cb5cdd7ece18c898657c3c66a219@epcas2p4.samsung.com>
2025-02-26 7:21 ` [PATCH V1 RESEND] watchdog: s3c2410_wdt: Fix PMU register bits for ExynosAutoV920 SoC Sangwook Shin
2025-02-26 7:43 ` Krzysztof Kozlowski
2025-03-18 0:44 ` [PATCH v2] " Sangwook Shin
2025-03-18 7:19 ` Krzysztof Kozlowski [this message]
2025-03-18 8:37 ` sw617.shin
2025-03-18 8:57 ` Krzysztof Kozlowski
2025-03-18 9:25 ` sw617.shin
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=658c00e2-e8ef-4997-bb91-9620e97bafae@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=khwan.seo@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=sw617.shin@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.