From: Manuel Traut <manuel.traut@mt.com>
To: Markus Burri <markus.burri@mt.com>
Cc: linux-kernel@vger.kernel.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Marek Vasut <marex@denx.de>,
linux-rtc@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/5] rtc-rv8803: add new type for rv8901
Date: Wed, 19 Feb 2025 16:33:42 +0100 [thread overview]
Message-ID: <Z7X51iji1R8X0UAJ@mt.com> (raw)
In-Reply-To: <20250116131532.471040-3-markus.burri@mt.com>
On Thu, Jan 16, 2025 at 02:15:29PM +0100, Markus Burri wrote:
> The rtc-rv8901 has additional functionality (tamper detection).
> To support this additional functionality the type must be extended.
>
> Signed-off-by: Markus Burri <markus.burri@mt.com>
Reviewed-by: Manuel Traut <manuel.traut@mt.com>
> ---
> drivers/rtc/rtc-rv8803.c | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/rtc/rtc-rv8803.c b/drivers/rtc/rtc-rv8803.c
> index 1327251e5..50fbae931 100644
> --- a/drivers/rtc/rtc-rv8803.c
> +++ b/drivers/rtc/rtc-rv8803.c
> @@ -62,7 +62,8 @@ enum rv8803_type {
> rv_8803,
> rx_8803,
> rx_8804,
> - rx_8900
> + rx_8900,
> + rx_8901,
> };
>
> struct rv8803_data {
> @@ -173,7 +174,8 @@ static int rv8803_regs_reset(struct rv8803_data *rv8803, bool full)
> * The RV-8803 resets all registers to POR defaults after voltage-loss,
> * the Epson RTCs don't, so we manually reset the remainder here.
> */
> - if (full || rv8803->type == rx_8803 || rv8803->type == rx_8900) {
> + if (full || rv8803->type == rx_8803 || rv8803->type == rx_8900 ||
> + rv8803->type == rx_8901) {
> int ret = rv8803_regs_init(rv8803);
> if (ret)
> return ret;
> @@ -635,6 +637,7 @@ static const struct i2c_device_id rv8803_id[] = {
> { "rv8804", rx_8804 },
> { "rx8803", rx_8803 },
> { "rx8900", rx_8900 },
> + { "rx8901", rx_8901 },
> { }
> };
> MODULE_DEVICE_TABLE(i2c, rv8803_id);
> @@ -760,6 +763,10 @@ static const __maybe_unused struct of_device_id rv8803_of_match[] = {
> .compatible = "epson,rx8900",
> .data = (void *)rx_8900
> },
> + {
> + .compatible = "epson,rx8901",
> + .data = (void *)rx_8901
> + },
> { }
> };
> MODULE_DEVICE_TABLE(of, rv8803_of_match);
> --
> 2.39.5
>
next prev parent reply other threads:[~2025-02-19 15:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 13:15 [PATCH v2 0/5] rtc-rv8803: Implement timestamp trigger over event pins Markus Burri
2025-01-16 13:15 ` [PATCH v2 1/5] dt-bindings: rtc: add new type for epson,rx8901 Markus Burri
2025-02-19 15:32 ` Manuel Traut
2025-01-16 13:15 ` [PATCH v2 2/5] rtc-rv8803: add new type for rv8901 Markus Burri
2025-02-19 15:33 ` Manuel Traut [this message]
2025-01-16 13:15 ` [PATCH v2 3/5] rtc-rv8803: add tamper function to sysfs " Markus Burri
2025-02-19 16:20 ` Manuel Traut
2025-01-16 13:15 ` [PATCH v2 4/5] rtc-rv8803: extend sysfs to trigger internal ts-event Markus Burri
2025-02-19 16:23 ` Manuel Traut
2025-01-16 13:15 ` [PATCH v2 5/5] rtc-rv8803: extend sysfs to read status Markus Burri
2025-02-19 16:33 ` Manuel Traut
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=Z7X51iji1R8X0UAJ@mt.com \
--to=manuel.traut@mt.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=marex@denx.de \
--cc=markus.burri@mt.com \
--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 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 NNTP newsgroup(s).