From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Pankaj Dubey <pankaj.dubey@samsung.com>,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: kgene.kim@samsung.com, thomas.ab@samsung.com, olof@lixom.net,
p.fedin@samsung.com, Kukjin Kim <kgene@kernel.org>
Subject: Re: [RESPIN 2/6] drivers: memory: Add support for exynos SROM driver
Date: Fri, 26 Feb 2016 16:36:05 +0900 [thread overview]
Message-ID: <56D00065.6030507@samsung.com> (raw)
In-Reply-To: <56CFFDF0.9040107@samsung.com>
On 26.02.2016 16:25, Krzysztof Kozlowski wrote:
> On 25.02.2016 17:33, Pankaj Dubey wrote:
>> This patch adds Exynos SROM controller driver which will handle
>> save restore of SROM registers during S2R.
>>
>> Signed-off-by: Pankaj Dubey <pankaj.dubey@samsung.com>
>> Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
>> [p.fedin@samsung.com: tested on SMDK5410]
>> Tested-by: Pavel Fedin <p.fedin@samsung.com>
>> Signed-off-by: Kukjin Kim <kgene@kernel.org>
>> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
>> ---
>> drivers/memory/Kconfig | 1 +
>> drivers/memory/Makefile | 1 +
>> drivers/memory/samsung/Kconfig | 12 +++
>> drivers/memory/samsung/Makefile | 1 +
>> drivers/memory/samsung/exynos-srom.c | 175 +++++++++++++++++++++++++++++++++++
>> drivers/memory/samsung/exynos-srom.h | 51 ++++++++++
>> 6 files changed, 241 insertions(+)
>> create mode 100644 drivers/memory/samsung/Kconfig
>> create mode 100644 drivers/memory/samsung/Makefile
>> create mode 100644 drivers/memory/samsung/exynos-srom.c
>> create mode 100644 drivers/memory/samsung/exynos-srom.h
>>
>> diff --git a/drivers/memory/Kconfig b/drivers/memory/Kconfig
>> index 6f31546..bcb1982 100644
>> --- a/drivers/memory/Kconfig
>> +++ b/drivers/memory/Kconfig
>> @@ -114,6 +114,7 @@ config JZ4780_NEMC
>> the Ingenic JZ4780. This controller is used to handle external
>> memory devices such as NAND and SRAM.
>>
>> +source "drivers/memory/samsung/Kconfig"
>> source "drivers/memory/tegra/Kconfig"
>>
>> endif
>> diff --git a/drivers/memory/Makefile b/drivers/memory/Makefile
>> index 1c46af5..d100e40 100644
>> --- a/drivers/memory/Makefile
>> +++ b/drivers/memory/Makefile
>> @@ -16,4 +16,5 @@ obj-$(CONFIG_MVEBU_DEVBUS) += mvebu-devbus.o
>> obj-$(CONFIG_TEGRA20_MC) += tegra20-mc.o
>> obj-$(CONFIG_JZ4780_NEMC) += jz4780-nemc.o
>>
>> +obj-$(CONFIG_SAMSUNG_MC) += samsung/
>> obj-$(CONFIG_TEGRA_MC) += tegra/
>> diff --git a/drivers/memory/samsung/Kconfig b/drivers/memory/samsung/Kconfig
>> new file mode 100644
>> index 0000000..c2cd45e
>> --- /dev/null
>> +++ b/drivers/memory/samsung/Kconfig
>> @@ -0,0 +1,12 @@
>> +config SAMSUNG_MC
>> + bool "SAMSUNG Exynos Memory Controller support" if COMPILE_TEST
>> + default y
>> + depends on ARCH_EXYNOS
These two are not needed and they introduce issues (when COMPILE_TEST it
should not depend on exynos and should not be in such case enabled by
default).
>> + help
>> + This driver supports the Memory Controller (MC) hardwares found on
>> + SAMSUNG Exynos SoCs.
>> +
>
> if SAMSUNG_MC
>
>> +config EXYNOS_SROM
>> + bool
bool should be described with COMPILE_TEST
>> + depends on (ARM && ARCH_EXYNOS && PM) || ((ARM || ARM64) && COMPILE_TEST)
>
> (ARM && ARCH_EXYNOS && PM) || COMPILE_TEST
>
> You don't need to limit compile testing to ARM/ARM64.
>
So overall it should be like:
config SAMSUNG_MC
bool "Samsung Exynos Memory Controller support" if COMPILE_TEST
help
Support for the Memory Controller (MC) devices found on
Samsung Exynos SoCs.
if SAMSUNG_MC
config EXYNOS_SROM
bool "Exynos SROM controller driver" if COMPILE_TEST
depends on (ARM && ARCH_EXYNOS && PM) || COMPILE_TEST
endif
next prev parent reply other threads:[~2016-02-26 7:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 8:33 [RESPIN 0/6] Add support for Exynos SROM Controller driver Pankaj Dubey
2016-02-25 8:33 ` [RESPIN 1/6] dt-bindings: EXYNOS: Add exynos-srom device tree binding Pankaj Dubey
2016-03-02 17:53 ` Rob Herring
2016-03-05 4:42 ` pankaj.dubey
2016-03-08 7:05 ` Pavel Fedin
2016-04-04 3:35 ` Krzysztof Kozlowski
2016-03-05 6:18 ` pankaj.dubey
2016-03-11 2:39 ` pankaj.dubey
2016-02-25 8:33 ` [RESPIN 2/6] drivers: memory: Add support for exynos SROM driver Pankaj Dubey
2016-02-26 7:25 ` Krzysztof Kozlowski
2016-02-26 7:36 ` Krzysztof Kozlowski [this message]
2016-02-25 8:33 ` [RESPIN 3/6] MAINTAINERS: Add maintainers entry for drivers/memory/samsung Pankaj Dubey
2016-02-25 8:33 ` [RESPIN 4/6] ARM: EXYNOS: Remove SROM related register settings from mach-exynos Pankaj Dubey
2016-02-26 7:28 ` Krzysztof Kozlowski
2016-02-25 8:33 ` [RESPIN 5/6] dt-bindings: EXYNOS: Describe SROMc configuration Pankaj Dubey
2016-03-02 17:57 ` Rob Herring
2016-03-05 4:47 ` pankaj.dubey
2016-02-25 8:33 ` [RESPIN 6/6] drivers: memory: exynos-srom: Add support for bank configuration Pankaj Dubey
2016-02-26 7:51 ` [RESPIN 0/6] Add support for Exynos SROM Controller driver Krzysztof Kozlowski
2016-02-26 8:33 ` Pavel Fedin
2016-02-26 10:55 ` Krzysztof Kozlowski
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=56D00065.6030507@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=p.fedin@samsung.com \
--cc=pankaj.dubey@samsung.com \
--cc=thomas.ab@samsung.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).