From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Johan Hovold <johan@kernel.org>
Cc: Jonathan Marek <jonathan@marek.ca>,
linux-arm-msm@vger.kernel.org,
"open list:REAL TIME CLOCK (RTC) SUBSYSTEM"
<linux-rtc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/5] rtc: pm8xxx: implement qcom,no-alarm flag for non-HLOS owned alarm
Date: Wed, 16 Oct 2024 14:26:13 +0200 [thread overview]
Message-ID: <20241016122613e1ba2e2a@mail.local> (raw)
In-Reply-To: <Zw9gZkLPMB9ZBQlh@hovoldconsulting.com>
On 16/10/2024 08:42:46+0200, Johan Hovold wrote:
> On Mon, Oct 14, 2024 at 08:47:26PM -0400, Jonathan Marek wrote:
> > Qualcomm x1e80100 firmware sets the ownership of the RTC alarm to ADSP.
> > Thus writing to RTC alarm registers and receiving alarm interrupts is not
> > possible.
> >
> > Add a qcom,no-alarm flag to support RTC on this platform.
>
> An alternative may be to drop the alarm interrupt from DT and use that
> as an indicator.
>
> > Signed-off-by: Jonathan Marek <jonathan@marek.ca>
> > ---
> > drivers/rtc/rtc-pm8xxx.c | 44 +++++++++++++++++++++++++++-------------
> > 1 file changed, 30 insertions(+), 14 deletions(-)
> >
> > diff --git a/drivers/rtc/rtc-pm8xxx.c b/drivers/rtc/rtc-pm8xxx.c
> > index c32fba550c8e0..1e78939625622 100644
> > --- a/drivers/rtc/rtc-pm8xxx.c
> > +++ b/drivers/rtc/rtc-pm8xxx.c
> > @@ -61,6 +61,7 @@ struct pm8xxx_rtc {
> > struct rtc_device *rtc;
> > struct regmap *regmap;
> > bool allow_set_time;
> > + bool no_alarm;
>
> How about inverting this one and naming it has_alarm or similar to avoid
> the double negation in your conditionals (!no_alarm)?
>
> > int alarm_irq;
> > const struct pm8xxx_rtc_regs *regs;
> > struct device *dev;
> > @@ -473,9 +474,14 @@ static int pm8xxx_rtc_probe(struct platform_device *pdev)
> > if (!rtc_dd->regmap)
> > return -ENXIO;
> >
> > - rtc_dd->alarm_irq = platform_get_irq(pdev, 0);
> > - if (rtc_dd->alarm_irq < 0)
> > - return -ENXIO;
> > + rtc_dd->no_alarm = of_property_read_bool(pdev->dev.of_node,
> > + "qcom,no-alarm");
> > +
>
> Stray newline.
>
> > + if (!rtc_dd->no_alarm) {
> > + rtc_dd->alarm_irq = platform_get_irq(pdev, 0);
> > + if (rtc_dd->alarm_irq < 0)
> > + return -ENXIO;
> > + }
> >
> > rtc_dd->allow_set_time = of_property_read_bool(pdev->dev.of_node,
> > "allow-set-time");
> > @@ -503,7 +509,8 @@ static int pm8xxx_rtc_probe(struct platform_device *pdev)
> >
> > platform_set_drvdata(pdev, rtc_dd);
> >
> > - device_init_wakeup(&pdev->dev, 1);
> > + if (!rtc_dd->no_alarm)
> > + device_init_wakeup(&pdev->dev, 1);
> >
> > rtc_dd->rtc = devm_rtc_allocate_device(&pdev->dev);
> > if (IS_ERR(rtc_dd->rtc))
> > @@ -512,27 +519,36 @@ static int pm8xxx_rtc_probe(struct platform_device *pdev)
> > rtc_dd->rtc->ops = &pm8xxx_rtc_ops;
> > rtc_dd->rtc->range_max = U32_MAX;
> >
> > - rc = devm_request_any_context_irq(&pdev->dev, rtc_dd->alarm_irq,
> > - pm8xxx_alarm_trigger,
> > - IRQF_TRIGGER_RISING,
> > - "pm8xxx_rtc_alarm", rtc_dd);
> > - if (rc < 0)
> > - return rc;
> > + if (!rtc_dd->no_alarm) {
> > + rc = devm_request_any_context_irq(&pdev->dev, rtc_dd->alarm_irq,
> > + pm8xxx_alarm_trigger,
> > + IRQF_TRIGGER_RISING,
> > + "pm8xxx_rtc_alarm", rtc_dd);
> > + if (rc < 0)
> > + return rc;
> > + }
> >
> > rc = devm_rtc_register_device(rtc_dd->rtc);
> > if (rc)
> > return rc;
> >
> > - rc = dev_pm_set_wake_irq(&pdev->dev, rtc_dd->alarm_irq);
> > - if (rc)
> > - return rc;
> > + if (!rtc_dd->no_alarm) {
> > + rc = dev_pm_set_wake_irq(&pdev->dev, rtc_dd->alarm_irq);
> > + if (rc)
> > + return rc;
Also, probe must not fail after devm_rtc_allocate_device has been
called.so you could fix this with this patch.
> > + } else {
> > + clear_bit(RTC_FEATURE_ALARM, rtc_dd->rtc->features);
>
> I assume that you should be clearing the feature bit before registering
> the RTC.
>
> > + }
> >
> > return 0;
> > }
>
> Johan
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-10-16 12:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 0:47 [PATCH v3 0/5] x1e80100 RTC support Jonathan Marek
2024-10-15 0:47 ` [PATCH v3 1/5] rtc: pm8xxx: implement qcom,no-alarm flag for non-HLOS owned alarm Jonathan Marek
2024-10-15 19:24 ` Bjorn Andersson
2024-10-16 6:42 ` Johan Hovold
2024-10-16 12:26 ` Alexandre Belloni [this message]
2024-10-16 12:44 ` Jonathan Marek
2024-10-16 13:02 ` Johan Hovold
2024-10-16 13:12 ` Jonathan Marek
2024-10-16 13:21 ` Johan Hovold
2024-10-15 0:47 ` [PATCH v3 2/5] dt-bindings: rtc: qcom-pm8xxx: document qcom,no-alarm flag Jonathan Marek
2024-10-15 5:33 ` Krzysztof Kozlowski
2024-10-16 6:46 ` Johan Hovold
2024-10-15 0:47 ` [PATCH v3 3/5] arm64: dts: qcom: x1e80100-pmics: enable RTC Jonathan Marek
2024-10-15 0:47 ` [PATCH v3 4/5] arm64: dts: qcom: x1e80100-crd: add rtc offset to set rtc time Jonathan Marek
2024-10-16 6:51 ` Johan Hovold
2024-10-16 13:31 ` Jonathan Marek
2024-10-18 9:44 ` Johan Hovold
2024-10-31 20:09 ` Konrad Dybcio
2024-10-15 0:47 ` [PATCH v3 5/5] arm64: dts: qcom: x1e78100-t14s: " Jonathan Marek
2025-01-12 23:35 ` [PATCH v3 0/5] x1e80100 RTC support Alexandre Belloni
2025-01-20 14:51 ` Johan Hovold
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=20241016122613e1ba2e2a@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=johan@kernel.org \
--cc=jonathan@marek.ca \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox