From: "Alim Akhtar" <alim.akhtar@samsung.com>
To: "'Sangwook Shin'" <sw617.shin@samsung.com>, <krzk@kernel.org>,
<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] watchdog: s3c2410_wdt: Fix PMU register bits for ExynosAutoV920 SoC
Date: Thu, 13 Feb 2025 10:25:40 +0530 [thread overview]
Message-ID: <001901db7dd3$88f487e0$9add97a0$@samsung.com> (raw)
In-Reply-To: <20250213004104.3881711-1-sw617.shin@samsung.com>
Hello Sangwook
> -----Original Message-----
> From: Sangwook Shin <sw617.shin@samsung.com>
> Sent: Thursday, February 13, 2025 6:11 AM
> To: krzk@kernel.org; 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>;
> Sangwook Shin <sw617.shin@samsung.com>
> Subject: [PATCH] watchdog: s3c2410_wdt: Fix PMU register bits for
> ExynosAutoV920 SoC
>
> 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>
> Signed-off-by: Sangwook Shin <sw617.shin@samsung.com>
> ---
Reviewed-by: Alim Akhtar <alim.akhtar@samsung.com>
prev parent reply other threads:[~2025-02-13 4:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250213004402epcas2p34923dcba3635ceed9b712a24f354d6f0@epcas2p3.samsung.com>
2025-02-13 0:41 ` [PATCH] watchdog: s3c2410_wdt: Fix PMU register bits for ExynosAutoV920 SoC Sangwook Shin
2025-02-13 2:03 ` Guenter Roeck
2025-02-13 4:55 ` Alim Akhtar [this message]
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='001901db7dd3$88f487e0$9add97a0$@samsung.com' \
--to=alim.akhtar@samsung.com \
--cc=khwan.seo@samsung.com \
--cc=krzk@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox