From: Linus Walleij <linus.walleij@linaro.org>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"kernelci-results@groups.io" <kernelci-results@groups.io>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Johan Hovold <johan@kernel.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Collabora Kernel ML <kernel@collabora.com>,
Sean Wang <sean.wang@kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>
Subject: Re: linusw/devel bisection: baseline.bootrr.mediatek-mt8173-pinctrl-probed on mt8173-elm-hana
Date: Tue, 15 Dec 2020 13:20:34 +0100 [thread overview]
Message-ID: <CACRpkdbozXM3FHQB9+GcPJZdNT+Vi1223m2uEqqJ21ukY1A4Gw@mail.gmail.com> (raw)
In-Reply-To: <483b08f2-09c3-e753-d2ce-4e34fee627f3@collabora.com>
On Mon, Dec 14, 2020 at 11:28 PM Guillaume Tucker
<guillaume.tucker@collabora.com> wrote:
> Please see the bisection report below about the pinctrl driver
> failing to probe on the arm64 mt8173-elm-hana platform.
That's an excellent, helpful report which helps a lot!
Thank you for doing this!
> This is the error message:
>
> [ 0.051788] gpio gpiochip0: Detected name collision for GPIO name ''
> [ 0.051813] gpio gpiochip0: GPIO name collision on the same chip, this is not allowed, fix all lines on the chip to have unique names
> [ 0.051832] gpiochip_add_data_with_key: GPIOs 377..511 (1000b000.pinctrl) failed to register, -17
> [ 0.051946] mediatek-mt8173-pinctrl: probe of 1000b000.pinctrl failed with error -22
It seems we need to teach the core to ignore the name (empty string).
Yours,
Linus Walleij
next prev parent reply other threads:[~2020-12-15 12:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5fd76cf2.1c69fb81.6f19b.b16a@mx.google.com>
2020-12-14 22:28 ` linusw/devel bisection: baseline.bootrr.mediatek-mt8173-pinctrl-probed on mt8173-elm-hana Guillaume Tucker
2020-12-15 12:20 ` Linus Walleij [this message]
2020-12-16 10:10 ` Guillaume Tucker
2020-12-16 12:41 ` Linus Walleij
2020-12-16 17:30 ` Guillaume Tucker
2020-12-16 20:52 ` 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=CACRpkdbozXM3FHQB9+GcPJZdNT+Vi1223m2uEqqJ21ukY1A4Gw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=bgolaszewski@baylibre.com \
--cc=enric.balletbo@collabora.com \
--cc=geert+renesas@glider.be \
--cc=guillaume.tucker@collabora.com \
--cc=johan@kernel.org \
--cc=kernel@collabora.com \
--cc=kernelci-results@groups.io \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=sean.wang@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).