[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YlVJc3z1xXT2emIc@ninjato>
Date: Tue, 12 Apr 2022 11:42:11 +0200
From: Wolfram Sang <wsa+renesas@...g-engineering.com>
To: Geert Uytterhoeven <geert+renesas@...der.be>
Cc: Krzysztof Kozlowski <krzk@...nel.org>,
Sergey Shtylyov <s.shtylyov@....ru>,
Duc Nguyen <duc.nguyen.ub@...esas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>,
Andrew Gabbasov <andrew_gabbasov@...tor.com>,
linux-renesas-soc@...r.kernel.org, linux-mtd@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] memory: renesas-rpc-if: Simplify single/double data
register access
On Mon, Apr 11, 2022 at 02:55:29PM +0200, Geert Uytterhoeven wrote:
> For manual write and read, factor out the common access to the first
> data register by keeping track of the current data pointer.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be>
Works fine with reading/writing on a V3U, so:
Tested-by: Wolfram Sang <wsa+renesas@...g-engineering.com>
I agree the code is more concise. I am not sure, though, if it is really
more readable. But I don't mind very much, so except for a small nit:
Reviewed-by: Wolfram Sang <wsa+renesas@...g-engineering.com>
> + if (nbytes == 8)
> + regmap_write(rpc->regmap, RPCIF_SMWDR1, *p++);
> + regmap_write(rpc->regmap, RPCIF_SMWDR0, *p++);
Last '++' can be omitted?
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists