From: Bart Van Assche <bvanassche@acm.org>
To: peter.wang@mediatek.com, stanley.chu@mediatek.com,
linux-scsi@vger.kernel.org, martin.petersen@oracle.com,
avri.altman@wdc.com, alim.akhtar@samsung.com, jejb@linux.ibm.com
Cc: wsd_upstream@mediatek.com, linux-mediatek@lists.infradead.org,
chun-hung.wu@mediatek.com, alice.chao@mediatek.com,
cc.chou@mediatek.com, chaotian.jing@mediatek.com,
jiajie.hao@mediatek.com, powen.kao@mediatek.com,
qilin.tan@mediatek.com, lin.gui@mediatek.com
Subject: Re: [PATCH v1] ufs: core: fix lockdep warning of clk_scaling_lock
Date: Fri, 22 Jul 2022 14:00:09 -0700 [thread overview]
Message-ID: <c9138aae-db78-7163-e207-3fb134db226c@acm.org> (raw)
In-Reply-To: <20220722095308.10112-1-peter.wang@mediatek.com>
On 7/22/22 02:53, peter.wang@mediatek.com wrote:
> This patch only release write lock of clk_scaling_lock before
> ufshcd_wb_toggle.
The above is not clear to me. Please make the above more clear.
Additionally, patches must be signed before these can be merged
upstream. Where is your Signed-off-by?
> - /* Enable Write Booster if we have scaled up else disable it */
> - downgrade_write(&hba->clk_scaling_lock);
> - is_writelock = false;
> - ufshcd_wb_toggle(hba, scale_up);
> + wb_toggle = true;
>
> out_unprepare:
> - ufshcd_clock_scaling_unprepare(hba, is_writelock);
> + ufshcd_clock_scaling_unprepare(hba);
> +
> + /* Enable Write Booster if we have scaled up else disable it */
> + if (wb_toggle)
> + ufshcd_wb_toggle(hba, scale_up);
> +
> return ret;
> }
The patch description should mention that this patch changes the
ufshcd_wb_toggle() call: before this patch clk_scaling_lock was held in
reader mode during the ufshcd_wb_toggle() call and with this patch
applied clk_scaling_lock is not held while ufshcd_wb_toggle() is called.
I'm missing an explanation of why this change is safe.
Thanks,
Bart.
next prev parent reply other threads:[~2022-07-22 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 9:53 [PATCH v1] ufs: core: fix lockdep warning of clk_scaling_lock peter.wang
2022-07-22 21:00 ` Bart Van Assche [this message]
2022-07-25 3:56 ` Peter Wang
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=c9138aae-db78-7163-e207-3fb134db226c@acm.org \
--to=bvanassche@acm.org \
--cc=alice.chao@mediatek.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=cc.chou@mediatek.com \
--cc=chaotian.jing@mediatek.com \
--cc=chun-hung.wu@mediatek.com \
--cc=jejb@linux.ibm.com \
--cc=jiajie.hao@mediatek.com \
--cc=lin.gui@mediatek.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=peter.wang@mediatek.com \
--cc=powen.kao@mediatek.com \
--cc=qilin.tan@mediatek.com \
--cc=stanley.chu@mediatek.com \
--cc=wsd_upstream@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