From: Lee Jones <lee@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
Janusz Krzysztofik <jmkrzyszt@gmail.com>,
Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org,
Christophe Leroy <christophe.leroy@csgroup.eu>,
andy.shevchenko@gmail.com, Andreas Kemnade <andreas@kemnade.info>
Subject: Re: [PATCH v3] ARM/mfd/gpio: Fixup TPS65010 regression on OMAP1 OSK1
Date: Mon, 15 May 2023 13:36:47 +0100 [thread overview]
Message-ID: <20230515123647.GD10825@google.com> (raw)
In-Reply-To: <20230430093505.561265-1-linus.walleij@linaro.org>
On Sun, 30 Apr 2023, Linus Walleij wrote:
> Aaro reports problems on the OSK1 board after we altered
> the dynamic base for GPIO allocations.
>
> It appears this happens because the OMAP driver now
> allocates GPIO numbers dynamically, so all that is
> references by number is a bit up in the air.
>
> Let's bite the bullet and try to just move the gpio_chip
> in the tps65010 MFD driver over to using dynamic allocations.
> Alter everything in the OSK1 board file to use a GPIO
> descriptor table and lookups.
>
> Utilize the NULL device to define some board-specific
> GPIO lookups and use these to immediately look up the
> same GPIOs, convert to IRQ numbers and pass as resources
> to the devices. This is ugly but should work.
>
> The .setup() callback for tps65010 was used for some GPIO
> hogging, but since the OSK1 is the only user in the entire
> kernel we can alter the signatures to something that
> is helpful and make a clean transition.
>
> Fixes: 92bf78b33b0b ("gpio: omap: use dynamic allocation of base")
> Cc: Christophe Leroy <christophe.leroy@csgroup.eu>
> Cc: andy.shevchenko@gmail.com
> Cc: Andreas Kemnade <andreas@kemnade.info>
> Cc: Lee Jones <lee@kernel.org>
> Reported-by: Aaro Koskinen <aaro.koskinen@iki.fi>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ChangeLog v2->v3:
> - Add proper gpiod table terminators.
> - Use DEFINE_RES_IRQ()
> - Forward-declare struct gpio_chip instead of including a header.
> ChangeLog v1->v2:
> - Fix the CF card GPIO lookup
> - Use the right Fixes: tag
> ---
> arch/arm/mach-omap1/board-osk.c | 137 ++++++++++++++++++++++----------
> drivers/mfd/tps65010.c | 14 ++--
Reviewed-by: Lee Jones <lee@kernel.org>
What's the merge plan for this?
> include/linux/mfd/tps65010.h | 11 +--
> 3 files changed, 102 insertions(+), 60 deletions(-)
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-05-15 12:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-30 9:35 [PATCH v3] ARM/mfd/gpio: Fixup TPS65010 regression on OMAP1 OSK1 Linus Walleij
2023-04-30 10:55 ` Andy Shevchenko
2023-05-15 12:36 ` Lee Jones [this message]
2023-05-15 13:32 ` Linus Walleij
2023-05-16 7:08 ` Lee Jones
2023-05-15 21:02 ` Aaro Koskinen
2023-05-16 12:07 ` Linus Walleij
2023-05-16 15:52 ` Aaro Koskinen
2023-05-16 18:07 ` Linus Walleij
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=20230515123647.GD10825@google.com \
--to=lee@kernel.org \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=andy.shevchenko@gmail.com \
--cc=christophe.leroy@csgroup.eu \
--cc=jmkrzyszt@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.