From: Joe Perches <joe@perches.com>
To: Alexander A Sverdlin <alexander.sverdlin@nokia.com>,
linux-mips@vger.kernel.org
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Corey Minyard <cminyard@mvista.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Revert "MIPS: octeon: Remove vestiges of CONFIG_CAVIUM_RESERVE32"
Date: Sat, 30 Jul 2022 10:18:10 -0700 [thread overview]
Message-ID: <d5f8d6b58a32cdbf6326ccef7d46a58ba753edc7.camel@perches.com> (raw)
In-Reply-To: <20220725091740.28188-3-alexander.sverdlin@nokia.com>
On Mon, 2022-07-25 at 11:17 +0200, Alexander A Sverdlin wrote:
> From: Alexander Sverdlin <alexander.sverdlin@nokia.com>
>
> This reverts commit e98b461bb057aaea6fa766260788c08825213837.
>
> We actually have been using the CONFIG_CAVIUM_RESERVE32 and previous patch
> defined it in the corresponding Kconfig.
Perhaps all of the uses of
#if defined(CONFIG_CAVIUM_RESERVE32)
should be
#if defined(CONFIG_CAVIUM_RESERVE32) && CONFIG_CAVIUM_RESERVE32
> diff --git a/arch/mips/cavium-octeon/executive/cvmx-cmd-queue.c b/arch/mips/cavium-octeon/executive/cvmx-cmd-queue.c
[]
> @@ -57,14 +57,27 @@ EXPORT_SYMBOL_GPL(__cvmx_cmd_queue_state_ptr);
> static cvmx_cmd_queue_result_t __cvmx_cmd_queue_init_state_ptr(void)
> {
> char *alloc_name = "cvmx_cmd_queues";
> +#if defined(CONFIG_CAVIUM_RESERVE32) && CONFIG_CAVIUM_RESERVE32
> + extern uint64_t octeon_reserve32_memory;
> +#endif
Like these
> +#if defined(CONFIG_CAVIUM_RESERVE32) && CONFIG_CAVIUM_RESERVE32
> + if (octeon_reserve32_memory)
> + __cvmx_cmd_queue_state_ptr =
> + cvmx_bootmem_alloc_named_range(sizeof(*__cvmx_cmd_queue_state_ptr),
> + octeon_reserve32_memory,
> + octeon_reserve32_memory +
> + (CONFIG_CAVIUM_RESERVE32 <<
> + 20) - 1, 128, alloc_name);
> + else
> +#endif
> + __cvmx_cmd_queue_state_ptr =
> + cvmx_bootmem_alloc_named(sizeof(*__cvmx_cmd_queue_state_ptr),
> + 128,
> + alloc_name);
[]
> diff --git a/arch/mips/cavium-octeon/setup.c b/arch/mips/cavium-octeon/setup.c
[]
> @@ -284,6 +284,11 @@ void octeon_crash_smp_send_stop(void)
[]
> +#ifdef CONFIG_CAVIUM_RESERVE32
here.
> +uint64_t octeon_reserve32_memory;
> +EXPORT_SYMBOL(octeon_reserve32_memory);
> +#endif
[]
> @@ -661,7 +666,9 @@ void __init prom_init(void)
> int i;
> u64 t;
> int argc;
> -
> +#ifdef CONFIG_CAVIUM_RESERVE32
> + int64_t addr = -1;
here
> +#endif
> /*
> * The bootloader passes a pointer to the boot descriptor in
> * $a3, this is available as fw_arg3.
> @@ -776,6 +783,25 @@ void __init prom_init(void)
> cvmx_write_csr(CVMX_LED_UDD_DATX(1), 0);
> cvmx_write_csr(CVMX_LED_EN, 1);
> }
> +#ifdef CONFIG_CAVIUM_RESERVE32
etc...
next prev parent reply other threads:[~2022-07-30 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 9:17 [PATCH 0/2] MIPS: Restore CONFIG_CAVIUM_RESERVE32 Alexander A Sverdlin
2022-07-25 9:17 ` [PATCH 1/2] MIPS: Introduce CAVIUM_RESERVE32 Kconfig option Alexander A Sverdlin
2022-08-30 3:02 ` Yu Zhao
2022-09-05 18:50 ` Yu Zhao
2022-09-06 7:55 ` Alexander Sverdlin
2022-07-25 9:17 ` [PATCH 2/2] Revert "MIPS: octeon: Remove vestiges of CONFIG_CAVIUM_RESERVE32" Alexander A Sverdlin
2022-07-30 17:18 ` Joe Perches [this message]
2022-07-30 9:02 ` [PATCH 0/2] MIPS: Restore CONFIG_CAVIUM_RESERVE32 Thomas Bogendoerfer
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=d5f8d6b58a32cdbf6326ccef7d46a58ba753edc7.camel@perches.com \
--to=joe@perches.com \
--cc=alexander.sverdlin@nokia.com \
--cc=cminyard@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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
all inboxes | Powered by JetHome®