From: "Jason-JH Lin (林睿祥)" <Jason-JH.Lin@mediatek.com>
To: "jassisinghbrar@gmail.com" <jassisinghbrar@gmail.com>,
"CK Hu (胡俊光)" <ck.hu@mediatek.com>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>
Cc: "linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"Singo Chang (張興國)" <Singo.Chang@mediatek.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Nancy Lin (林欣螢)" <Nancy.Lin@mediatek.com>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"jaswinder.singh@linaro.org" <jaswinder.singh@linaro.org>
Subject: Re: [PATCH v2] mailbox: mtk-cmdq: Move devm_mbox_controller_register() after devm_pm_runtime_enable()
Date: Thu, 18 Jul 2024 14:12:58 +0000 [thread overview]
Message-ID: <64f73196293dd86ce2f838b4d76616bcda14bd0e.camel@mediatek.com> (raw)
In-Reply-To: <8fbe44af-8da3-4554-ac2b-5db58003449e@collabora.com>
Hi Angelo,
Thanks for the reviews.
[snip]
> > ---
> > drivers/mailbox/mtk-cmdq-mailbox.c | 14 ++++++++------
> > 1 file changed, 8 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/mailbox/mtk-cmdq-mailbox.c
> > b/drivers/mailbox/mtk-cmdq-mailbox.c
> > index f1dfce9e27f5..002003c3970a 100644
> > --- a/drivers/mailbox/mtk-cmdq-mailbox.c
> > +++ b/drivers/mailbox/mtk-cmdq-mailbox.c
> > @@ -370,6 +370,8 @@ static void cmdq_remove(struct platform_device
> > *pdev)
> > {
> > struct cmdq *cmdq = platform_get_drvdata(pdev);
> >
> > + devm_mbox_controller_unregister(&pdev->dev, &cmdq->mbox);
>
> ...if you moved devm_mbox_controller_register() after
> devm_pm_runtime_enable(),
> this means that the teardown sequence will disable pm runtime after
> unregistering
> the mbox controller, so why do you need to call
> devm_mbox_controller_unregister()
> manually here?
>
Since this is the first time I use b4 --manul-rerell to the v1 path, I
forgot to remove the change in v1.
I'll remove this and send v3 soon.
Regards,
Jason-JH.Lin
> Cheers,
> Angelo
prev parent reply other threads:[~2024-07-18 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 8:38 Jason-JH.Lin via B4 Relay
2024-07-18 10:09 ` AngeloGioacchino Del Regno
2024-07-18 14:12 ` Jason-JH Lin (林睿祥) [this message]
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=64f73196293dd86ce2f838b4d76616bcda14bd0e.camel@mediatek.com \
--to=jason-jh.lin@mediatek.com \
--cc=Nancy.Lin@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=Singo.Chang@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=ck.hu@mediatek.com \
--cc=jassisinghbrar@gmail.com \
--cc=jaswinder.singh@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.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
all inboxes | Powered by JetHome®