[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2f9aa86e-40e1-91f6-06b2-c79d62f7a136@infradead.org>
Date: Mon, 20 Feb 2023 11:55:58 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: Rafał Miłecki <zajec5@...il.com>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>
Cc: Matthias Brugger <matthias.bgg@...il.com>,
Kunihiko Hayashi <hayashi.kunihiko@...ionext.com>,
Masami Hiramatsu <mhiramat@...nel.org>,
linux-mediatek@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
Rafał Miłecki <rafal@...ecki.pl>
Subject: Re: [PATCH V3 2/2] nvmem: add generic driver for devices with MMIO
access
Hi,
On 2/20/23 09:49, Rafał Miłecki wrote:
> +static int mmio_nvmem_write(void *context, unsigned int offset, void *val, size_t bytes)
> +{
> + struct mmio_nvmem *priv = context;
> +
> + switch (priv->io_width) {
> + case 1:
> + case 2:
> + case 4:
> + return -EOPNOTSUPP;
I'm just curious: (since read supports those cases)
what size writes are typically used here?
And what value for priv->io_width?
Thanks.
> + default:
> + memcpy_toio(priv->base + offset, val, bytes);
> + }
> +
> + return 0;
> +}
--
~Randy
Powered by blists - more mailing lists