All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pankaj Dubey <pankaj.dubey@samsung.com>
To: Ming Lei <tom.leiming@gmail.com>,
	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
Cc: Thomas Abraham <thomas.ab@samsung.com>
Subject: Re: kernel panic when booting on exynos 5440
Date: Thu, 25 Dec 2014 16:02:44 +0530	[thread overview]
Message-ID: <549BE7CC.1000005@samsung.com> (raw)
In-Reply-To: <CACVXFVNCZdMyHQ1fzZDGs7h7X9vWmMVBJFRqWs7_P=WBQUYk1g@mail.gmail.com>

+CC: Thomas Abraham

Hi Ming,

On Thursday 25 December 2014 02:18 PM, Ming Lei wrote:
> 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.
>

Yes, it will.
As exynos5440 DT does not have PMU device node, neither above mentioned 
patch added corresponding matching device_id.
If I remember correctly, I might have missed this because exynos5440 DT 
was not having PMU node.

> What do you think about the problem?

I missed this part, and I should have taken care of this in original 
patch itself. Well as of now I can think of only one solution that if we 
really want to keep support for exynos5440 in mainline kernel, to avoid 
above issue we should skip pmu mapping for exynos5440. In this case 
following patch will do this work.

Also I will like to know from Kukjin that what best can be done now.
If he is OK with below solution I can post the same.

---------------------------------------------------------------

Subject: [PATCH] ARM: EXYNOS: do not try to map PMU for exynos5440

Commit id: 2e94ac42898f84d76e3c21dd91bc is not taking care
of mapping of exynos5440 PMU register which will result in kernel panic.
As of now let's avoid mapping of exynos5440 PMU.

Signed-off-by: Pankaj Dubey <pankaj.dubey@samsung.com>
---
  arch/arm/mach-exynos/exynos.c | 3 ++-
  1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/arch/arm/mach-exynos/exynos.c b/arch/arm/mach-exynos/exynos.c
index c13d083..1891b8c 100644
--- a/arch/arm/mach-exynos/exynos.c
+++ b/arch/arm/mach-exynos/exynos.c
@@ -208,7 +208,8 @@ static void __init exynos_init_irq(void)
          * DT is not unflatten so we can't use DT APIs before
          * init_irq
          */
-       exynos_map_pmu();
+       if (!of_machine_is_compatible("samsung,exynos5440"))
+               exynos_map_pmu();
  }

  static void __init exynos_dt_machine_init(void)

------------------------------------------------------
>
> Thanks,
> Ming Lei
>

Thanks,
Pankaj Dubey

WARNING: multiple messages have this Message-ID (diff)
From: pankaj.dubey@samsung.com (Pankaj Dubey)
To: linux-arm-kernel@lists.infradead.org
Subject: kernel panic when booting on exynos 5440
Date: Thu, 25 Dec 2014 16:02:44 +0530	[thread overview]
Message-ID: <549BE7CC.1000005@samsung.com> (raw)
In-Reply-To: <CACVXFVNCZdMyHQ1fzZDGs7h7X9vWmMVBJFRqWs7_P=WBQUYk1g@mail.gmail.com>

+CC: Thomas Abraham

Hi Ming,

On Thursday 25 December 2014 02:18 PM, Ming Lei wrote:
> 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.
>

Yes, it will.
As exynos5440 DT does not have PMU device node, neither above mentioned 
patch added corresponding matching device_id.
If I remember correctly, I might have missed this because exynos5440 DT 
was not having PMU node.

> What do you think about the problem?

I missed this part, and I should have taken care of this in original 
patch itself. Well as of now I can think of only one solution that if we 
really want to keep support for exynos5440 in mainline kernel, to avoid 
above issue we should skip pmu mapping for exynos5440. In this case 
following patch will do this work.

Also I will like to know from Kukjin that what best can be done now.
If he is OK with below solution I can post the same.

---------------------------------------------------------------

Subject: [PATCH] ARM: EXYNOS: do not try to map PMU for exynos5440

Commit id: 2e94ac42898f84d76e3c21dd91bc is not taking care
of mapping of exynos5440 PMU register which will result in kernel panic.
As of now let's avoid mapping of exynos5440 PMU.

Signed-off-by: Pankaj Dubey <pankaj.dubey@samsung.com>
---
  arch/arm/mach-exynos/exynos.c | 3 ++-
  1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/arch/arm/mach-exynos/exynos.c b/arch/arm/mach-exynos/exynos.c
index c13d083..1891b8c 100644
--- a/arch/arm/mach-exynos/exynos.c
+++ b/arch/arm/mach-exynos/exynos.c
@@ -208,7 +208,8 @@ static void __init exynos_init_irq(void)
          * DT is not unflatten so we can't use DT APIs before
          * init_irq
          */
-       exynos_map_pmu();
+       if (!of_machine_is_compatible("samsung,exynos5440"))
+               exynos_map_pmu();
  }

  static void __init exynos_dt_machine_init(void)

------------------------------------------------------
>
> Thanks,
> Ming Lei
>

Thanks,
Pankaj Dubey

  reply	other threads:[~2014-12-25 10:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-25  8:48 kernel panic when booting on exynos 5440 Ming Lei
2014-12-25  8:48 ` Ming Lei
2014-12-25 10:32 ` Pankaj Dubey [this message]
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=549BE7CC.1000005@samsung.com \
    --to=pankaj.dubey@samsung.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=thomas.ab@samsung.com \
    --cc=tom.leiming@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 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.