From: jmondi <jacopo@jmondi.org>
To: Chris Brandt <Chris.Brandt@renesas.com>
Cc: "linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
Jacopo Mondi <jacopo+renesas@jmondi.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: The RZ/A1 pin controller driver will be broken for 4.13
Date: Wed, 30 Aug 2017 08:46:56 +0200 [thread overview]
Message-ID: <20170830064656.GA5584@w540> (raw)
In-Reply-To: <SG2PR06MB1165ADDEBA8097EA034C27D28A9F0@SG2PR06MB1165.apcprd06.prod.outlook.com>
Hi Chris,
thanks for bisecting this down to the problem
On Tue, Aug 29, 2017 at 06:56:53PM +0000, Chris Brandt wrote:
> Just FYI,
>
> After pulling Geert's new renesas-drivers-2017-08-29-v4.13-rc7, I tried
> testing RZ/A1 and it hangs during boot.
>
> Basically...
>
> [ 110.329579] pinctrl-rza1 fcfe3000.pin-controller: Parsed gpiochip gpio-0-0 with 6 pins
> [ 112.970056] pinctrl-rza1 fcfe3000.pin-controller: Parsed gpiochip gpio-1-1 with 16 pins
> (hangs here forever)
>
>
> After some debug, I found that this commit broke the new
> drivers/pinctrl/pinctrl-rza1.c driver.
>
> 108d23e322a2 ("gpiolib: request the gpio before querying its direction")
>
> Looks like it was added for -rc5.
>
> If I revert that one patch, RZ/A1 boots fine.
>
> Since we're at -rc7, I probably won't have time to fix it before the
> release.
I tried -rc1 on a Peach, not -rc5 :(
I will have a look into that and see how bad this is
>
> Poor RZ/A1 pinctrl driver...it took so long to get into mainline, and
> then it only worked for 1 release.
>
Yeah, that's definitely bad karma for this platform
Thanks
j
> :(
>
>
> Chris
>
next prev parent reply other threads:[~2017-08-30 6:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 18:56 The RZ/A1 pin controller driver will be broken for 4.13 Chris Brandt
2017-08-30 6:46 ` jmondi [this message]
2017-08-30 8:26 ` Geert Uytterhoeven
2017-08-30 12:01 ` jmondi
2017-08-30 12:57 ` Chris Brandt
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=20170830064656.GA5584@w540 \
--to=jacopo@jmondi.org \
--cc=Chris.Brandt@renesas.com \
--cc=geert@linux-m68k.org \
--cc=jacopo+renesas@jmondi.org \
--cc=linux-renesas-soc@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 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.