All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Devang Tailor" <dev.tailor@samsung.com>
To: "'Krzysztof Kozlowski'" <krzk@kernel.org>,
	<alexandre.belloni@bootlin.com>, <robh@kernel.org>,
	<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<alim.akhtar@samsung.com>, <linux-rtc@vger.kernel.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<inux-arm-kernel@lists.infradead.org>,
	<linux-samsung-soc@vger.kernel.org>, <faraz.ata@samsung.com>
Subject: RE: [PATCH 2/3] rtc: s3c: support for exynosautov9 on-chip RTC
Date: Tue, 8 Jul 2025 10:33:24 +0530	[thread overview]
Message-ID: <156b01dbefc5$a3a29aa0$eae7cfe0$@samsung.com> (raw)
In-Reply-To: <3c794a74-30d6-4a16-8bdb-4345b3b5e453@kernel.org>

Hi Krzysztof,


> -----Original Message-----
> From: Krzysztof Kozlowski <krzk@kernel.org>
> Sent: 07 July 2025 14:54
> To: Devang Tailor <dev.tailor@samsung.com>;
> alexandre.belloni@bootlin.com; robh@kernel.org; krzk+dt@kernel.org;
> conor+dt@kernel.org; alim.akhtar@samsung.com; linux-rtc@vger.kernel.org;
> devicetree@vger.kernel.org; linux-kernel@vger.kernel.org; inux-arm-
> kernel@lists.infradead.org; linux-samsung-soc@vger.kernel.org;
> faraz.ata@samsung.com
> Subject: Re: [PATCH 2/3] rtc: s3c: support for exynosautov9 on-chip RTC
> 
> On 02/07/2025 07:24, Devang Tailor wrote:
> > The on-chip RTC of this SoC is almost similar to the previous versions
> > of SoC. Hence re-use the existing driver with platform specific change
> > to enable RTC.
> >
> > This has been tested with 'hwclock' & 'date' utilities
> >
> > Signed-off-by: Devang Tailor <dev.tailor@samsung.com>
> > ---
> >  drivers/rtc/rtc-s3c.c | 26 ++++++++++++++++++++++++++
> > drivers/rtc/rtc-s3c.h |  4 ++++
> >  2 files changed, 30 insertions(+)
> >
> > diff --git a/drivers/rtc/rtc-s3c.c b/drivers/rtc/rtc-s3c.c index
> > 5dd575865adf..00686aa805f2 100644
> > --- a/drivers/rtc/rtc-s3c.c
> > +++ b/drivers/rtc/rtc-s3c.c
> > @@ -384,6 +384,23 @@ static void s3c6410_rtc_disable(struct s3c_rtc
> *info)
> >  	writew(con, info->base + S3C2410_RTCCON);  }
> >
> > +static void exynosautov9_rtc_disable(struct s3c_rtc *info) {
> > +	unsigned int con;
> > +
> > +	con = readb(info->base + S3C2410_RTCCON);
> > +	con &= ~S3C2410_RTCCON_RTCEN;
> > +	writeb(con, info->base + S3C2410_RTCCON);
> > +
> > +	con = readb(info->base + EXYNOSAUTOV9_TICCON0);
> > +	con &= ~EXYNOSAUTOV9_TICCON_TICEN;
> > +	writeb(con, info->base + EXYNOSAUTOV9_TICCON0);
> > +
> > +	con = readb(info->base + EXYNOSAUTOV9_TICCON1);
> > +	con &= ~EXYNOSAUTOV9_TICCON_TICEN;
> > +	writeb(con, info->base + EXYNOSAUTOV9_TICCON1);
> 
> You clear these bits during disable, but why aren't they set during enable?
> Why is this asymmetric? This should be clearly explained, but both commit
> msg and code is completely silent.

OK. I will correct in V2 patch

> 
> > +}
> > +
> >  static void s3c_rtc_remove(struct platform_device *pdev)  {
> >  	struct s3c_rtc *info = platform_get_drvdata(pdev); @@ -574,6 +591,12
> > @@ static struct s3c_rtc_data const s3c6410_rtc_data = {
> >  	.disable		= s3c6410_rtc_disable,
> >  };
> >
> > +static struct s3c_rtc_data const exynosautov9_rtc_data = {
> 
> Please put const after static.

I tried to keep it similar to the existing format, I will correct it in V2 patch.

> 
> 
> 
> Best regards,
> Krzysztof


  reply	other threads:[~2025-07-08  6:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20250702051528epcas5p24abd15d8f554ea057bd6aac586644f4e@epcas5p2.samsung.com>
2025-07-02  5:24 ` [PATCH 0/3] On-chip RTC support for ExynosAutov9 Devang Tailor
2025-07-02  5:24   ` [PATCH 1/3] dt-bindings: rtc: s3c-rtc: add compatible for exynosautov9 Devang Tailor
2025-07-07  9:16     ` Krzysztof Kozlowski
2025-07-02  5:24   ` [PATCH 2/3] rtc: s3c: support for exynosautov9 on-chip RTC Devang Tailor
2025-07-07  9:23     ` Krzysztof Kozlowski
2025-07-08  5:03       ` Devang Tailor [this message]
2025-07-02  5:24   ` [PATCH 3/3] arm64: dts: exynosautov9: add RTC DT node Devang Tailor
2025-07-07  9:23     ` Krzysztof Kozlowski
2025-07-08  5:00       ` Devang Tailor

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='156b01dbefc5$a3a29aa0$eae7cfe0$@samsung.com' \
    --to=dev.tailor@samsung.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=alim.akhtar@samsung.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=faraz.ata@samsung.com \
    --cc=inux-arm-kernel@lists.infradead.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=robh@kernel.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.