From: sashiko-bot@kernel.org
To: "Luca Leonardo Scorcia" <l.scorcia@gmail.com>
Cc: robh@kernel.org, vkoul@kernel.org, devicetree@vger.kernel.org,
dri-devel@lists.freedesktop.org, neil.armstrong@linaro.org,
linux-phy@lists.infradead.org, linux-clk@vger.kernel.org,
conor+dt@kernel.org, olteanv@gmail.com
Subject: Re: [PATCH 3/7] clk: mediatek: mt8167: Map apmixedsys iomem as shared
Date: Sat, 10 Oct 2026 12:02:48 +0000 [thread overview]
Message-ID: <sashiko-outbox-166483@kernel.org> (raw)
In-Reply-To: <20261010115539.9237-4-l.scorcia@gmail.com>
Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider:
- [High] clk: mediatek: IS_ERR() used to check of_iomap() return value instead of NULL check
- [High] clk: mediatek: missing platform_set_drvdata() causes silent failure in remove()
- [Medium] clk: mediatek: missing iounmap() for driver base mapping in remove()
--
commit 847eb51d406a77cda5e7387f55742129733ec7b6
Author: Luca Leonardo Scorcia <l.scorcia@gmail.com>
clk: mediatek: mt8167: Map apmixedsys iomem as shared
The hdmi_phy for mt8167 and the apmixedsys clocks share the same IO
memory region and they both map it using devm_platform_ioremap_resource,
which implies exclusive access. Switch the apmixedsys driver to of_iomap,
like it is done in the mt8173-apmixedsys driver. Also, implement the
remove function while we're at it.
> diff --git a/drivers/clk/mediatek/clk-mt8167-apmixedsys.c b/drivers/clk/mediatek/clk-mt8167-apmixedsys.c
> index fb6c21bbeef81..3e8611991de78 100644
> --- a/drivers/clk/mediatek/clk-mt8167-apmixedsys.c
> +++ b/drivers/clk/mediatek/clk-mt8167-apmixedsys.c
[ ... ]
> @@ -97,17 +98,19 @@ static int clk_mt8167_apmixed_probe(struct platform_device *pdev)
> struct device *dev = &pdev->dev;
> int ret;
>
> - base = devm_platform_ioremap_resource(pdev, 0);
> + base = of_iomap(node, 0);
> if (IS_ERR(base))
[Severity: High]
Does this code handle the of_iomap() return value correctly? of_iomap()
returns NULL on failure, rather than an ERR_PTR. If it fails, base will be
NULL, which bypasses this error check and propagates to the register
functions.
> return PTR_ERR(base);
>
> clk_data = mtk_devm_alloc_clk_data(dev, MT8167_CLK_APMIXED_NR_CLK);
> - if (!clk_data)
> - return -ENOMEM;
> + if (IS_ERR_OR_NULL(clk_data)) {
[Severity: High]
Does this code need to save clk_data to the device's driver data? It looks
like clk_mt8167_apmixed_probe() allocates clk_data but never calls
platform_set_drvdata() to store it before returning.
> + ret = -ENOMEM;
> + goto unmap_io;
> + }
[ ... ]
> @@ -124,10 +127,22 @@ static int clk_mt8167_apmixed_probe(struct platform_device *pdev)
> mtk_clk_unregister_dividers(adj_divs, ARRAY_SIZE(adj_divs), clk_data);
> unregister_plls:
> mtk_clk_unregister_plls(plls, ARRAY_SIZE(plls), clk_data);
> +unmap_io:
> + iounmap(base);
>
> return ret;
> }
>
> +static void clk_mt8167_apmixed_remove(struct platform_device *pdev)
> +{
> + struct device_node *node = pdev->dev.of_node;
> + struct clk_hw_onecell_data *clk_data = platform_get_drvdata(pdev);
[Severity: High]
Since platform_set_drvdata() was never called in the probe function, won't
platform_get_drvdata() evaluate to NULL here? This would render the
subsequent unregister calls as no-ops, failing to unregister the clocks.
[Severity: Medium]
Does this remove function leak the I/O memory mapping? The base mapping
created by of_iomap() in clk_mt8167_apmixed_probe() doesn't appear to be
unmapped via iounmap() here.
Since base is only a local variable in the probe function and isn't saved to
a device context, there is no way for clk_mt8167_apmixed_remove() to retrieve
the pointer to clean it up.
> +
> + of_clk_del_provider(node);
> + mtk_clk_unregister_dividers(adj_divs, ARRAY_SIZE(adj_divs), clk_data);
> + mtk_clk_unregister_plls(plls, ARRAY_SIZE(plls), clk_data);
> +}
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261010115539.9237-1-l.scorcia@gmail.com?part=3
next prev parent reply other threads:[~2026-10-10 12:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 11:54 [PATCH 0/7] Add support for Mediatek mt8167 HDMI display output Luca Leonardo Scorcia
2026-10-10 11:54 ` [PATCH 1/7] dt-bindings: mediatek: hdmi-phy: Add compatible for mt8167 Luca Leonardo Scorcia
2026-10-12 9:19 ` CK Hu (胡俊光)
2026-10-12 9:41 ` Krzysztof Kozlowski
2026-10-12 9:40 ` Krzysztof Kozlowski
2026-10-12 17:43 ` Luca Leonardo Scorcia
2026-10-10 11:54 ` [PATCH 2/7] phy: mediatek: hdmi: Add support " Luca Leonardo Scorcia
2026-10-10 12:12 ` sashiko-bot
2026-10-10 11:54 ` [PATCH 3/7] clk: mediatek: mt8167: Map apmixedsys iomem as shared Luca Leonardo Scorcia
2026-10-10 12:02 ` sashiko-bot [this message]
2026-10-10 11:54 ` [PATCH 4/7] clk: mediatek: mt8167: Correct HDMI-related clock definitions Luca Leonardo Scorcia
2026-10-10 11:54 ` [PATCH 5/7] drm/mediatek: mtk_hdmi: Set tz_disabled for mt8167 Luca Leonardo Scorcia
2026-10-12 9:37 ` CK Hu (胡俊光)
2026-10-10 11:54 ` [PATCH 6/7] drm/mediatek: mtk_hdmi: Improve the secure output bit toggle Luca Leonardo Scorcia
2026-10-10 11:54 ` [PATCH 7/7] arm64: dts: mediatek: mt8167: Add HDMI display nodes Luca Leonardo Scorcia
2026-10-10 12:08 ` sashiko-bot
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=sashiko-outbox-166483@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=l.scorcia@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=olteanv@gmail.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=vkoul@kernel.org \
/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