From: Sascha Hauer <s.hauer@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH next 0/3] RISC-V: resurrect nmon
Date: Fri, 9 Jul 2021 22:58:38 +0200 [thread overview]
Message-ID: <20210709205838.GE9782@pengutronix.de> (raw)
In-Reply-To: <20210708083035.40814-1-antonynpavlov@gmail.com>
On Thu, Jul 08, 2021 at 11:30:32AM +0300, Antony Pavlov wrote:
> After migrating to PBL we can't use nmon assembler macro
> in C code anymore. This series adds necessary wrapper
> for invoking nmon from PBL C code.
>
> Antony Pavlov (3):
> RISC-V: make it possible to run nmon from PBL C code
> RISC-V: boards: erizo: make it possible to use nmon
> RISC-V: boards: beaglev: make it possible to use nmon
Applied, thanks
Sascha
>
> arch/riscv/Kconfig.socs | 1 +
> arch/riscv/boards/beaglev/lowlevel.c | 2 ++
> arch/riscv/boards/erizo/lowlevel.c | 2 ++
> arch/riscv/boot/Makefile | 1 +
> arch/riscv/boot/nmon_entry.S | 13 ++++++++
> arch/riscv/include/asm/riscv_nmon.h | 49 ++++++++++++++++++----------
> 6 files changed, 51 insertions(+), 17 deletions(-)
> create mode 100644 arch/riscv/boot/nmon_entry.S
>
> --
> 2.32.0
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2021-07-09 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 8:30 Antony Pavlov
2021-07-08 8:30 ` [PATCH next 1/3] RISC-V: make it possible to run nmon from PBL C code Antony Pavlov
2021-07-08 8:30 ` [PATCH next 2/3] RISC-V: boards: erizo: make it possible to use nmon Antony Pavlov
2021-07-08 8:30 ` [PATCH next 3/3] RISC-V: boards: beaglev: " Antony Pavlov
2021-07-09 20:58 ` Sascha Hauer [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=20210709205838.GE9782@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.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