From: Krzysztof Kozlowski <krzk@kernel.org>
To: Antoni Pokusinski <apokusinski01@gmail.com>,
alexandre.belloni@bootlin.com, krzk+dt@kernel.org,
conor+dt@kernel.org, robh@kernel.org,
alexander.stein@ew.tq-group.com
Cc: linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/3] rtc: pcf85063: add support for RV8063
Date: Tue, 8 Apr 2025 08:14:36 +0200 [thread overview]
Message-ID: <b42d082e-0568-4d2c-849c-a0b9ab762afd@kernel.org> (raw)
In-Reply-To: <20250407193521.634807-3-apokusinski01@gmail.com>
On 07/04/2025 21:35, Antoni Pokusinski wrote:
> Microcrystal RV8063 is a real-time clock with SPI interface. Its
> functionality is very similar to the RV8263 rtc.
>
> Signed-off-by: Antoni Pokusinski <apokusinski01@gmail.com>
> ---
> drivers/rtc/Kconfig | 21 ++++++-----
> drivers/rtc/rtc-pcf85063.c | 74 +++++++++++++++++++++++++++++++++++++-
> 2 files changed, 85 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig
> index 838bdc138ffe..1b9be96faa13 100644
> --- a/drivers/rtc/Kconfig
> +++ b/drivers/rtc/Kconfig
> @@ -483,15 +483,6 @@ config RTC_DRV_PCF8523
> This driver can also be built as a module. If so, the module
> will be called rtc-pcf8523.
>
> -config RTC_DRV_PCF85063
> - tristate "NXP PCF85063"
> - select REGMAP_I2C
> - help
> - If you say yes here you get support for the PCF85063 RTC chip
> -
> - This driver can also be built as a module. If so, the module
> - will be called rtc-pcf85063.
> -
> config RTC_DRV_PCF85363
> tristate "NXP PCF85363"
> select REGMAP_I2C
> @@ -971,6 +962,18 @@ config RTC_DRV_PCF2127
> This driver can also be built as a module. If so, the module
> will be called rtc-pcf2127.
>
> +config RTC_DRV_PCF85063
Why? This breaks the order.
> + tristate "NXP PCF85063"
> + depends on RTC_I2C_AND_SPI
> + select REGMAP_I2C if I2C
> + select REGMAP_SPI if SPI_MASTER
> + help
> + If you say yes here you get support for the PCF85063 and RV8063
> + RTC chips.
> +
> + This driver can also be built as a module. If so, the module
> + will be called rtc-pcf85063.
> +
...
> module_exit(pcf85063_exit);
> @@ -740,3 +811,4 @@ module_exit(pcf85063_exit);
> MODULE_AUTHOR("Søren Andersen <san@rosetechnology.dk>");
> MODULE_DESCRIPTION("PCF85063 RTC driver");
> MODULE_LICENSE("GPL");
> +MODULE_ALIAS("spi:rv8063");
Drop and use proper ID tables.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-04-08 6:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 19:35 [PATCH 0/3] add support for RV8063 SPI rtc Antoni Pokusinski
2025-04-07 19:35 ` [PATCH 1/3] rtc: pcf85063: create pcf85063_i2c_probe Antoni Pokusinski
2025-04-07 19:35 ` [PATCH 2/3] rtc: pcf85063: add support for RV8063 Antoni Pokusinski
2025-04-08 6:14 ` Krzysztof Kozlowski [this message]
2025-04-08 7:36 ` Alexandre Belloni
2025-04-08 19:00 ` Antoni Pokusinski
2025-04-07 19:35 ` [PATCH 3/3] dt-bindings: rtc: add binding " Antoni Pokusinski
2025-04-10 21:13 ` Rob Herring
2025-04-11 7:11 ` Antoni Pokusinski
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=b42d082e-0568-4d2c-849c-a0b9ab762afd@kernel.org \
--to=krzk@kernel.org \
--cc=alexander.stein@ew.tq-group.com \
--cc=alexandre.belloni@bootlin.com \
--cc=apokusinski01@gmail.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=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