From: Tony Lindgren <tony@atomide.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
Janusz Krzysztofik <jmkrzyszt@gmail.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Kevin Hilman <khilman@kernel.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Andy Shevchenko <andy@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH] OMAP/gpio: drop MPUIO static base
Date: Tue, 26 Sep 2023 10:09:53 +0300 [thread overview]
Message-ID: <20230926070953.GV5285@atomide.com> (raw)
In-Reply-To: <20230912-omap-mpuio-base-v1-1-290d9bd24b23@linaro.org>
* Linus Walleij <linus.walleij@linaro.org> [230912 08:45]:
> The OMAP GPIO driver hardcodes the MPIO chip base, but there
> is no point: we have already moved all consumers over to using
> descriptor look-ups.
>
> Drop the MPUIO GPIO base and use dynamic assignment.
>
> Root out the unused instances of the OMAP_MPUIO() macro and
> delete the unused OMAP_GPIO_IS_MPUIO() macro.
>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> Maybe Bartosz can merge this into the GPIO tree with Tony's
> et al blessing?
Best to wait for Tested-by from Aaro on this one.
As far as I'm concerned, good to see this:
Reviewed-by: Tony Lindgren <tony@atomide.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-09-26 7:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 8:44 [PATCH] OMAP/gpio: drop MPUIO static base Linus Walleij
2023-09-26 7:09 ` Tony Lindgren [this message]
2023-10-04 0:36 ` Janusz Krzysztofik
2023-10-04 10:23 ` Linus Walleij
2023-10-04 9:37 ` Bartosz Golaszewski
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=20230926070953.GV5285@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=andy@kernel.org \
--cc=brgl@bgdev.pl \
--cc=grygorii.strashko@ti.com \
--cc=jmkrzyszt@gmail.com \
--cc=khilman@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=ssantosh@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).