From: Nancy.Lin <nancy.lin@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Chun-Kuang Hu <chunkuang.hu@kernel.org>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
<wim@linux-watchdog.org>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>, <linux@roeck-us.net>,
<nfraprado@collabora.com>
Cc: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
"Nathan Chancellor" <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
"jason-jh . lin" <jason-jh.lin@mediatek.com>,
Yongqiang Niu <yongqiang.niu@mediatek.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<dri-devel@lists.freedesktop.org>, <llvm@lists.linux.dev>,
<singo.chang@mediatek.com>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: Re: [PATCH v26 07/10] soc: mediatek: mmsys: add mmsys for support 64 reset bits
Date: Tue, 23 Aug 2022 19:30:01 +0800 [thread overview]
Message-ID: <140b3cd10317a5db781df180ce4efb697cdd641b.camel@mediatek.com> (raw)
In-Reply-To: <44c86ad9-8158-0a8a-ce31-a995c8d10e0b@gmail.com>
Hi Matthias,
Thanks for the review.
On Tue, 2022-08-23 at 12:20 +0200, Matthias Brugger wrote:
>
> On 19/08/2022 08:10, Nancy.Lin wrote:
> > Add mmsys for support 64 reset bits. It is a preparation for MT8195
> > vdosys1 HW reset. MT8195 vdosys1 has more than 32 reset bits.
> >
> > 1. Add the number of reset bits in mmsys private data
> > 2. move the whole "reset register code section" behind the
> > "get mmsys->data" code section for getting the num_resets in mmsys-
> > >data.
> >
> > Signed-off-by: Nancy.Lin <nancy.lin@mediatek.com>
> > Reviewed-by: AngeloGioacchino Del Regno <
> > angelogioacchino.delregno@collabora.com>
> > Reviewed-by: CK Hu <ck.hu@mediatek.com>
> > Tested-by: Bo-Chen Chen <rex-bc.chen@mediatek.com>
> > ---
> > drivers/soc/mediatek/mtk-mmsys.c | 40 +++++++++++++++++++++----
> > -------
> > drivers/soc/mediatek/mtk-mmsys.h | 1 +
> > 2 files changed, 27 insertions(+), 14 deletions(-)
> >
> > diff --git a/drivers/soc/mediatek/mtk-mmsys.c
> > b/drivers/soc/mediatek/mtk-mmsys.c
> > index 999be064103b..20ae751ad8a7 100644
> > --- a/drivers/soc/mediatek/mtk-mmsys.c
> > +++ b/drivers/soc/mediatek/mtk-mmsys.c
> > @@ -20,6 +20,8 @@
> > #include "mt8195-mmsys.h"
> > #include "mt8365-mmsys.h"
> >
> > +#define MMSYS_SW_RESET_PER_REG 32
> > +
> > static const struct mtk_mmsys_driver_data
> > mt2701_mmsys_driver_data = {
> > .clk_driver = "clk-mt2701-mm",
> > .routes = mmsys_default_routing_table,
> > @@ -86,6 +88,7 @@ static const struct mtk_mmsys_driver_data
> > mt8173_mmsys_driver_data = {
> > .routes = mmsys_default_routing_table,
> > .num_routes = ARRAY_SIZE(mmsys_default_routing_table),
> > .sw0_rst_offset = MT8183_MMSYS_SW0_RST_B,
> > + .num_resets = 32,
> > };
> >
> > static const struct mtk_mmsys_match_data mt8173_mmsys_match_data
> > = {
> > @@ -100,6 +103,7 @@ static const struct mtk_mmsys_driver_data
> > mt8183_mmsys_driver_data = {
> > .routes = mmsys_mt8183_routing_table,
> > .num_routes = ARRAY_SIZE(mmsys_mt8183_routing_table),
> > .sw0_rst_offset = MT8183_MMSYS_SW0_RST_B,
> > + .num_resets = 32,
> > };
> >
> > static const struct mtk_mmsys_match_data mt8183_mmsys_match_data
> > = {
> > @@ -114,6 +118,7 @@ static const struct mtk_mmsys_driver_data
> > mt8186_mmsys_driver_data = {
> > .routes = mmsys_mt8186_routing_table,
> > .num_routes = ARRAY_SIZE(mmsys_mt8186_routing_table),
> > .sw0_rst_offset = MT8186_MMSYS_SW0_RST_B,
> > + .num_resets = 32,
> > };
> >
> > static const struct mtk_mmsys_match_data mt8186_mmsys_match_data
> > = {
> > @@ -128,6 +133,7 @@ static const struct mtk_mmsys_driver_data
> > mt8192_mmsys_driver_data = {
> > .routes = mmsys_mt8192_routing_table,
> > .num_routes = ARRAY_SIZE(mmsys_mt8192_routing_table),
> > .sw0_rst_offset = MT8186_MMSYS_SW0_RST_B,
> > + .num_resets = 32,
>
> You didn't reply to Nicolas regarding the reset numbers. I actually
> agree with
> him that we will need the num_resets declared for all devices. Why do
> you think
> this is not the case?
>
> Regards,
> Matthias
>
Sorry, I lost Nicolas's email.
I checked with the mmsys git log with reset controller function.
1. Enric add mmsys reset controller function in [1]/[2].
=> in mtk_mmsys_reset_update(), all mmsys reset offset is
MMSYS_SW0_RST_B (0x140).
2. After Enric's patch, Rex add sw0_rst_offset in mmsys driver data in
[3].
So, I think sw0_rst_offset is not zero. Instead of only add num_resets
but also need to add sw0_rst_offset for all mmsys. What do you think ?
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/soc/mediatek/mtk-mmsys.c?id=f27ef2856343e2ddc392975d7b15120442e4d7b7
[2]
https://patchwork.kernel.org/project/linux-mediatek/cover/20210825102632.601614-1-enric.balletbo@collabora.com/
[3]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/soc/mediatek/mtk-mmsys.c?id=62dc30150c06774a8122c52aedd0eddaceaf5940
Regards,
Nancy
>
> > };
> >
> > static const struct mtk_mmsys_match_data mt8192_mmsys_match_data
> > = {
> > @@ -288,13 +294,19 @@ static int mtk_mmsys_reset_update(struct
> > reset_controller_dev *rcdev, unsigned l
> > {
> > struct mtk_mmsys *mmsys = container_of(rcdev, struct mtk_mmsys,
> > rcdev);
> > unsigned long flags;
> > + u32 offset;
> > + u32 reg;
> > +
> > + offset = (id / MMSYS_SW_RESET_PER_REG) * sizeof(u32);
> > + id = id % MMSYS_SW_RESET_PER_REG;
> > + reg = mmsys->data->sw0_rst_offset + offset;
> >
> > spin_lock_irqsave(&mmsys->lock, flags);
> >
> > if (assert)
> > - mtk_mmsys_update_bits(mmsys, mmsys->data-
> > >sw0_rst_offset, BIT(id), 0, NULL);
> > + mtk_mmsys_update_bits(mmsys, reg, BIT(id), 0, NULL);
> > else
> > - mtk_mmsys_update_bits(mmsys, mmsys->data-
> > >sw0_rst_offset, BIT(id), BIT(id), NULL);
> > + mtk_mmsys_update_bits(mmsys, reg, BIT(id), BIT(id),
> > NULL);
> >
> > spin_unlock_irqrestore(&mmsys->lock, flags);
> >
> > @@ -351,18 +363,6 @@ static int mtk_mmsys_probe(struct
> > platform_device *pdev)
> > return ret;
> > }
> >
> > - spin_lock_init(&mmsys->lock);
> > -
> > - mmsys->rcdev.owner = THIS_MODULE;
> > - mmsys->rcdev.nr_resets = 32;
> > - mmsys->rcdev.ops = &mtk_mmsys_reset_ops;
> > - mmsys->rcdev.of_node = pdev->dev.of_node;
> > - ret = devm_reset_controller_register(&pdev->dev, &mmsys-
> > >rcdev);
> > - if (ret) {
> > - dev_err(&pdev->dev, "Couldn't register mmsys reset
> > controller: %d\n", ret);
> > - return ret;
> > - }
> > -
> > res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> > if (!res) {
> > dev_err(dev, "Couldn't get mmsys resource\n");
> > @@ -384,6 +384,18 @@ static int mtk_mmsys_probe(struct
> > platform_device *pdev)
> > mmsys->data = match_data->drv_data[0];
> > }
> >
> > + spin_lock_init(&mmsys->lock);
> > +
> > + mmsys->rcdev.owner = THIS_MODULE;
> > + mmsys->rcdev.nr_resets = mmsys->data->num_resets;
> > + mmsys->rcdev.ops = &mtk_mmsys_reset_ops;
> > + mmsys->rcdev.of_node = pdev->dev.of_node;
> > + ret = devm_reset_controller_register(&pdev->dev, &mmsys-
> > >rcdev);
> > + if (ret) {
> > + dev_err(&pdev->dev, "Couldn't register mmsys reset
> > controller: %d\n", ret);
> > + return ret;
> > + }
> > +
> > #if IS_REACHABLE(CONFIG_MTK_CMDQ)
> > ret = cmdq_dev_get_client_reg(dev, &mmsys->cmdq_base, 0);
> > if (ret)
> > diff --git a/drivers/soc/mediatek/mtk-mmsys.h
> > b/drivers/soc/mediatek/mtk-mmsys.h
> > index f01ba206481d..20a271b80b3b 100644
> > --- a/drivers/soc/mediatek/mtk-mmsys.h
> > +++ b/drivers/soc/mediatek/mtk-mmsys.h
> > @@ -92,6 +92,7 @@ struct mtk_mmsys_driver_data {
> > const struct mtk_mmsys_routes *routes;
> > const unsigned int num_routes;
> > const u16 sw0_rst_offset;
> > + const u32 num_resets;
> > };
> >
> > struct mtk_mmsys_match_data {
>
>
next prev parent reply other threads:[~2022-08-23 11:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 6:10 [PATCH v26 00/10] Add MediaTek SoC(vdosys1) support for mt8195 Nancy.Lin
2022-08-19 6:10 ` [PATCH v26 01/10] dt-bindings: reset: mt8195: add vdosys1 reset control bit Nancy.Lin
2022-08-19 6:10 ` [PATCH v26 02/10] soc: mediatek: add mtk-mmsys ethdr and mdp_rdma components Nancy.Lin
2022-08-19 6:10 ` [PATCH v26 03/10] soc: mediatek: add mtk-mmsys support for mt8195 vdosys1 Nancy.Lin
2022-08-19 6:10 ` [PATCH v26 04/10] soc: mediatek: add mtk_mmsys_update_bits API Nancy.Lin
2022-08-19 6:10 ` [PATCH v26 05/10] soc: mediatek: add mtk-mmsys config API for mt8195 vdosys1 Nancy.Lin
2022-08-19 6:10 ` [PATCH v26 06/10] soc: mediatek: add cmdq support of " Nancy.Lin
2022-08-19 6:10 ` [PATCH v26 07/10] soc: mediatek: mmsys: add mmsys for support 64 reset bits Nancy.Lin
2022-08-23 10:20 ` Matthias Brugger
2022-08-23 11:30 ` Nancy.Lin [this message]
2022-08-23 12:08 ` Matthias Brugger
2022-08-24 2:44 ` Nancy.Lin
2022-08-24 11:41 ` Matthias Brugger
2022-08-25 2:19 ` Nancy.Lin
2022-08-19 6:10 ` [PATCH v26 08/10] soc: mediatek: mmsys: add reset control for MT8195 vdosys1 Nancy.Lin
2022-08-19 6:10 ` [PATCH v26 09/10] soc: mediatek: add mtk-mutex component - dp_intf1 Nancy.Lin
2022-08-19 6:10 ` [PATCH v26 10/10] soc: mediatek: add mtk-mutex support for mt8195 vdosys1 Nancy.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=140b3cd10317a5db781df180ce4efb697cdd641b.camel@mediatek.com \
--to=nancy.lin@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=airlied@linux.ie \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.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@roeck-us.net \
--cc=llvm@lists.linux.dev \
--cc=matthias.bgg@gmail.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nfraprado@collabora.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=singo.chang@mediatek.com \
--cc=wim@linux-watchdog.org \
--cc=yongqiang.niu@mediatek.com \
/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