From: Heiko Stuebner <heiko@sntech.de>
To: Jianqun Xu <jay.xu@rock-chips.com>, linux-rockchip@lists.infradead.org
Cc: linus.walleij@linaro.org, brgl@bgdev.pl,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
linux-gpio@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Urja Rannikko <urjaman@gmail.com>
Subject: Re: 5.15-rc2 panics on boot on RK3288 veyron speedy, seems related to rockchip pinctrl / gpio split
Date: Sun, 26 Sep 2021 22:11:59 +0200 [thread overview]
Message-ID: <1870262.PYKUYFuaPT@phil> (raw)
In-Reply-To: <CAPCnQJm8ABVsv9uXM2iJ59-DCP1Y65i5zf+pM3yQ0Na8Xfra7Q@mail.gmail.com>
Hi,
Am Sonntag, 26. September 2021, 13:57:33 CEST schrieb Urja Rannikko:
> A boot log of this is attached. I can say that this happens on
> 5.15-rc2 but not on 5.14.7.
>
> Based on the log and some reading of the code my diagnosis is that
> rockchip_pinctrl_probe (via rockchip_pinctrl_register and after that
> the pinctrl core register calls) ends up trying to apply the
> configuration and accesses a null bank->gpio_chip (i think at
> drivers/pinctrl/pinctrl-rockchip.c:2139)
> before the gpio is "populated" / probed a couple of lines later in
> rockchip_pinctrl_probe (line 2710 onwards).
>
> What I don't know is how this is supposed to work and/or how to
> properly fix it, so that's why I'm sending this bug report instead.
>
> I'm sending this to the people who last touched the rockchip pinctrl
> (and gpio), because that's where this log points me to.
See
https://lore.kernel.org/all/20210913224926.1260726-1-heiko@sntech.de/
Heiko
prev parent reply other threads:[~2021-09-26 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 11:57 5.15-rc2 panics on boot on RK3288 veyron speedy, seems related to rockchip pinctrl / gpio split Urja Rannikko
2021-09-26 20:11 ` Heiko Stuebner [this message]
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=1870262.PYKUYFuaPT@phil \
--to=heiko@sntech.de \
--cc=brgl@bgdev.pl \
--cc=jay.xu@rock-chips.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=urjaman@gmail.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