From: Biju Das <biju.das.jz@bp.renesas.com>
To: Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Biju Das <biju.das.jz@bp.renesas.com>,
Support Opensource <support.opensource@diasemi.com>,
linux-rtc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Biju Das <biju.das.au@gmail.com>,
linux-renesas-soc@vger.kernel.org
Subject: [PATCH v2 0/3] rtc: da9063: Make IRQ as optional
Date: Mon, 4 Dec 2023 13:05:01 +0000 [thread overview]
Message-ID: <20231204130504.126787-1-biju.das.jz@bp.renesas.com> (raw)
On some platforms (eg: RZ/{G2UL,Five} SMARC EVK), there is no IRQ
populated by default. Add irq optional support.
v1->v2:
* Make RTC patch series separate from dt patches.
* Propagated real errors for platform_get_irq_byname_optional().
* Cleared ALARM feature bit for non-irq case.
* Added Rb tag from Geert for patch#2 and #3
* Restored dev_err() for devm_request_threaded_irq() as an RTC can wake
up a system without an IRQ.
Biju Das (3):
rtc: da9063: Make IRQ as optional
rtc: da9063: Use device_get_match_data()
rtc: da9063: Use dev_err_probe()
drivers/rtc/rtc-da9063.c | 89 ++++++++++++++++++----------------------
1 file changed, 41 insertions(+), 48 deletions(-)
--
2.25.1
next reply other threads:[~2023-12-04 13:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 13:05 Biju Das [this message]
2023-12-04 13:05 ` [PATCH v2 1/3] rtc: da9063: Make IRQ as optional Biju Das
2023-12-04 13:25 ` Geert Uytterhoeven
2023-12-04 13:05 ` [PATCH v2 2/3] rtc: da9063: Use device_get_match_data() Biju Das
2023-12-04 13:05 ` [PATCH v2 3/3] rtc: da9063: Use dev_err_probe() Biju Das
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=20231204130504.126787-1-biju.das.jz@bp.renesas.com \
--to=biju.das.jz@bp.renesas.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=biju.das.au@gmail.com \
--cc=geert+renesas@glider.be \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=support.opensource@diasemi.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).