From: Tony Lindgren <tony@atomide.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Andreas Kemnade <andreas@kemnade.info>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
linux-omap@vger.kernel.org, linux-gpio@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [BISECTED REGRESSION] OMAP1 GPIO breakage
Date: Thu, 27 Apr 2023 10:03:07 +0300 [thread overview]
Message-ID: <20230427070307.GF14287@atomide.com> (raw)
In-Reply-To: <CACRpkdb7a32Ny=JR7=pAW_QRMj-S5QuhcSN8U6_f4PhAXj5pRA@mail.gmail.com>
* Linus Walleij <linus.walleij@linaro.org> [230426 20:36]:
> On Wed, Apr 26, 2023 at 9:19 AM Tony Lindgren <tony@atomide.com> wrote:
>
> > Not sure what the best way to fix this might be, adding Linus W to Cc too.
> > Maybe using gpio line names in the legacy platform data instead of numbers?
>
> I sent a fat invasive fix which, if it works, will fix the problem once and
> for all on OSK1.
>
> If it works, I can write the same fix for Nokia 770 or whatever.
>
> I think it is best to just get rid of the static GPIO numbers from these
> boards so I took a stab at that.
OK makes sense to me thanks!
Tony
next prev parent reply other threads:[~2023-04-27 7:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 17:32 [BISECTED REGRESSION] OMAP1 GPIO breakage Aaro Koskinen
2023-04-25 18:11 ` Andreas Kemnade
2023-04-25 18:38 ` Aaro Koskinen
2023-04-25 19:20 ` Andreas Kemnade
2023-04-25 19:36 ` Aaro Koskinen
2023-04-25 19:58 ` Andreas Kemnade
2023-04-26 7:19 ` Tony Lindgren
2023-04-26 7:39 ` Andreas Kemnade
2023-04-26 10:52 ` andy.shevchenko
2023-04-26 18:29 ` Andreas Kemnade
2023-04-26 20:36 ` Linus Walleij
2023-04-27 7:03 ` Tony Lindgren [this message]
2023-04-27 8:38 ` Bartosz Golaszewski
2023-05-04 5:51 ` Tony Lindgren
2023-05-04 12:13 ` Linus Walleij
2023-05-04 12:45 ` Andreas Kemnade
2023-05-05 8:38 ` Tony Lindgren
2023-04-26 20:12 ` Andreas Kemnade
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=20230427070307.GF14287@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=bartosz.golaszewski@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.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).