From: Chen-Yu Tsai <wenst@chromium.org> To: Matthias Brugger <matthias.bgg@gmail.com>, AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>, Srinivas Kandagatla <srinivas.kandagatla@linaro.org> Cc: Chen-Yu Tsai <wenst@chromium.org>, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, William-tw Lin <william-tw.lin@mediatek.com> Subject: [PATCH 3/3] nvmem: mtk-efuse: Drop NVMEM device name Date: Tue, 30 Jan 2024 17:56:53 +0800 [thread overview] Message-ID: <20240130095656.3712469-4-wenst@chromium.org> (raw) In-Reply-To: <20240130095656.3712469-1-wenst@chromium.org> The MT8183 has not one but two efuse devices. The static name and ID causes the second efuse device to fail to probe, due to duplicate sysfs entries. With the rework of the mtk-socinfo driver, lookup by name is no longer necessary. The custom name can simply be dropped. Fixes: 4e6102d60d88 ("nvmem: mtk-efuse: Register MediaTek socinfo driver from efuse") Signed-off-by: Chen-Yu Tsai <wenst@chromium.org> --- drivers/nvmem/mtk-efuse.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/nvmem/mtk-efuse.c b/drivers/nvmem/mtk-efuse.c index f5bebcecf9bd..9caf04667341 100644 --- a/drivers/nvmem/mtk-efuse.c +++ b/drivers/nvmem/mtk-efuse.c @@ -86,7 +86,6 @@ static int mtk_efuse_probe(struct platform_device *pdev) econfig.size = resource_size(res); econfig.priv = priv; econfig.dev = dev; - econfig.name = "mtk-efuse"; if (pdata->uses_post_processing) econfig.fixup_dt_cell_info = &mtk_efuse_fixup_dt_cell_info; nvmem = devm_nvmem_register(dev, &econfig); -- 2.43.0.429.g432eaa2c6b-goog
WARNING: multiple messages have this Message-ID (diff)
From: Chen-Yu Tsai <wenst@chromium.org> To: Matthias Brugger <matthias.bgg@gmail.com>, AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>, Srinivas Kandagatla <srinivas.kandagatla@linaro.org> Cc: Chen-Yu Tsai <wenst@chromium.org>, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, William-tw Lin <william-tw.lin@mediatek.com> Subject: [PATCH 3/3] nvmem: mtk-efuse: Drop NVMEM device name Date: Tue, 30 Jan 2024 17:56:53 +0800 [thread overview] Message-ID: <20240130095656.3712469-4-wenst@chromium.org> (raw) In-Reply-To: <20240130095656.3712469-1-wenst@chromium.org> The MT8183 has not one but two efuse devices. The static name and ID causes the second efuse device to fail to probe, due to duplicate sysfs entries. With the rework of the mtk-socinfo driver, lookup by name is no longer necessary. The custom name can simply be dropped. Fixes: 4e6102d60d88 ("nvmem: mtk-efuse: Register MediaTek socinfo driver from efuse") Signed-off-by: Chen-Yu Tsai <wenst@chromium.org> --- drivers/nvmem/mtk-efuse.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/nvmem/mtk-efuse.c b/drivers/nvmem/mtk-efuse.c index f5bebcecf9bd..9caf04667341 100644 --- a/drivers/nvmem/mtk-efuse.c +++ b/drivers/nvmem/mtk-efuse.c @@ -86,7 +86,6 @@ static int mtk_efuse_probe(struct platform_device *pdev) econfig.size = resource_size(res); econfig.priv = priv; econfig.dev = dev; - econfig.name = "mtk-efuse"; if (pdata->uses_post_processing) econfig.fixup_dt_cell_info = &mtk_efuse_fixup_dt_cell_info; nvmem = devm_nvmem_register(dev, &econfig); -- 2.43.0.429.g432eaa2c6b-goog _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-01-30 9:57 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-30 9:56 [PATCH 0/3] soc: mediatek: mtk-socinfo: Fixes and cleanup Chen-Yu Tsai 2024-01-30 9:56 ` Chen-Yu Tsai 2024-01-30 9:56 ` [PATCH 1/3] soc: mediatek: mtk-socinfo: Clean up NVMEM cell read Chen-Yu Tsai 2024-01-30 9:56 ` Chen-Yu Tsai 2024-01-30 11:20 ` AngeloGioacchino Del Regno 2024-01-30 11:20 ` AngeloGioacchino Del Regno 2024-01-30 9:56 ` [PATCH 2/3] soc: mediatek: mtk-socinfo: Add extra entry for MT8183 Chen-Yu Tsai 2024-01-30 9:56 ` Chen-Yu Tsai 2024-01-30 11:19 ` AngeloGioacchino Del Regno 2024-01-30 11:19 ` AngeloGioacchino Del Regno 2024-01-31 7:19 ` William-tw Lin (林鼎崴) 2024-01-30 9:56 ` Chen-Yu Tsai [this message] 2024-01-30 9:56 ` [PATCH 3/3] nvmem: mtk-efuse: Drop NVMEM device name Chen-Yu Tsai 2024-01-30 11:15 ` AngeloGioacchino Del Regno 2024-01-30 11:15 ` AngeloGioacchino Del Regno 2024-02-06 16:14 ` Nícolas F. R. A. Prado 2024-02-06 16:14 ` Nícolas F. R. A. Prado 2024-02-13 13:07 ` Srinivas Kandagatla 2024-02-13 13:07 ` Srinivas Kandagatla 2024-02-13 14:13 ` Chen-Yu Tsai 2024-02-13 14:13 ` Chen-Yu Tsai 2024-01-31 8:44 ` [PATCH 0/3] soc: mediatek: mtk-socinfo: Fixes and cleanup AngeloGioacchino Del Regno 2024-01-31 8:44 ` AngeloGioacchino Del Regno 2024-02-13 14:36 ` (subset) " Srinivas Kandagatla 2024-02-13 14:36 ` 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=20240130095656.3712469-4-wenst@chromium.org \ --to=wenst@chromium.org \ --cc=angelogioacchino.delregno@collabora.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=william-tw.lin@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.