linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Kemnade <andreas@kemnade.info>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: linux-omap@vger.kernel.org, linux-gpio@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
	Tony Lindgren <tony@atomide.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [BISECTED REGRESSION] OMAP1 GPIO breakage
Date: Tue, 25 Apr 2023 20:11:17 +0200	[thread overview]
Message-ID: <20230425201117.457f224c@aktux> (raw)
In-Reply-To: <20230425173241.GF444508@darkstar.musicnaut.iki.fi>

Hi,

On Tue, 25 Apr 2023 20:32:41 +0300
Aaro Koskinen <aaro.koskinen@iki.fi> wrote:

> Hi,
> 
> It seems GPIOs on OMAP1 boards are somewhat broken after:
> 
> commit 92bf78b33b0b463b00c6b0203b49aea845daecc8
> Author: Andreas Kemnade <andreas@kemnade.info>
> Date:   Fri Jan 13 21:59:22 2023 +0100
> 
>     gpio: omap: use dynamic allocation of base
> 
> E.g. on OSK1 the ethernet IRQ cannot (omap_gpio.0) no longer be requested:
> 
> [    0.277252] Error requesting gpio 0 for smc91x irq
> 
> Also the tps65010 (still using static allocation) will now conflict:
> 
> [    0.400726] gpio gpiochip5: Static allocation of GPIO base is deprecated, use dynamic allocation.
> [    0.400848] gpio gpiochip5: (tps65010): GPIO integer space overlap, cannot add chip
> [    0.400970] gpiochip_add_data_with_key: GPIOs 208..214 (tps65010) failed to register, -16
> [    0.401092] tps65010 i2c-tps65010: can't add gpiochip, err -16
> 
> I think this change should be reverted until the board files and other
> gpiochips are fixed accordingly.
> 
well, then just fix that tps65010 thing. 

that change is itself a regression fix for exactly the same kind of error.
twl4030 gpio registration conflicts with omap gpio registration.
Probably in former times, the dynamic allocation always started at 512, 
so no conflicts between static and dynamic.

So I see two options: either fix the remaining static allocation
or fix allocation so there are no overlaps between static and dynamic.

Regards,
Andreas

  reply	other threads:[~2023-04-25 18:11 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 [this message]
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
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=20230425201117.457f224c@aktux \
    --to=andreas@kemnade.info \
    --cc=aaro.koskinen@iki.fi \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 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).