From: Vignesh Raghavendra <vigneshr@ti.com>
To: Roger Quadros <rogerq@kernel.org>, <krzk@kernel.org>
Cc: <miquel.raynal@bootlin.com>, <tony@atomide.com>, <kishon@ti.com>,
<nm@ti.com>, <linux-omap@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] memory: omap-gpmc: Make OMAP_GPMC config visible and selectable
Date: Sat, 26 Mar 2022 19:39:23 +0530 [thread overview]
Message-ID: <e28524f0-7251-afc3-4237-58994659f0d3@ti.com> (raw)
In-Reply-To: <20220326084331.28310-1-rogerq@kernel.org>
Hi Roger,
On 26/03/22 2:13 pm, Roger Quadros wrote:
> So far for armv7 TI platforms, GPMC was being selected by
> arch/arm/mach-* architecture Kconfig files.
>
> For K3 platforms, GPMC is no longer required for basic boot
> and cannot be always enabled by default by mach- Kconfig.
>
> We need a way for user (or board defconfig) to enable
> it if required so ake OMAP_GPMC Kconfig option always visible.
>
> Signed-off-by: Roger Quadros <rogerq@kernel.org>
> ---
> drivers/memory/Kconfig | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/memory/Kconfig b/drivers/memory/Kconfig
> index 30bff6cb1b8d..da2af9c38fe3 100644
> --- a/drivers/memory/Kconfig
> +++ b/drivers/memory/Kconfig
> @@ -103,8 +103,8 @@ config TI_EMIF
> temperature changes
>
> config OMAP_GPMC
> - bool "Texas Instruments OMAP SoC GPMC driver" if COMPILE_TEST
> - depends on OF_ADDRESS
> + bool "Texas Instruments OMAP SoC GPMC driver"
> + depends on OF_ADDRESS || COMPILE_TEST
Can we make this tristate now, so that driver can be built as module?
> select GPIOLIB
> help
> This driver is for the General Purpose Memory Controller (GPMC)
next prev parent reply other threads:[~2022-03-26 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 8:43 Roger Quadros
2022-03-26 14:09 ` Vignesh Raghavendra [this message]
2022-03-26 14:36 ` Roger Quadros
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=e28524f0-7251-afc3-4237-58994659f0d3@ti.com \
--to=vigneshr@ti.com \
--cc=kishon@ti.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=nm@ti.com \
--cc=rogerq@kernel.org \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®