From: Matthias Brugger <matthias.bgg@gmail.com>
To: Fabien Parent <fparent@baylibre.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] soc: mediatek: mmsys: Add support for MT8167 SoC
Date: Tue, 30 Mar 2021 11:15:47 +0200 [thread overview]
Message-ID: <052990a7-673f-31f4-2453-a84b007cdbcf@gmail.com> (raw)
In-Reply-To: <20201027160631.608503-2-fparent@baylibre.com>
Hi Fabien,
Sorry for taking so long on that patch.
Generally the patch looks good, but I just merged a small change how we add new
SoC to the driver.
Please see comments below.
On 27/10/2020 17:06, Fabien Parent wrote:
> Add routing table for DSI on MT8167 SoC. The registers are mostly
> incompatible with the current defines, so new one for MT8167 are added.
>
> Signed-off-by: Fabien Parent <fparent@baylibre.com>
> ---
>
> This patch depends on the patch series
> "soc: mediatek: Prepare MMSYS for DDP routing using tables"
>
> [0] https://lore.kernel.org/patchwork/cover/1317813/
>
> drivers/soc/mediatek/mtk-mmsys.c | 50 ++++++++++++++++++++++++++++++++
> 1 file changed, 50 insertions(+)
>
> diff --git a/drivers/soc/mediatek/mtk-mmsys.c b/drivers/soc/mediatek/mtk-mmsys.c
> index f00d6d08c9c5..9890990a74a9 100644
> --- a/drivers/soc/mediatek/mtk-mmsys.c
> +++ b/drivers/soc/mediatek/mtk-mmsys.c
> @@ -85,6 +85,22 @@
> #define DSI_SEL_IN_RDMA 0x1
> #define DSI_SEL_IN_MASK 0x1
>
> +/* MT8167 */
> +#define MT8167_DISP_REG_CONFIG_DISP_OVL0_MOUT_EN 0x030
> +#define MT8167_DISP_REG_CONFIG_DISP_DITHER_MOUT_EN 0x038
> +#define MT8167_DISP_REG_CONFIG_DISP_COLOR0_SEL_IN 0x058
> +#define MT8167_DISP_REG_CONFIG_DISP_DSI0_SEL_IN 0x064
> +#define MT8167_DISP_REG_CONFIG_DISP_RDMA0_SOUT_SEL_IN 0x06c
> +
> +#define MT8167_DITHER_MOUT_EN_RDMA0 BIT(0)
> +#define MT8167_DITHER_MOUT_EN_MASK 0x7
> +
> +#define MT8167_RDMA0_SOUT_DSI0 0x2
> +#define MT8167_RDMA0_SOUT_MASK 0x3
> +
> +#define MT8167_DSI0_SEL_IN_RDMA0 0x1
> +#define MT8167_DSI0_SEL_IN_MASK 0x3
> +
> struct mtk_mmsys_routes {
> u32 from_comp;
> u32 to_comp;
> @@ -124,6 +140,30 @@ struct mtk_mmsys {
> const struct mtk_mmsys_driver_data *data;
> };
>
> +static const struct mtk_mmsys_routes mt8167_mmsys_routing_table[] = {
Please put the defines and the routing table in a separate header file
mt8167-mmsys.h
Thanks and once again sorry for the inconvenience.
Matthias
> + {
> + DDP_COMPONENT_OVL0, DDP_COMPONENT_COLOR0,
> + MT8167_DISP_REG_CONFIG_DISP_OVL0_MOUT_EN,
> + OVL0_MOUT_EN_COLOR0, OVL0_MOUT_EN_COLOR0
> + }, {
> + DDP_COMPONENT_DITHER, DDP_COMPONENT_RDMA0,
> + MT8167_DISP_REG_CONFIG_DISP_DITHER_MOUT_EN,
> + MT8167_DITHER_MOUT_EN_MASK, MT8167_DITHER_MOUT_EN_RDMA0
> + }, {
> + DDP_COMPONENT_OVL0, DDP_COMPONENT_COLOR0,
> + MT8167_DISP_REG_CONFIG_DISP_COLOR0_SEL_IN,
> + COLOR0_SEL_IN_OVL0, COLOR0_SEL_IN_OVL0
> + }, {
> + DDP_COMPONENT_RDMA0, DDP_COMPONENT_DSI0,
> + MT8167_DISP_REG_CONFIG_DISP_DSI0_SEL_IN,
> + MT8167_DSI0_SEL_IN_MASK, MT8167_DSI0_SEL_IN_RDMA0
> + }, {
> + DDP_COMPONENT_RDMA0, DDP_COMPONENT_DSI0,
> + MT8167_DISP_REG_CONFIG_DISP_RDMA0_SOUT_SEL_IN,
> + MT8167_RDMA0_SOUT_MASK, MT8167_RDMA0_SOUT_DSI0
> + },
> +};
> +
> static const struct mtk_mmsys_routes mt8173_mmsys_routing_table[] = {
> {
> DDP_COMPONENT_BLS, DDP_COMPONENT_DSI0,
> @@ -288,6 +328,12 @@ static const struct mtk_mmsys_routes mt8173_mmsys_routing_table[] = {
> }
> };
>
> +static const struct mtk_mmsys_driver_data mt8167_mmsys_driver_data = {
> + .clk_driver = "clk-mt8167-mm",
> + .routes = mt8167_mmsys_routing_table,
> + .num_routes = ARRAY_SIZE(mt8167_mmsys_routing_table),
> +};
> +
> static const struct mtk_mmsys_driver_data mt8173_mmsys_driver_data = {
> .clk_driver = "clk-mt8173-mm",
> .routes = mt8173_mmsys_routing_table,
> @@ -385,6 +431,10 @@ static const struct of_device_id of_match_mtk_mmsys[] = {
> .compatible = "mediatek,mt6797-mmsys",
> .data = &mt6797_mmsys_driver_data,
> },
> + {
> + .compatible = "mediatek,mt8167-mmsys",
> + .data = &mt8167_mmsys_driver_data,
> + },
> {
> .compatible = "mediatek,mt8173-mmsys",
> .data = &mt8173_mmsys_driver_data,
>
_______________________________________________
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:[~2021-03-30 9:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 16:06 [PATCH 1/2] dt-bindings: mediatek: mmsys: add mt1867 binding Fabien Parent
2020-10-27 16:06 ` [PATCH 2/2] soc: mediatek: mmsys: Add support for MT8167 SoC Fabien Parent
2021-03-30 9:15 ` Matthias Brugger [this message]
2020-10-27 23:38 ` [PATCH 1/2] dt-bindings: mediatek: mmsys: add mt1867 binding Chun-Kuang Hu
2020-10-30 19:17 ` Rob Herring
2021-01-09 23:17 ` Chun-Kuang Hu
2021-02-23 22:21 ` Fabien Parent
2021-03-18 0:41 ` Chun-Kuang Hu
2021-04-06 14:11 ` Matthias Brugger
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=052990a7-673f-31f4-2453-a84b007cdbcf@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=fparent@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.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).