From: wangwenhu <wenhu.pku@gmail.com>
To: Scott Wood <oss@buserror.net>,
Kumar Gala <galak@kernel.crashing.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: wenhu.wang@vivo.com, trivial@kernel.org
Subject: [PATCH] powerpc/Kconfig: Make FSL_85XX_CACHE_SRAM configurable
Date: Mon, 20 Jan 2020 06:43:27 -0800 [thread overview]
Message-ID: <20200120144327.20800-1-wenhu.pku@gmail.com> (raw)
From: wangwenhu <wenhu.wang@vivo.com>
When generating .config file with menuconfig on Freescale BOOKE
SOC, FSL_85XX_CACHE_SRAM is not configurable for the lack of
description in the Kconfig field, which makes it impossible
to support L2Cache-Sram driver. Add a description to make it
configurable.
Signed-off-by: wangwenhu <wenhu.wang@vivo.com>
---
arch/powerpc/platforms/85xx/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/platforms/85xx/Kconfig b/arch/powerpc/platforms/85xx/Kconfig
index fa3d29dcb57e..ee5ba10b98cb 100644
--- a/arch/powerpc/platforms/85xx/Kconfig
+++ b/arch/powerpc/platforms/85xx/Kconfig
@@ -17,7 +17,7 @@ if FSL_SOC_BOOKE
if PPC32
config FSL_85XX_CACHE_SRAM
- bool
+ bool "Freescale Cache-Sram"
select PPC_LIB_RHEAP
help
When selected, this option enables cache-sram support
--
2.23.0
next reply other threads:[~2020-01-20 20:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 14:43 wangwenhu [this message]
2020-01-21 3:25 ` [PATCH] powerpc/Kconfig: Make FSL_85XX_CACHE_SRAM configurable Scott Wood
2020-01-21 5:20 ` 王文虎
2020-01-21 5:49 ` [PATCH] " Scott Wood
2020-01-21 6:38 ` 王文虎
2020-02-29 23:12 ` Scott Wood
2020-03-02 4:42 ` 王文虎
2020-03-02 8:58 ` Scott Wood
2020-03-02 9:51 ` 王文虎
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=20200120144327.20800-1-wenhu.pku@gmail.com \
--to=wenhu.pku@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=oss@buserror.net \
--cc=paulus@samba.org \
--cc=trivial@kernel.org \
--cc=wenhu.wang@vivo.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).