From: Miles Chen <miles.chen@mediatek.com>
To: <yassine.oudjana@gmail.com>
Cc: <angelogioacchino.delregno@collabora.com>,
<bgolaszewski@baylibre.com>, <chun-jie.chen@mediatek.com>,
<devicetree@vger.kernel.org>, <ikjn@chromium.org>,
<krzysztof.kozlowski+dt@linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-clk@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>, <matthias.bgg@gmail.com>,
<miles.chen@mediatek.com>, <mturquette@baylibre.com>,
<p.zabel@pengutronix.de>, <robh+dt@kernel.org>,
<sam.shih@mediatek.com>, <sboyd@kernel.org>,
<tinghan.shen@mediatek.com>, <weiyi.lu@mediatek.com>,
<wenst@chromium.org>, <y.oudjana@protonmail.com>,
<~postmarketos/upstreaming@lists.sr.ht>
Subject: Re: [PATCH v2 4/4] clk: mediatek: Add drivers for MediaTek MT6735 main clock drivers
Date: Fri, 20 May 2022 16:35:14 +0800 [thread overview]
Message-ID: <20220520083514.27891-1-miles.chen@mediatek.com> (raw)
In-Reply-To: <20220519142211.458336-5-y.oudjana@protonmail.com>
hi Yassine,
> Add drivers for MT6735 apmixedsys, topckgen, infracfg and pericfg
> clock and reset controllers. These provide the base clocks on the
> platform, and should be enough to bring up all essential blocks
> including PWRAP, MSDC and peripherals (UART, I2C, SPI).
>
> Signed-off-by: Yassine Oudjana <y.oudjana@protonmail.com>
> ---
> Dependencies:
> - clk: mediatek: Move to struct clk_hw provider APIs (series)
> https://patchwork.kernel.org/project/linux-mediatek/cover/20220510104804.544597-1-wenst@chromium.org/
> - Cleanup MediaTek clk reset drivers and support MT8192/MT8195 (series)
> https://patchwork.kernel.org/project/linux-mediatek/cover/20220503093856.22250-1-rex-bc.chen@mediatek.com/
> - Export required symbols to compile clk drivers as module (single patch)
> https://patchwork.kernel.org/project/linux-mediatek/patch/20220518111652.223727-7-angelogioacchino.delregno@collabora.com/
> - clk: mediatek: Improvements to simple probe/remove and reset controller unregistration
> https://patchwork.kernel.org/project/linux-clk/cover/20220519134728.456643-1-y.oudjana@protonmail.com/
>
> MAINTAINERS | 4 +
> drivers/clk/mediatek/Kconfig | 9 +
> drivers/clk/mediatek/Makefile | 1 +
> drivers/clk/mediatek/clk-mt6735-apmixedsys.c | 235 ++++
...snip...
> +#define APLL2_CON0 0x284
> +#define APLL2_CON1 0x288
> +#define APLL2_CON2 0x28c
> +#define APLL2_PWR_CON0 0x294
> +
> +#define CON0_RST_BAR BIT(24)
> +
> +static const struct mtk_pll_data apmixedsys_plls[] = {
> + {
> + .id = ARMPLL,
> + .name = "armpll",
> + .parent_name = "clk26m",
> +
> + .reg = ARMPLL_CON0,
> + .pwr_reg = ARMPLL_PWR_CON0,
> + .en_mask = 0x00000001,
> +
> + .pd_reg = ARMPLL_CON1,
> + .pd_shift = 24,
> +
> + .pcw_reg = ARMPLL_CON1,
> + .pcw_chg_reg = ARMPLL_CON1,
> + .pcwbits = 21,
> +
> + .flags = PLL_AO
Thanks for submitting this patch.
I compare this with drivers/clk/mediatek/clk-mt7986-apmixed.c,
and other clk files are using macros to make the mtk_pll_data array
more readable.
Would you mind following the same style for all c files, please?
e.g.,
static const struct mtk_pll_data plls[] = {
PLL(CLK_APMIXED_ARMPLL, "armpll", 0x0200, 0x020C, 0x00000001, 0, 32,
0x0200, 4, 0, 0x0204, 0),
PLL(CLK_APMIXED_NET2PLL, "net2pll", 0x0210, 0x021C, 0x00000001, 0, 32,
0x0210, 4, 0, 0x0214, 0),
...
};
> + },
> + {
> + .id = MAINPLL,
> + .name = "mainpll",
> + .parent_name = "clk26m",
> +
> + .reg = MAINPLL_CON0,
> + .pwr_reg = MAINPLL_PWR_CON0,
> + .en_mask = 0xf0000101,
> +
> + .pd_reg = MAINPLL_CON1,
> + .pd_shift = 24,
> +
> + .pcw_reg = MAINPLL_CON1,
> + .pcw_chg_reg = MAINPLL_CON1,
> + .pcwbits = 21,
> +
> + .flags = HAVE_RST_BAR,
> + .rst_bar_mask = CON0_RST_BAR
> + },
> + {
> + .id = UNIVPLL,
> + .name = "univpll",
> + .parent_name = "clk26m",
> +
> + .reg = UNIVPLL_CON0,
> + .pwr_reg = UNIVPLL_PWR_CON0,
> + .en_mask = 0xfc000001,
> +
> + .pd_reg = UNIVPLL_CON1,
> + .pd_shift = 24,
> +
> + .pcw_reg = UNIVPLL_CON1,
> + .pcw_chg_reg = UNIVPLL_CON1,
> + .pcwbits = 21,
> +
> + .flags = HAVE_RST_BAR,
> + .rst_bar_mask = CON0_RST_BAR
> + },
> + {
> + .id = MMPLL,
> + .name = "mmpll",
> + .parent_name = "clk26m",
> +
> + .reg = MMPLL_CON0,
> + .pwr_reg = MMPLL_PWR_CON0,
> + .en_mask = 0x00000001,
> +
> + .pd_reg = MMPLL_CON1,
> + .pd_shift = 24,
> +
> + .pcw_reg = MMPLL_CON1,
> + .pcw_chg_reg = MMPLL_CON1,
> + .pcwbits = 21
> + },
> + {
> + .id = MSDCPLL,
> + .name = "msdcpll",
> + .parent_name = "clk26m",
> +
> + .reg = MSDCPLL_CON0,
> + .pwr_reg = MSDCPLL_PWR_CON0,
> + .en_mask = 0x00000001,
> +
> + .pd_reg = MSDCPLL_CON1,
> + .pd_shift = 24,
> +
> + .pcw_reg = MSDCPLL_CON1,
> + .pcw_chg_reg = MSDCPLL_CON1,
> + .pcwbits = 21,
> + },
> + {
> + .id = VENCPLL,
> + .name = "vencpll",
> + .parent_name = "clk26m",
> +
> + .reg = VENCPLL_CON0,
> + .pwr_reg = VENCPLL_PWR_CON0,
> + .en_mask = 0x00000001,
> +
> + .pd_reg = VENCPLL_CON1,
> + .pd_shift = 24,
> +
> + .pcw_reg = VENCPLL_CON1,
> + .pcw_chg_reg = VENCPLL_CON1,
> + .pcwbits = 21,
> +
> + .flags = HAVE_RST_BAR,
> + .rst_bar_mask = CON0_RST_BAR
> + },
> + {
> + .id = TVDPLL,
> + .name = "tvdpll",
> + .parent_name = "clk26m",
> +
> + .reg = TVDPLL_CON0,
> + .pwr_reg = TVDPLL_PWR_CON0,
> + .en_mask = 0x00000001,
> +
> + .pd_reg = TVDPLL_CON1,
> + .pd_shift = 24,
> +
> + .pcw_reg = TVDPLL_CON1,
> + .pcw_chg_reg = TVDPLL_CON1,
> + .pcwbits = 21
> + },
> + {
> + .id = APLL1,
> + .name = "apll1",
> + .parent_name = "clk26m",
> +
> + .reg = APLL1_CON0,
> + .pwr_reg = APLL1_PWR_CON0,
> +module_platform_driver(clk_mt6735_apmixedsys);
> +
> +MODULE_AUTHOR("Yassine Oudjana <y.oudjana@protonmail.com>");
> +MODULE_DESCRIPTION("Mediatek MT6735 apmixedsys clock driver");
Would you mind changing all Mediatek to MediaTek?
i.e.,
s/Mediatek/MediaTek/
thanks,
Miles
> +MODULE_LICENSE("GPL");
next prev parent reply other threads:[~2022-05-20 8:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 14:22 [PATCH v2 0/4] Mediatek MT6735 main clock and reset drivers Yassine Oudjana
2022-05-19 14:22 ` [PATCH v2 1/4] dt-bindings: clock: Add Mediatek MT6735 clock bindings Yassine Oudjana
2022-05-19 14:22 ` [PATCH v2 2/4] dt-bindings: reset: Add MT6735 reset bindings Yassine Oudjana
2022-05-20 8:55 ` AngeloGioacchino Del Regno
2022-05-20 9:13 ` Yassine Oudjana
2022-05-23 12:15 ` AngeloGioacchino Del Regno
2022-05-19 14:22 ` [PATCH v2 3/4] dt-bindings: arm: mediatek: Add MT6735 clock controller compatibles Yassine Oudjana
2022-05-19 14:22 ` [PATCH v2 4/4] clk: mediatek: Add drivers for MediaTek MT6735 main clock drivers Yassine Oudjana
2022-05-20 8:35 ` Miles Chen [this message]
2022-05-20 9:18 ` Yassine Oudjana
2022-05-20 9:35 ` Miles Chen
2022-05-20 10:26 ` AngeloGioacchino Del Regno
2022-05-20 11:08 ` Yassine Oudjana
2022-05-22 17:02 ` Miles Chen
2022-08-13 10:44 ` Yassine Oudjana
2022-08-29 9:31 ` AngeloGioacchino Del Regno
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=20220520083514.27891-1-miles.chen@mediatek.com \
--to=miles.chen@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bgolaszewski@baylibre.com \
--cc=chun-jie.chen@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=ikjn@chromium.org \
--cc=krzysztof.kozlowski+dt@linaro.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=matthias.bgg@gmail.com \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=sam.shih@mediatek.com \
--cc=sboyd@kernel.org \
--cc=tinghan.shen@mediatek.com \
--cc=weiyi.lu@mediatek.com \
--cc=wenst@chromium.org \
--cc=y.oudjana@protonmail.com \
--cc=yassine.oudjana@gmail.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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
Powered by JetHome