From: Krzysztof Kozlowski <krzk@kernel.org>
To: "irving.ch.lin" <irving-ch.lin@mediatek.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
nfraprado@collabora.com
Cc: angelogioacchino.delregno@collabora.com,
Project_Global_Chrome_Upstream_Group@mediatek.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
linux-pm@vger.kernel.org, netdev@vger.kernel.org,
linux-mediatek@lists.infradead.org,
Irving lin <irving-ch.lin@mediatek.corp-partner.google.com>
Subject: Re: clk: mt8189: Porting driver for clk
Date: Mon, 2 Jun 2025 10:33:09 +0200 [thread overview]
Message-ID: <ae1a799c-202e-4aab-8ed8-1be91c780f50@kernel.org> (raw)
In-Reply-To: <20250602082610.1848291-1-irving-ch.lin@mediatek.com>
On 02/06/2025 10:25, irving.ch.lin wrote:
> From: Irving lin <irving-ch.lin@mediatek.corp-partner.google.com>
>
> 1. Add mt8189 clk driver
> 2. Fix mux failed
I don't understand this.
> 3. Add apll12_div_tdmout_b
> 4. Add disable-unused configs
Neither this
>
> BUG=b:387252012
> TEST=emerge-skywalker chromeos-kernel-6_6
Drop these
>
> Signed-off-by: Irving lin <irving-ch.lin@mediatek.corp-partner.google.com>
> ---
Missing bindings / undocumented ABI
There are also several other trivial issues, so this looks like you sent
us old, straight downstream code. This won't work, you need to clean it
up seriously or better start from scratch from recent drivers. Plus read
carefully submitting patches. The way you organized it and sent makes
review very difficult.
Please run standard kernel tools for static analysis, like coccinelle,
smatch and sparse, and fix reported warnings. Also please check for
warnings when building with W=1 for gcc and clang. Most of these
commands (checks or W=1 build) can build specific targets, like some
directory, to narrow the scope to only your code. The code here looks
like it needs a fix. Feel free to get in touch if the warning is not clear.
...
> +static int clk_dbg_mt8189_probe(struct platform_device *pdev)
> +{
> + set_clkdbg_ops(&clkdbg_mt8189_ops);
> +
> + return 0;
> +}
> +
> +static struct platform_driver clk_dbg_mt8189_drv = {
> + .probe = clk_dbg_mt8189_probe,
> + .driver = {
> + .name = "clk-dbg-mt8189",
> + .owner = THIS_MODULE,
10 year old downstream code. Use the tools please or better start from
recent drivers, don't send us 10 year old vendor code.
> + },
> +};
> +
> +/*
> + * init functions
> + */
> +
> +static int __init clkdbg_mt8189_init(void)
> +{
> + scpsys_base = ioremap(0x1C001000, PAGE_SIZE);
So on module load on Qcom platform you will map it? You just broke
absolutely EVERY possible user, platform, machine,
This is really, really terrible code.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-06-02 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 8:25 clk: mt8189: Porting driver for clk irving.ch.lin
2025-06-02 8:33 ` Krzysztof Kozlowski [this message]
2025-06-02 9:16 ` Krzysztof Kozlowski
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=ae1a799c-202e-4aab-8ed8-1be91c780f50@kernel.org \
--to=krzk@kernel.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=irving-ch.lin@mediatek.com \
--cc=irving-ch.lin@mediatek.corp-partner.google.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nfraprado@collabora.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=wim@linux-watchdog.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;
as well as URLs for NNTP newsgroup(s).