From: Brian Norris <computersforpeace@gmail.com>
To: Punnaiah Choudary Kalluri <punnaiah.choudary.kalluri@xilinx.com>
Cc: mark.rutland@arm.com, jussi.kivilinna@iki.fi,
linux-doc@vger.kernel.org, artem.bityutskiy@linux.intel.com,
linux-mtd@lists.infradead.org,
Punnaiah Choudary Kalluri <punnaia@xilinx.com>,
arnd@arndb.de, michal.simek@xilinx.com,
ezequiel.garcia@free-electrons.com, grant.likely@linaro.org,
devicetree@vger.kernel.org, jason@lakedaemon.net,
pawel.moll@arm.com, ijc+devicetree@hellion.org.uk,
joern@logfs.org, kpc528@gmail.com, robh+dt@kernel.org,
acourbot@nvidia.com, pekon@ti.com,
kalluripunnaiahchoudary@gmail.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, rob@landley.net,
galak@codeaurora.org, ivan.khoronzhuk@ti.com,
dwmw2@infradead.org
Subject: Re: [PATCH v5 2/2] memory: pl353: Add driver for arm pl353 static memory controller
Date: Thu, 2 Apr 2015 13:58:52 -0700 [thread overview]
Message-ID: <20150402205852.GI32500@ld-irv-0074> (raw)
In-Reply-To: <bc55f81bea314bc49b62b6fbcb662ae3@BN1BFFO11FD014.protection.gbl>
I'm not following the review of the 'memory' portions much, but has this
gotten much review? I was looking at the MTD portions when I noticed an
obvious issue below:
On Tue, Jan 06, 2015 at 11:19:17PM +0530, Punnaiah Choudary Kalluri wrote:
> Add driver for arm pl353 static memory controller. This controller is
> used in xilinx zynq soc for interfacing the nand and nor/sram memory
> devices.
>
> Signed-off-by: Punnaiah Choudary Kalluri <punnaia@xilinx.com>
> ---
> Changes in v5:
> - Added pl353_smc_get_clkrate function, made pl353_smc_set_cycles as public
> API
> - Removed nand timing parameter initialization and moved it to nand driver
> Changes in v4:
> - Modified driver to support multiple instances
> - Used sleep instaed of busywait for delay
> Changes in v3:
> - None
> Changes in v2:
> - Since now the timing parameters are in nano seconds, added logic to convert
> them to the cycles
> ---
> drivers/memory/Kconfig | 6 +
> drivers/memory/Makefile | 1 +
> drivers/memory/pl353-smc.c | 525 ++++++++++++++++++++++++++++++++++++++
> include/linux/memory/pl353-smc.h | 37 +++
> 4 files changed, 569 insertions(+), 0 deletions(-)
> create mode 100644 drivers/memory/pl353-smc.c
> create mode 100644 include/linux/memory/pl353-smc.h
>
> diff --git a/drivers/memory/Kconfig b/drivers/memory/Kconfig
> index 6d91c27..9d4880f 100644
> --- a/drivers/memory/Kconfig
> +++ b/drivers/memory/Kconfig
> @@ -85,4 +85,10 @@ config FSL_IFC
> bool
> depends on FSL_SOC
>
> +config PL353_SMC
> + bool "ARM PL353 Static Memory Controller(SMC) driver"
Space after 'Controller'. i.e.:
bool "ARM PL353 Static Memory Controller (SMC) driver"
> + default y
We almost definitely don't want this to be 'default y', especially given
that it would then be enabled on all ARM systems. Users could add it
their configuration themselves if they want it, or you might add it to
multi_v7_defconfig.
> + depends on ARM
> + help
> + This driver is for the ARM PL353 Static Memory Controller(SMC) module.
Same spacing issue here.
> endif
[...]
Brian
next prev parent reply other threads:[~2015-04-02 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1420566557-19846-1-git-send-email-punnaia@xilinx.com>
2015-01-06 17:49 ` [PATCH v5 1/2] Devicetree: Add pl353 smc controller devicetree binding information Punnaiah Choudary Kalluri
2015-01-06 17:49 ` [PATCH v5 2/2] memory: pl353: Add driver for arm pl353 static memory controller Punnaiah Choudary Kalluri
2015-04-02 20:58 ` Brian Norris [this message]
2015-04-03 2:10 ` punnaiah choudary kalluri
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=20150402205852.GI32500@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=acourbot@nvidia.com \
--cc=arnd@arndb.de \
--cc=artem.bityutskiy@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=ivan.khoronzhuk@ti.com \
--cc=jason@lakedaemon.net \
--cc=joern@logfs.org \
--cc=jussi.kivilinna@iki.fi \
--cc=kalluripunnaiahchoudary@gmail.com \
--cc=kpc528@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=pawel.moll@arm.com \
--cc=pekon@ti.com \
--cc=punnaia@xilinx.com \
--cc=punnaiah.choudary.kalluri@xilinx.com \
--cc=rob@landley.net \
--cc=robh+dt@kernel.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