Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: Andrea della Porta <andrea.porta@suse.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
	Andrea della Porta <andrea.porta@suse.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-gpio@vger.kernel.org
Subject: Re: [PATCH 13/21] pinctrl: remove unneeded 'fast_io' parameter in regmap_config
Date: Wed, 13 Aug 2025 21:42:17 +0200	[thread overview]
Message-ID: <aJzqmX-Nh3bWgjWn@apocalypse> (raw)
In-Reply-To: <20250813161517.4746-14-wsa+renesas@sang-engineering.com>

Hi Wolfram,

On 18:14 Wed 13 Aug     , 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/pinctrl/pinctrl-rp1.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/drivers/pinctrl/pinctrl-rp1.c b/drivers/pinctrl/pinctrl-rp1.c
> index dadafc935dbb..6699b36349d0 100644
> --- a/drivers/pinctrl/pinctrl-rp1.c
> +++ b/drivers/pinctrl/pinctrl-rp1.c
> @@ -1627,7 +1627,6 @@ static const struct regmap_config rp1_pinctrl_regmap_cfg = {
>  	.reg_bits = 32,
>  	.val_bits = 32,
>  	.reg_stride = 4,
> -	.fast_io = true,
>  	.name = "rp1-pinctrl",
>  };

Looks fine to me, just a little heads up: the following patch
https://lore.kernel.org/all/20250812092618.14270-1-andrea.porta@suse.com/

adds other two regmap_config with fast_io set to true, so we can
get rid of them too. I can do it in my patch in case I have to send a
second revision, or you can amend yours to cope with my changes and set
my patch as a prerequisite. I guess that it's easier for me since
I have only a single patch, while yours is a big patchset so better
to avoid the noise of a second revision.

Many thanks,
Andrea

>  
> -- 
> 2.47.2
> 

  reply	other threads:[~2025-08-13 19:40 UTC|newest]

Thread overview: 13+ 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 03/21] gpio: " Wolfram Sang
2025-08-14  7:20   ` Bartosz Golaszewski
2025-08-13 16:14 ` [PATCH 13/21] pinctrl: " Wolfram Sang
2025-08-13 19:42   ` Andrea della Porta [this message]
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 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=aJzqmX-Nh3bWgjWn@apocalypse \
    --to=andrea.porta@suse.com \
    --cc=broonie@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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