From: Michal Simek <monstr@monstr.eu>
To: Michal Simek <michal.simek@xilinx.com>,
linux-kernel@vger.kernel.org, git@xilinx.com
Cc: Stefan Asserhall <stefan.asserhall@xilinx.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>,
Valentin Schneider <valentin.schneider@arm.com>
Subject: Re: [PATCH] microblaze: Fix _reset() function
Date: Tue, 25 Feb 2020 12:26:31 +0100 [thread overview]
Message-ID: <efea364d-a3e5-c1ea-1719-15c64db4c03c@monstr.eu> (raw)
In-Reply-To: <ce58b2e6d0fbc8bf94d3cd986c068fbc4fda4d04.1581497006.git.michal.simek@xilinx.com>
[-- Attachment #1.1: Type: text/plain, Size: 1018 bytes --]
On 12. 02. 20 9:43, Michal Simek wrote:
> There is a need to disable VM before jump to zero reset vector.
>
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> Reviewed-by: Stefan Asserhall <stefan.asserhall@xilinx.com>
> ---
>
> arch/microblaze/kernel/entry.S | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/microblaze/kernel/entry.S b/arch/microblaze/kernel/entry.S
> index f6ded356394a..b179f8f6d287 100644
> --- a/arch/microblaze/kernel/entry.S
> +++ b/arch/microblaze/kernel/entry.S
> @@ -958,6 +958,7 @@ ENTRY(_switch_to)
> nop
>
> ENTRY(_reset)
> + VM_OFF
> brai 0; /* Jump to reset vector */
>
> /* These are compiled and loaded into high memory, then
>
Applied.
M
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal SoCs
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2020-02-25 11:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 8:43 [PATCH] microblaze: Fix _reset() function Michal Simek
2020-02-25 11:26 ` Michal Simek [this message]
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=efea364d-a3e5-c1ea-1719-15c64db4c03c@monstr.eu \
--to=monstr@monstr.eu \
--cc=bigeasy@linutronix.de \
--cc=git@xilinx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=stefan.asserhall@xilinx.com \
--cc=tglx@linutronix.de \
--cc=valentin.schneider@arm.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;
as well as URLs for NNTP newsgroup(s).