From: Chih-En Hsu <chih-en.hsu@mediatek.com>
To: andrew-ct chen <andrew-ct.chen@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 v2] nvmem: mtk-efuse: Remove EFUSE register write support
Date: Wed, 26 Aug 2020 16:38:05 +0800 [thread overview]
Message-ID: <1598431085.604.0.camel@mtksdccf07> (raw)
In-Reply-To: <1598430653.18394.5.camel@mtksdaap41>
Hi Andrew:
OK, I will fix it.
Thanks a lot.
Alex
On Wed, 2020-08-26 at 16:30 +0800, andrew-ct chen wrote:
> Hi Chih-En,
>
> On Wed, 2020-08-26 at 14:21 +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.
>
> The fixed patch should be ba360fd040e34 ("nvmem: mtk-efuse: remove nvmem
> regmap dependency")
>
> > Fixes: 4c7e4fe37766 ("nvmem: mediatek: Add Mediatek EFUSE driver")
> > 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;
>
>
prev parent reply other threads:[~2020-08-26 8:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 6:21 [PATCH v2] nvmem: mtk-efuse: Remove EFUSE register write support Chih-En Hsu
2020-08-26 7:34 ` CK Hu
2020-08-26 8:30 ` andrew-ct chen
2020-08-26 8:38 ` Chih-En Hsu [this message]
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=1598431085.604.0.camel@mtksdccf07 \
--to=chih-en.hsu@mediatek.com \
--cc=Michael.Mei@mediatek.com \
--cc=andrew-ct.chen@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