From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cyrille Pitchen 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 Message-ID: <55DB4EA6.9090807@atmel.com> References: <201508241303.52066.marex@denx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: , , , , , , , , , , , , , , , , , , To: Marek Vasut Return-path: In-Reply-To: <201508241303.52066.marex@denx.de> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-spi.vger.kernel.org Hi Marek, Le 24/08/2015 13:03, Marek Vasut a =E9crit : > On Monday, August 24, 2015 at 12:14:00 PM, Cyrille Pitchen wrote: >> This driver add support to the new Atmel QSPI controller embedded in= to >> sama5d2x SoCs. It expects a NOR memory to be connected to the QSPI >> controller. >> >> Signed-off-by: Cyrille Pitchen >> Acked-by: Nicolas Ferre >=20 > Hi, >=20 > [...] >=20 >> +/* Register access macros */ >=20 > These are functions, not macros :) >=20 > 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. >=20 > Also, why do you use the _relaxed() versions of the functions ? >=20 >> +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 v= alue) >> +{ >> + writeb_relaxed(value, aq->regs + reg); >> +} >=20 > [...] >=20 >> +static int atmel_qspi_run_command(struct atmel_qspi *aq, >> + const struct atmel_qspi_command *cmd) >> +{ >> + u32 iar, icr, ifr, sr; >> + int err =3D 0; >> + >> + iar =3D 0; >> + icr =3D 0; >> + ifr =3D aq->ifr_width | cmd->ifr_tfrtyp; >> + >> + /* Compute instruction parameters */ >> + if (cmd->enable.bits.instruction) { >> + icr |=3D QSPI_ICR_INST(cmd->instruction); >> + ifr |=3D QSPI_IFR_INSTEN; >> + } >> + >> + /* Compute address parameters */ >> + switch (cmd->enable.bits.address) { >> + case 4: >> + ifr |=3D QSPI_IFR_ADDRL; >> + /*break;*/ /* fallback to the 24bit address case */ >=20 > 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. */ >=20 >> + case 3: >> + iar =3D (cmd->enable.bits.data) ? 0 : cmd->address; >> + ifr |=3D QSPI_IFR_ADDREN; >> + break; >> + case 0: >> + break; >> + default: >> + return -EINVAL; >> + } >=20 > [...] >=20 >> +no_data: >> + /* Poll INSTRuction End status */ >> + sr =3D qspi_readl(aq, QSPI_SR); >> + if (sr & QSPI_SR_INSTRE) >> + return err; >> + >> + /* Wait for INSTRuction End interrupt */ >> + init_completion(&aq->completion); >=20 > 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_comp= letion 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_complet= ion only from atmel_qspi_probe() and reinit_completion() elsewhere. >=20 >> + aq->pending =3D 0; >> + qspi_writel(aq, QSPI_IER, QSPI_SR_INSTRE); >> + if (!wait_for_completion_timeout(&aq->completion, >> + msecs_to_jiffies(1000))) >> + err =3D -ETIMEDOUT; >> + qspi_writel(aq, QSPI_IDR, QSPI_SR_INSTRE); >> + >> + return err; >> +} >=20 > [...] >=20 > Hope this helps :) >=20 Indeed, it does! I still work on the next version of this series to tak= e all your comments into account. Best regards, Cyrille