From: Cyrille Pitchen <cyrille.pitchen@atmel.com>
To: Marek Vasut <marex@denx.de>
Cc: <nicolas.ferre@atmel.com>, <broonie@kernel.org>,
<linux-spi@vger.kernel.org>, <dwmw2@infradead.org>,
<computersforpeace@gmail.com>, <zajec5@gmail.com>,
<beanhuo@micron.com>, <juhosg@openwrt.org>,
<shijie.huang@intel.com>, <ben@decadent.org.uk>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <robh+dt@kernel.org>,
<pawel.moll@arm.com>, <mark.rutland@arm.com>,
<ijc+devicetree@hellion.org.uk>, <galak@codeaurora.org>,
<linux-mtd@lists.infradead.org>
Subject: Re: [PATCH linux-next v4 5/5] mtd: atmel-quadspi: add driver for Atmel QSPI controller
Date: Mon, 24 Aug 2015 19:04:38 +0200 [thread overview]
Message-ID: <55DB4EA6.9090807@atmel.com> (raw)
In-Reply-To: <201508241303.52066.marex@denx.de>
Hi Marek,
Le 24/08/2015 13:03, Marek Vasut a écrit :
> On Monday, August 24, 2015 at 12:14:00 PM, Cyrille Pitchen wrote:
>> This driver add support to the new Atmel QSPI controller embedded into
>> sama5d2x SoCs. It expects a NOR memory to be connected to the QSPI
>> controller.
>>
>> Signed-off-by: Cyrille Pitchen <cyrille.pitchen@atmel.com>
>> Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
>
> Hi,
>
> [...]
>
>> +/* Register access macros */
>
> These are functions, not macros :)
>
> btw is there any reason for these ? I'd say, just put the read*() and
> write*() functions directly into the code and be done with it, it is
> much less confusing.
>
> Also, why do you use the _relaxed() versions of the functions ?
>
>> +static inline u32 qspi_readl(struct atmel_qspi *aq, u32 reg)
>> +{
>> + return readl_relaxed(aq->regs + reg);
>> +}
>> +
>> +static inline void qspi_writel(struct atmel_qspi *aq, u32 reg, u32 value)
>> +{
>> + writel_relaxed(value, aq->regs + reg);
>> +}
>> +
>> +static inline u16 qspi_readw(struct atmel_qspi *aq, u32 reg)
>> +{
>> + return readw_relaxed(aq->regs + reg);
>> +}
>> +
>> +static inline void qspi_writew(struct atmel_qspi *aq, u32 reg, u16 value)
>> +{
>> + writew_relaxed(value, aq->regs + reg);
>> +}
>> +
>> +static inline u8 qspi_readb(struct atmel_qspi *aq, u32 reg)
>> +{
>> + return readb_relaxed(aq->regs + reg);
>> +}
>> +
>> +static inline void qspi_writeb(struct atmel_qspi *aq, u32 reg, u8 value)
>> +{
>> + writeb_relaxed(value, aq->regs + reg);
>> +}
>
> [...]
>
>> +static int atmel_qspi_run_command(struct atmel_qspi *aq,
>> + const struct atmel_qspi_command *cmd)
>> +{
>> + u32 iar, icr, ifr, sr;
>> + int err = 0;
>> +
>> + iar = 0;
>> + icr = 0;
>> + ifr = aq->ifr_width | cmd->ifr_tfrtyp;
>> +
>> + /* Compute instruction parameters */
>> + if (cmd->enable.bits.instruction) {
>> + icr |= QSPI_ICR_INST(cmd->instruction);
>> + ifr |= QSPI_IFR_INSTEN;
>> + }
>> +
>> + /* Compute address parameters */
>> + switch (cmd->enable.bits.address) {
>> + case 4:
>> + ifr |= QSPI_IFR_ADDRL;
>> + /*break;*/ /* fallback to the 24bit address case */
>
> What's this commented out bit of code for ? :-)
I just wanted to stress out there was no missing "break;".
I've reworded the comment to:
/* No "break" on purpose: fallback to the 24bit address case. */
>
>> + case 3:
>> + iar = (cmd->enable.bits.data) ? 0 : cmd->address;
>> + ifr |= QSPI_IFR_ADDREN;
>> + break;
>> + case 0:
>> + break;
>> + default:
>> + return -EINVAL;
>> + }
>
> [...]
>
>> +no_data:
>> + /* Poll INSTRuction End status */
>> + sr = qspi_readl(aq, QSPI_SR);
>> + if (sr & QSPI_SR_INSTRE)
>> + return err;
>> +
>> + /* Wait for INSTRuction End interrupt */
>> + init_completion(&aq->completion);
>
> You should use reinit_completion() in the code. init_completion()
> should be used only in the probe() function and nowhere else.
Alright. In the next version I'll rename the "completion" member of
struct atmel_qspi into "cmd_completion". Also I'll add another dma_completion
member in this very same structure to replace the local
"struct completion completion" in atmel_qspi_run_dma_transfer().
Then I'll call init_completion() on both cmd_completion and dma_completion only
from atmel_qspi_probe() and reinit_completion() elsewhere.
>
>> + aq->pending = 0;
>> + qspi_writel(aq, QSPI_IER, QSPI_SR_INSTRE);
>> + if (!wait_for_completion_timeout(&aq->completion,
>> + msecs_to_jiffies(1000)))
>> + err = -ETIMEDOUT;
>> + qspi_writel(aq, QSPI_IDR, QSPI_SR_INSTRE);
>> +
>> + return err;
>> +}
>
> [...]
>
> Hope this helps :)
>
Indeed, it does! I still work on the next version of this series to take all your
comments into account.
Best regards,
Cyrille
next prev parent reply other threads:[~2015-08-24 17:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 10:13 [PATCH linux-next v4 0/5] add driver for Atmel QSPI controller Cyrille Pitchen
2015-08-24 10:13 ` [PATCH linux-next v4 1/5] mtd: spi-nor: notify (Q)SPI controller about protocol change Cyrille Pitchen
2015-08-24 10:16 ` Marek Vasut
[not found] ` <cover.1440410236.git.cyrille.pitchen-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2015-08-24 10:13 ` [PATCH linux-next v4 2/5] Documentation: mtd: add a DT property to set the number of dummy cycles Cyrille Pitchen
2015-08-24 10:13 ` [PATCH linux-next v4 3/5] mtd: spi-nor: allow to tune " Cyrille Pitchen
2015-08-24 10:48 ` Marek Vasut
[not found] ` <201508241248.17466.marex-ynQEQJNshbs@public.gmane.org>
2015-08-24 16:42 ` Cyrille Pitchen
[not found] ` <55DB4986.1000207-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2015-08-24 16:48 ` Marek Vasut
2015-08-24 10:13 ` [PATCH linux-next v4 4/5] Documentation: atmel-quadspi: add binding file for Atmel QSPI driver Cyrille Pitchen
[not found] ` <d45c21eab00863f379a0388b439a6ae5c44f7acc.1440410236.git.cyrille.pitchen-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2015-08-24 10:22 ` Marek Vasut
2015-08-24 10:14 ` [PATCH linux-next v4 5/5] mtd: atmel-quadspi: add driver for Atmel QSPI controller Cyrille Pitchen
[not found] ` <bf368fc101f38db231131b69eff0863210f2b01c.1440410236.git.cyrille.pitchen-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2015-08-24 11:03 ` Marek Vasut
[not found] ` <201508241303.52066.marex-ynQEQJNshbs@public.gmane.org>
2015-08-24 12:49 ` Russell King - ARM Linux
2015-08-24 13:15 ` Marek Vasut
2015-08-24 17:04 ` Cyrille Pitchen [this message]
[not found] ` <55DB4EA6.9090807-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2015-08-24 17:45 ` Marek Vasut
[not found] ` <201508241945.33577.marex-ynQEQJNshbs@public.gmane.org>
2015-08-25 9:46 ` Jonas Gorski
[not found] ` <CAOiHx=kExyKAoGW4ciWHHxGNosNR0VdvHHrSqeo7RH1rNOXgig-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-08-25 10:21 ` Cyrille Pitchen
2015-08-25 10:17 ` Cyrille Pitchen
[not found] ` <55DC40C1.3050405-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2015-08-25 10:22 ` Marek Vasut
[not found] ` <201508251222.10813.marex-ynQEQJNshbs@public.gmane.org>
2015-08-25 15:57 ` Brian Norris
2015-08-25 1:44 ` Bean Huo 霍斌斌 (beanhuo)
[not found] ` <A765B125120D1346A63912DDE6D8B6310BF47A26-xjs9rfTec9KBtk7LW/CC8tTcztV8WXajQQ4Iyu8u01E@public.gmane.org>
2015-08-25 11:24 ` Cyrille Pitchen
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=55DB4EA6.9090807@atmel.com \
--to=cyrille.pitchen@atmel.com \
--cc=beanhuo@micron.com \
--cc=ben@decadent.org.uk \
--cc=broonie@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=juhosg@openwrt.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=marex@denx.de \
--cc=mark.rutland@arm.com \
--cc=nicolas.ferre@atmel.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=shijie.huang@intel.com \
--cc=zajec5@gmail.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).