From: Drew Fustini <fustini@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Guo Ren <guoren@kernel.org>, Fu Wei <wefu@redhat.com>,
linux-arm-msm@vger.kernel.org, linux-riscv@lists.infradead.org,
Michal Wilczynski <m.wilczynski@samsung.com>,
Icenowy Zheng <uwu@icenowy.me>, Yao Zi <ziyao@disroot.org>
Subject: Re: [PATCH 16/21] reset: remove unneeded 'fast_io' parameter in regmap_config
Date: Wed, 13 Aug 2025 11:28:46 -0700 [thread overview]
Message-ID: <aJzZXvSjoAVa8kjF@x1> (raw)
In-Reply-To: <20250813161517.4746-17-wsa+renesas@sang-engineering.com>
On Wed, Aug 13, 2025 at 06:15:02PM +0200, 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/reset/reset-intel-gw.c | 1 -
> drivers/reset/reset-qcom-pdc.c | 1 -
> drivers/reset/reset-th1520.c | 1 -
> 3 files changed, 3 deletions(-)
[snip]
> diff --git a/drivers/reset/reset-th1520.c b/drivers/reset/reset-th1520.c
> index 7874f0693e1b..3ec22ae1fac1 100644
> --- a/drivers/reset/reset-th1520.c
> +++ b/drivers/reset/reset-th1520.c
> @@ -78,7 +78,6 @@ static const struct regmap_config th1520_reset_regmap_config = {
> .reg_bits = 32,
> .val_bits = 32,
> .reg_stride = 4,
> - .fast_io = true,
> };
>
> static int th1520_reset_probe(struct platform_device *pdev)
> --
> 2.47.2
Acked-by: Drew Fustini <fustini@kernel.org> # for reset-th1520.c
next prev parent reply other threads:[~2025-08-13 18:28 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 16:14 [PATCH 00/21] treewide: remove unneeded 'fast_io' parameter in regmap_config 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 [this message]
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
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=aJzZXvSjoAVa8kjF@x1 \
--to=fustini@kernel.org \
--cc=broonie@kernel.org \
--cc=guoren@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=m.wilczynski@samsung.com \
--cc=p.zabel@pengutronix.de \
--cc=uwu@icenowy.me \
--cc=wefu@redhat.com \
--cc=wsa+renesas@sang-engineering.com \
--cc=ziyao@disroot.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).