From: Sachin Kamat <sachin.kamat@linaro.org>
To: Linus Walleij <linus.walleij@linaro.org>,
Kukjin Kim <kgene.kim@samsung.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>
Subject: Failure due to missing (Exynos related) pinctrl patch
Date: Tue, 29 Jan 2013 10:40:34 +0530 [thread overview]
Message-ID: <CAK9yfHybC6ZgGwxa_i=LrMpU_q9M4aaMraTqK63B+fw11NBqRA@mail.gmail.com> (raw)
Hi Linus, Kukjin,
Patch titled "pinctrl: exynos: change PINCTRL_EXYNOS option"
(linux-next commit Id: 7452b64d) which is present in linux-next is
missing in the mainline kernel. This patch is required along with the
patch "gpio: samsung: fix pinctrl condition for exynos and exynos5440"
(mainline commit Id: e4a5da51) which has already made it into
mainline. Without the missing patch we get the following boot up
warnings and subsequent failures with dt boot on 4412 based board:
WARNING: at drivers/gpio/gpio-samsung.c:3102 samsung_gpiolib_init+0x29c/0x2e8()
Unknown SoC in gpio-samsung, no GPIOs added
Modules linked in:
[<c00142dc>] (unwind_backtrace+0x0/0xf8) from [<c00202bc>]
(warn_slowpath_common+0x4c/0x64)
[<c00202bc>] (warn_slowpath_common+0x4c/0x64) from [<c0020368>]
(warn_slowpath_fmt+0x30/0x40)
[<c0020368>] (warn_slowpath_fmt+0x30/0x40) from [<c028b924>]
(samsung_gpiolib_init+0x29c/0x2e8)
[<c028b924>] (samsung_gpiolib_init+0x29c/0x2e8) from [<c000862c>]
(do_one_initcall+0x34/0x174)
[<c000862c>] (do_one_initcall+0x34/0x174) from [<c0275960>]
(kernel_init_freeable+0xfc/0x1c8)
[<c0275960>] (kernel_init_freeable+0xfc/0x1c8) from [<c01c0a5c>]
(kernel_init+0x8/0xe4)
[<c01c0a5c>] (kernel_init+0x8/0xe4) from [<c000e158>] (ret_from_fork+0x14/0x3c)
--
With warm regards,
Sachin
next reply other threads:[~2013-01-29 5:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 5:10 Sachin Kamat [this message]
2013-01-29 6:20 ` Failure due to missing (Exynos related) pinctrl patch Kukjin Kim
2013-01-29 22:25 ` Linus Walleij
2013-01-30 3:54 ` Sachin Kamat
2013-01-30 4:08 ` Kukjin Kim
2013-01-30 4:10 ` Sachin Kamat
2013-01-30 9:48 ` Linus Walleij
2013-01-30 10:15 ` Sachin Kamat
2013-01-31 13:59 ` 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='CAK9yfHybC6ZgGwxa_i=LrMpU_q9M4aaMraTqK63B+fw11NBqRA@mail.gmail.com' \
--to=sachin.kamat@linaro.org \
--cc=kgene.kim@samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-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 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).