From: CK Hu <ck.hu@mediatek.com>
To: jason-jh.lin <jason-jh.lin@mediatek.com>,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
"Chun-Kuang Hu" <chunkuang.hu@kernel.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: David Airlie <airlied@linux.ie>, <singo.chang@mediatek.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
<postmaster@vger.kernel.org>,
"Fabien Parent" <fparent@baylibre.com>,
John 'Warthog9' Hawley <warthog9@eaglescrag.net>,
<linux-stm32@st-md-mailman.stormreply.com>,
<roy-cw.yeh@mediatek.com>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
<devicetree@vger.kernel.org>, Daniel Vetter <daniel@ffwll.ch>,
<nancy.lin@mediatek.com>, <linux-mediatek@lists.infradead.org>,
<hsinyi@chromium.org>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <moudy.ho@mediatek.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>
Subject: Re: [RESEND v17 3/7] soc: mediatek: add mtk-mmsys support for mt8195 vdosys0
Date: Thu, 7 Apr 2022 13:58:30 +0800 [thread overview]
Message-ID: <f04154f2908d3420bc48ed35273a1d4866bd40af.camel@mediatek.com> (raw)
In-Reply-To: <20220407030409.9664-4-jason-jh.lin@mediatek.com>
Hi, Jason:
On Thu, 2022-04-07 at 11:04 +0800, jason-jh.lin wrote:
> 1. Add mt8195 mmsys compatible for vdosys0.
> 2. Add mt8195 routing table settings and fix build fail.
> 3. Add clock name, clock driver name and routing table into the
> driver data
> of mt8195 vdosys0.
> 4. Add get match data by clock name function and clock platform
> labels
> to identify which mmsys node is corresponding to vdosys0.
>
> Signed-off-by: jason-jh.lin <jason-jh.lin@mediatek.com>
>
[snip]
>
> +static const struct mtk_mmsys_driver_data mt8195_vdosys0_driver_data
> = {
> + .clk_name = "cfg_vdo0",
> + .clk_driver = "clk-mt8195-vdo0",
> + .routes = mmsys_mt8195_routing_table,
> + .num_routes = ARRAY_SIZE(mmsys_mt8195_routing_table),
> +};
> +
>
[snip]
>
> +static int mtk_mmsys_get_match_data_by_clk_name(const struct
> mtk_mmsys_driver_data **data,
> + struct device *dev)
> +{
> + int i;
> + struct clk *clk;
> + const char *clk_name;
> + const struct of_device_id *of_id =
> of_match_node(mtk_clk_platform_labels,
> + dev->of_node);
> + const struct mtk_mmsys_driver_data *drvdata[] = {
> + &mt8195_vdosys0_driver_data,
> + };
> +
> + if (!of_id || !of_id->data) {
> + dev_err(dev, "Can't find match clk platform labels\n");
> + return -EINVAL;
> + }
> +
> + clk = devm_clk_get(dev, NULL);
> + if (IS_ERR(clk)) {
> + dev_err(dev, "failed to get mmsys clk\n");
> + return PTR_ERR(clk);
> + }
> +
> + clk_name = __clk_get_name(clk);
> + if (!clk_name) {
> + dev_err(dev, "invalid mmsys clk name\n");
> + return -EINVAL;
> + }
> +
> + for (i = 0; i < ARRAY_SIZE(drvdata); i++)
> + if (strncmp(drvdata[i]->clk_name, clk_name,
> strlen(clk_name)) == 0 &&
Why not
strcmp(drvdata[i]->clk_name, clk_name) == 0
Regards,
CK
> + strncmp(drvdata[i]->clk_driver, of_id->data,
> strlen(of_id->data)) == 0) {
> + *data = drvdata[i];
> + return 0;
> + }
> +
> + return -EINVAL;
> +}
> +
>
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2022-04-07 5:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 3:04 [RESEND v17 0/7] Add Mediatek Soc DRM (vdosys0) support for mt8195 jason-jh.lin
2022-04-07 3:04 ` [RESEND v17 1/7] dt-bindings: arm: mediatek: mmsys: add power and gce properties jason-jh.lin
2022-04-07 3:04 ` [RESEND v17 2/7] dt-bindings: arm: mediatek: mmsys: add mt8195 SoC binding jason-jh.lin
2022-04-07 5:12 ` CK Hu
2022-04-07 8:30 ` AngeloGioacchino Del Regno
2022-04-07 3:04 ` [RESEND v17 3/7] soc: mediatek: add mtk-mmsys support for mt8195 vdosys0 jason-jh.lin
2022-04-07 5:45 ` CK Hu
2022-04-07 6:27 ` Jason-JH Lin
2022-04-08 1:28 ` CK Hu
2022-04-08 8:49 ` AngeloGioacchino Del Regno
2022-04-12 6:33 ` CK Hu
2022-04-07 5:58 ` CK Hu [this message]
2022-04-08 1:42 ` Jason-JH Lin
2022-04-07 9:11 ` AngeloGioacchino Del Regno
2022-04-08 2:42 ` Jason-JH Lin
2022-04-08 8:34 ` AngeloGioacchino Del Regno
2022-04-07 3:04 ` [RESEND v17 4/7] soc: mediatek: add mtk-mutex " jason-jh.lin
2022-04-07 3:04 ` [RESEND v17 5/7] drm/mediatek: add DSC support for mediatek-drm jason-jh.lin
2022-04-07 3:04 ` [RESEND v17 6/7] drm/mediatek: add MERGE " jason-jh.lin
2022-04-07 3:04 ` [RESEND v17 7/7] drm/mediatek: add mediatek-drm of vdosys0 support for mt8195 jason-jh.lin
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=f04154f2908d3420bc48ed35273a1d4866bd40af.camel@mediatek.com \
--to=ck.hu@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=airlied@linux.ie \
--cc=alexandre.torgue@foss.st.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=fparent@baylibre.com \
--cc=hsinyi@chromium.org \
--cc=jason-jh.lin@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=matthias.bgg@gmail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=moudy.ho@mediatek.com \
--cc=nancy.lin@mediatek.com \
--cc=p.zabel@pengutronix.de \
--cc=postmaster@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=roy-cw.yeh@mediatek.com \
--cc=singo.chang@mediatek.com \
--cc=warthog9@eaglescrag.net \
/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