From: Ming Lei <tom.leiming@gmail.com> To: Russell King <linux@arm.linux.org.uk>, Kukjin Kim <kgene@kernel.org>, linux-arm-kernel <linux-arm-kernel@lists.infradead.org>, linux-samsung-soc@vger.kernel.org, Pankaj Dubey <pankaj.dubey@samsung.com> Subject: kernel panic when booting on exynos 5440 Date: Thu, 25 Dec 2014 16:48:31 +0800 [thread overview] Message-ID: <CACVXFVNCZdMyHQ1fzZDGs7h7X9vWmMVBJFRqWs7_P=WBQUYk1g@mail.gmail.com> (raw) Hi Pankaj, In your commit fce9e5bb2(ARM: EXYNOS: Add support for mapping PMU base address via DT), 'pmu_base_addr' is only parsed for very limited machines from the table of 'exynos_dt_pmu_match'. For other boards, 'pmu_base_addr' will keep its default value of null, then panic() is triggered. What do you think about the problem? Thanks, Ming Lei
WARNING: multiple messages have this Message-ID (diff)
From: tom.leiming@gmail.com (Ming Lei) To: linux-arm-kernel@lists.infradead.org Subject: kernel panic when booting on exynos 5440 Date: Thu, 25 Dec 2014 16:48:31 +0800 [thread overview] Message-ID: <CACVXFVNCZdMyHQ1fzZDGs7h7X9vWmMVBJFRqWs7_P=WBQUYk1g@mail.gmail.com> (raw) Hi Pankaj, In your commit fce9e5bb2(ARM: EXYNOS: Add support for mapping PMU base address via DT), 'pmu_base_addr' is only parsed for very limited machines from the table of 'exynos_dt_pmu_match'. For other boards, 'pmu_base_addr' will keep its default value of null, then panic() is triggered. What do you think about the problem? Thanks, Ming Lei
next reply other threads:[~2014-12-25 8:48 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-25 8:48 Ming Lei [this message] 2014-12-25 8:48 ` kernel panic when booting on exynos 5440 Ming Lei 2014-12-25 10:32 ` Pankaj Dubey 2014-12-25 10:32 ` Pankaj Dubey 2014-12-25 10:43 ` Ming Lei 2014-12-25 10:43 ` Ming Lei 2014-12-25 10:53 ` Pankaj Dubey 2014-12-25 10:53 ` Pankaj Dubey 2014-12-26 1:39 ` Ming Lei 2014-12-26 1:39 ` Ming Lei 2015-01-04 2:57 ` Ming Lei 2015-01-04 2:57 ` Ming Lei 2015-01-05 10:13 ` Kukjin Kim 2015-01-05 10:13 ` Kukjin Kim 2015-01-05 12:13 ` Ming Lei 2015-01-05 12:13 ` Ming Lei
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='CACVXFVNCZdMyHQ1fzZDGs7h7X9vWmMVBJFRqWs7_P=WBQUYk1g@mail.gmail.com' \ --to=tom.leiming@gmail.com \ --cc=kgene@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-samsung-soc@vger.kernel.org \ --cc=linux@arm.linux.org.uk \ --cc=pankaj.dubey@samsung.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: linkBe 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.