From: andrew-ct chen <andrew-ct.chen@mediatek.com>
To: Chih-En Hsu <chih-en.hsu@mediatek.com>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <srv_heupstream@mediatek.com>,
<Michael.Mei@mediatek.com>
Subject: Re: [PATCH v3] nvmem: mtk-efuse: Remove EFUSE register write support
Date: Wed, 26 Aug 2020 21:31:09 +0800 [thread overview]
Message-ID: <1598448669.18394.8.camel@mtksdaap41> (raw)
In-Reply-To: <20200826083943.810-1-chih-en.hsu@mediatek.com>
Hi Chih-En,
On Wed, 2020-08-26 at 16:39 +0800, Chih-En Hsu wrote:
> This patch is to remove function "mtk_reg_write" since
> Mediatek EFUSE hardware only supports read functionality
> for NVMEM consumers.
Acked-by: Andrew-CT Chen <andrew-ct.chen@mediatek.com>
>
> Fixes: ba360fd040e3 ("nvmem: mtk-efuse: remove nvmem regmap dependency")
> Signed-off-by: Chih-En Hsu <chih-en.hsu@mediatek.com>
> ---
> drivers/nvmem/mtk-efuse.c | 14 --------------
> 1 file changed, 14 deletions(-)
>
> diff --git a/drivers/nvmem/mtk-efuse.c b/drivers/nvmem/mtk-efuse.c
> index 856d9c3fc38e..6a537d959f14 100644
> --- a/drivers/nvmem/mtk-efuse.c
> +++ b/drivers/nvmem/mtk-efuse.c
> @@ -28,19 +28,6 @@ static int mtk_reg_read(void *context,
> return 0;
> }
>
> -static int mtk_reg_write(void *context,
> - unsigned int reg, void *_val, size_t bytes)
> -{
> - struct mtk_efuse_priv *priv = context;
> - u32 *val = _val;
> - int i = 0, words = bytes / 4;
> -
> - while (words--)
> - writel(*val++, priv->base + reg + (i++ * 4));
> -
> - return 0;
> -}
> -
> static int mtk_efuse_probe(struct platform_device *pdev)
> {
> struct device *dev = &pdev->dev;
> @@ -61,7 +48,6 @@ static int mtk_efuse_probe(struct platform_device *pdev)
> econfig.stride = 4;
> econfig.word_size = 4;
> econfig.reg_read = mtk_reg_read;
> - econfig.reg_write = mtk_reg_write;
> econfig.size = resource_size(res);
> econfig.priv = priv;
> econfig.dev = dev;
next prev parent reply other threads:[~2020-08-26 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 8:39 [PATCH v3] nvmem: mtk-efuse: Remove EFUSE register write support Chih-En Hsu
2020-08-26 13:31 ` andrew-ct chen [this message]
2020-09-04 11:07 ` Srinivas Kandagatla
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=1598448669.18394.8.camel@mtksdaap41 \
--to=andrew-ct.chen@mediatek.com \
--cc=Michael.Mei@mediatek.com \
--cc=chih-en.hsu@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=srv_heupstream@mediatek.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).