From: Neil Armstrong <neil.armstrong@linaro.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-kernel@vger.kernel.org
Cc: Mark Brown <broonie@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-rtc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH 17/21] rtc: remove unneeded 'fast_io' parameter in regmap_config
Date: Thu, 14 Aug 2025 16:20:06 +0200 [thread overview]
Message-ID: <382972ef-92e2-44b3-a510-37009fa2f781@linaro.org> (raw)
In-Reply-To: <20250813161517.4746-18-wsa+renesas@sang-engineering.com>
On 13/08/2025 18:15, Wolfram Sang wrote:
> When using MMIO with regmap, fast_io is implied. No need to set it
> again.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
> No dependencies, can be applied directly to the subsystem tree. Buildbot is
> happy, too.
>
> drivers/rtc/rtc-meson.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/rtc/rtc-meson.c b/drivers/rtc/rtc-meson.c
> index 47e9ebf58ffc..21eceb9e2e13 100644
> --- a/drivers/rtc/rtc-meson.c
> +++ b/drivers/rtc/rtc-meson.c
> @@ -72,7 +72,6 @@ static const struct regmap_config meson_rtc_peripheral_regmap_config = {
> .val_bits = 32,
> .reg_stride = 4,
> .max_register = RTC_REG4,
> - .fast_io = true,
> };
>
> /* RTC front-end serialiser controls */
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
next prev parent reply other threads:[~2025-08-14 14:20 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 16:14 [PATCH 00/21] treewide: " Wolfram Sang
2025-08-13 16:14 ` [PATCH 01/21] bus: " Wolfram Sang
2025-08-13 16:14 ` [PATCH 02/21] clk: " Wolfram Sang
2025-08-21 21:46 ` Brian Masney
2025-08-22 5:59 ` Wolfram Sang
2025-08-13 16:14 ` [PATCH 03/21] gpio: " Wolfram Sang
2025-08-14 7:20 ` Bartosz Golaszewski
2025-08-13 16:14 ` [PATCH 04/21] drm: " Wolfram Sang
2025-08-15 15:06 ` Philipp Zabel
2025-08-18 2:03 ` Liu Ying
2025-08-13 16:14 ` [PATCH 05/21] iio: " Wolfram Sang
2025-08-16 12:34 ` Jonathan Cameron
2025-08-13 16:14 ` [PATCH 06/21] Input: " Wolfram Sang
2025-08-13 21:47 ` Dmitry Torokhov
2025-08-13 16:14 ` [PATCH 07/21] mailbox: " Wolfram Sang
2025-08-13 16:14 ` [PATCH 08/21] media: " Wolfram Sang
2025-08-13 16:14 ` [PATCH 09/21] mfd: " Wolfram Sang
2025-09-02 13:33 ` (subset) " Lee Jones
2025-08-13 16:14 ` [PATCH 10/21] mmc: " Wolfram Sang
2025-08-18 10:55 ` Ulf Hansson
2025-08-13 16:14 ` [PATCH 11/21] peci: " Wolfram Sang
2025-08-14 5:11 ` Paul Menzel
2025-08-13 16:14 ` [PATCH 12/21] phy: " Wolfram Sang
2025-08-13 16:14 ` [PATCH 13/21] pinctrl: " Wolfram Sang
2025-08-13 19:42 ` Andrea della Porta
2025-08-19 12:02 ` Linus Walleij
2025-08-19 12:04 ` Wolfram Sang
2025-08-19 12:25 ` Andrea della Porta
2025-08-13 16:15 ` [PATCH 14/21] pmdomain: " Wolfram Sang
2025-08-19 12:26 ` Ulf Hansson
2025-08-13 16:15 ` [PATCH 15/21] regulator: " Wolfram Sang
2025-08-13 16:15 ` [PATCH 16/21] reset: " Wolfram Sang
2025-08-13 18:28 ` Drew Fustini
2025-08-14 10:56 ` Philipp Zabel
2025-08-13 16:15 ` [PATCH 17/21] rtc: " Wolfram Sang
2025-08-14 14:20 ` Neil Armstrong [this message]
2025-09-14 23:18 ` (subset) " Alexandre Belloni
2025-08-13 16:15 ` [PATCH 18/21] soc: " Wolfram Sang
2025-08-14 9:29 ` Konrad Dybcio
2025-08-13 16:15 ` [PATCH 19/21] spi: " Wolfram Sang
2025-08-13 16:15 ` [PATCH 20/21] thermal: " Wolfram Sang
2025-08-13 16:15 ` [PATCH 21/21] ASoC: " Wolfram Sang
2025-08-13 21:28 ` (subset) [PATCH 00/21] treewide: " Mark Brown
2025-08-14 11:13 ` Mark Brown
2025-08-14 14:18 ` Mark Brown
2025-08-15 14:42 ` Bjorn Andersson
2025-08-20 17:02 ` Vinod Koul
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=382972ef-92e2-44b3-a510-37009fa2f781@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=wsa+renesas@sang-engineering.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
all inboxes | Powered by JetHome®