Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: Hiep Cao Minh <cm-hiep@jinso.co.jp>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Xuan Truong Nguyen" <nx-truong@jinso.co.jp>,
	"Laurent Pinchart" <laurent.pinchart+renesas@ideasonboard.com>,
	duclm <lm-duc@jinso.co.jp>,
	"Ryusuke Sakato" <ryusuke.sakato.bx@renesas.com>,
	"Kuninori Morimoto" <kuninori.morimoto.gx@renesas.com>,
	"Magnus Damm" <magnus.damm@gmail.com>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	稲吉 <h-inayoshi@jinso.co.jp>,
	"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
	Dung:人ソ <nv-dung@jinso.co.jp>,
	"Simon Horman" <horms+renesas@verge.net.au>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	"Wolfram Sang" <wsa@sang-engineering.com>
Subject: Re: GEN2:Lager: Only 1 core works when turning off the SW8-PIN4
Date: Fri, 30 Sep 2016 18:55:23 +0900	[thread overview]
Message-ID: <57EE368B.8030500@jinso.co.jp> (raw)
In-Reply-To: <CAMuHMdUw_k_SLUO1r5v12Cun40cfJCfA7Em4e-zupEDsxcEdhw@mail.gmail.com>

Hi Geert,

Thanks for your reply!

On 09/29/2016 10:40 PM, Geert Uytterhoeven wrote:
> Hi Hiep,
>
> On Thu, Sep 29, 2016 at 1:03 PM, Hiep Cao Minh <cm-hiep@jinso.co.jp> wrote:
>> I'd like to report the issue of the CPU operation.
>> We tested and found it on Lager board at linux-v4.8-rcx.
>>
>> The test procedure is the following:
>>
>> Confirmation command:
>>
>> # cat /proc/interrupts
>> CPU0
>> 19: 2509 GIC-0 27 Level arch_timer
>> 21: 0 GIC-0 36 Level e6050000.gpio
>> 22: 0 GIC-0 37 Level e6051000.gpio
>> 23: 0 GIC-0 38 Level e6052000.gpio
>> 24: 0 GIC-0 39 Level e6053000.gpio
>> 25: 0 GIC-0 40 Level e6054000.gpio
>> 26: 0 GIC-0 41 Level e6055000.gpio
>> 27: 23 GIC-0 101 Level e61f0000.thermal
>> …”
>>
>> This issue appears when we changed the SW8-PIN4 of Lager board.
>>
>> SW8-PIN4: ON
>>
>> + At linux-v4.7: OK (4 cores work together normally).
>> + At linux-v4.8-rc2: OK (4 cores work together normally).
>>
>> SW8-PIN4: OFF
>>
>> + At linux-v4.7: -> OK(4 cores work together normally).
>> + At linux-v4.8-rc2: -> NG(Only 1 core works).
> And the kernel prints "Unable to boot CPU%u when MD21 is set", right?
>
>> We tried to find out the issued patch and we realize that it happens from
>> the following patch:
>> " 043248c Merge tag 'armsoc-dt' of
>> git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc"
> The issue you're seeing is due to a combination of commits 5f3bca0db8ac01a7
> ("ARM: shmobile: apmu: Add APMU DT support via Enable method") and
> dc378795156d980c ("ARM: dts: r8a7790: Add APMU nodes").
>
> When debug mode is enabled (SW8-4 = OFF), trying to boot secondary CPUs may
> lock up the system after a cold boot, depending of boot load version.  Hence
> we explicitly prohibit that. BTW, this has been the case on Koelsch since commit
> 277efd30cfc72ec2 ("ARM: shmobile: Check r8a7791 MD21 at SMP boot").
>
> Now, does series "[PATCH/RFT 0/4] ARM: shmobile: R-Car Gen2: Allow booting
> secondary CPU cores in debug mode" (included in all renesas-drivers releases
> during September) fix it for you?
Thanks for your series patches.
I have had some problems of receiving post mail from Linux-Renesas 
Mailing List recently.

Could you please forward these series patches to me?

Thank you!.
Jinso/Linux-Team
Hiep.

  reply	other threads:[~2016-09-30  9:55 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <57A46D20.7040106@jinso.co.jp>
     [not found] ` <57C9764F.2070802@jinso.co.jp>
     [not found]   ` <f2bb791e-8973-10a9-a2ac-1a944b38d4ad@jinso.co.jp>
2016-09-12  8:57     ` GEN2: Initialization of VSP1 failed at upstream v4.8-rc2 Hiep Cao Minh
2016-09-12  9:06       ` Geert Uytterhoeven
2016-09-12  9:25         ` Hiep Cao Minh
2016-09-12 10:31         ` Laurent Pinchart
     [not found]         ` <57ECF4EA.4010704@jinso.co.jp>
2016-09-29 13:40           ` GEN2:Lager: Only 1 core works when turning off the SW8-PIN4 Geert Uytterhoeven
2016-09-30  9:55             ` Hiep Cao Minh [this message]
2016-09-30  9:58               ` Geert Uytterhoeven
2016-09-30 10:05                 ` Hiep Cao Minh
2016-11-07  9:44                   ` Geert Uytterhoeven
2016-11-07 10:37                     ` Hiep Cao Minh
2016-11-07 12:19                       ` Geert Uytterhoeven
2016-09-12  9:33       ` GEN2: Initialization of VIN failed at upstream v4.8-rc2 Hiep Cao Minh
2016-09-12 11:09         ` Niklas Söderlund
2016-09-13  5:12           ` Hiep Cao Minh
     [not found]     ` <9d9a647b-d75f-e89a-2d4d-55e409ccabae@jinso.co.jp>
2016-10-18 13:17       ` The failure summary report of GEN2 for linux stable v4.8 Wolfram Sang
     [not found]         ` <b7e9b4c2-1d5d-2e76-c0f4-fcc50150dc30@jinso.co.jp>
2016-10-24  7:00           ` Geert Uytterhoeven
     [not found]             ` <125b4831-cbdf-f8e1-da97-8ea9cf458c22@jinso.co.jp>
2016-10-24  9:21               ` Geert Uytterhoeven
2016-10-25  2:07                 ` Xuan Truong Nguyen
2016-10-28  8:14                 ` Yoshihiro Shimoda
2016-10-28 10:29                   ` Xuan Truong Nguyen
2016-11-07  0:30                   ` Xuan Truong Nguyen
2016-10-18 14:13       ` Laurent Pinchart
2016-10-18 15:55         ` Laurent Pinchart
2016-10-19  2:39         ` Xuan Truong Nguyen
     [not found]         ` <a101cec4-c9ee-48fa-4f16-5e4cb2b8fab7@jinso.co.jp>
2016-10-21 11:20           ` Laurent Pinchart
2016-10-24  5:51             ` Xuan Truong Nguyen
2016-11-11  1:31             ` Laurent Pinchart
2016-11-11  2:44               ` Xuan Truong Nguyen
     [not found]       ` <58060015.3020702@jinso.co.jp>
2016-10-19  0:40         ` The failure summary report of GEN3(RCAR H3) " Kuninori Morimoto
2016-10-19  2:45           ` Xuan Truong Nguyen
     [not found]         ` <b4efb8cc-bf55-cf34-a537-4ffa5041291a@jinso.co.jp>
2016-10-31 13:16           ` The failure summary report of GEN3(RCAR H3) for linux upstream v4.9-rc2 Geert Uytterhoeven
2016-11-02  1:29             ` duclm
2016-11-02  7:46               ` Geert Uytterhoeven

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=57EE368B.8030500@jinso.co.jp \
    --to=cm-hiep@jinso.co.jp \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=h-inayoshi@jinso.co.jp \
    --cc=horms+renesas@verge.net.au \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=lm-duc@jinso.co.jp \
    --cc=magnus.damm@gmail.com \
    --cc=nv-dung@jinso.co.jp \
    --cc=nx-truong@jinso.co.jp \
    --cc=ryusuke.sakato.bx@renesas.com \
    --cc=wsa@sang-engineering.com \
    --cc=yoshihiro.shimoda.uh@renesas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox