From: Simon Horman <horms@verge.net.au>
To: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Cc: linux-sh@vger.kernel.org, linux-gpio@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Possible regression in next-20150310 due to pinctrl: sh-pfc: r8a7790: Remove non existing GPIO pins
Date: Tue, 10 Mar 2015 16:55:39 +0900 [thread overview]
Message-ID: <20150310075538.GA20709@verge.net.au> (raw)
Hi,
I have observed what appears to be a regression in next-20150310. Using
the shmobile_defconfig the lager board does not produce console output
whatsoever. If I revert bfb6698fad74e7ba2 ("pinctrl: sh-pfc: r8a7790:
Remove non existing GPIO pins") then the problem seems to be resolved.
Likewise for the koelsh board and 896498d439cec6ff0 ("pinctrl: sh-pfc:
r8a7791: Remove non existing GPIO pins").
N.B.: In order to boot all the way to user-space I also need to revert
5da0e63e268dc5120 ("mmc: tmio: Fix PIO mode with CONFIG_HIGHMEM"), a
problem that I have reported separately[1].
[1] Possible regression in next-20150306 due to "mmc: tmio: Fix PIO mode
with CONFIG_HIGHMEM"
http://www.spinics.net/lists/linux-sh/msg40804.html
> > Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
>
> Patch applied with Geert's ACK.
>
> Yours,
> Linus Walleij
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next reply other threads:[~2015-03-10 7:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 7:55 Simon Horman [this message]
2015-03-10 9:30 ` Possible regression in next-20150310 due to pinctrl: sh-pfc: r8a7790: Remove non existing GPIO pins Geert Uytterhoeven
2015-03-11 0:04 ` Simon Horman
2015-03-10 14:00 ` 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=20150310075538.GA20709@verge.net.au \
--to=horms@verge.net.au \
--cc=geert+renesas@glider.be \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-sh@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).