From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: sean.wang@mediatek.com, marcel@holtmann.org,
johan.hedberg@gmail.com, luiz.dentz@gmail.com
Cc: Soul.Huang@mediatek.com, YN.Chen@mediatek.com,
Leon.Yen@mediatek.com, Eric-SY.Chang@mediatek.com,
Deren.Wu@mediatek.com, km.lin@mediatek.com,
robin.chiu@mediatek.com, Eddie.Chen@mediatek.com,
ch.yeh@mediatek.com, posh.sun@mediatek.com,
ted.huang@mediatek.com, Stella.Chang@mediatek.com,
Tom.Chou@mediatek.com, steve.lee@mediatek.com, jsiuda@google.com,
frankgor@google.com, abhishekpandit@google.com,
michaelfsun@google.com, abhishekpandit@chromium.org,
mcchou@chromium.org, shawnku@google.com,
linux-bluetooth@vger.kernel.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] Bluetooth: btusb: mediatek: use readx_poll_timeout instead of open coding
Date: Tue, 13 Sep 2022 09:47:47 +0200 [thread overview]
Message-ID: <8c734b83-aa2a-83a6-cb12-28e36ace2bbb@collabora.com> (raw)
In-Reply-To: <43b68b1f48c20b1dfcd7e6663c3dcb38e4e0648c.1663020936.git.objelf@gmail.com>
Il 13/09/22 00:18, sean.wang@mediatek.com ha scritto:
> From: Sean Wang <sean.wang@mediatek.com>
>
> Use readx_poll_timeout instead of open coding to poll the hardware reset
> status until it is done.
>
> Signed-off-by: Sean Wang <sean.wang@mediatek.com>
Hello Sean, thanks for the patch!
However, there's something to improve...
> ---
> drivers/bluetooth/btusb.c | 32 ++++++++++++++++++--------------
> 1 file changed, 18 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
> index c3daba17de7f..4dc9cae3e937 100644
> --- a/drivers/bluetooth/btusb.c
> +++ b/drivers/bluetooth/btusb.c
..snip..
> @@ -2910,18 +2918,14 @@ static void btusb_mtk_cmd_timeout(struct hci_dev *hdev)
> btusb_mtk_uhw_reg_write(data, MTK_BT_SUBSYS_RST, 0);
> btusb_mtk_uhw_reg_read(data, MTK_BT_SUBSYS_RST, &val);
>
> - /* Poll the register until reset is completed */
> - do {
> - btusb_mtk_uhw_reg_read(data, MTK_BT_MISC, &val);
> - if (val & MTK_BT_RST_DONE) {
> - bt_dev_dbg(hdev, "Bluetooth Reset Successfully");
> - break;
> - }
> + err = readx_poll_timeout(btusb_mtk_reset_done, hdev, val,
> + val & MTK_BT_RST_DONE,
> + 100000, 1000000);
I agree with using readx_poll_timeout() instead of open coding the same, but
there's a catch: this macro uses usleep_range(), which is meant to be used
for sleeping less than ~20ms.
Even the kerneldoc at include/linux/iopoll.h advertises that:
* @sleep_us: Maximum time to sleep between reads in us (0
* tight-loops). Should be less than ~20ms since usleep_range
* is used (see Documentation/timers/timers-howto.rst).
So, if there's any reason for which you can't sleep for less than 100ms
per iteration, I'm afraid that you can't use readx_poll_timeout()...
...otherwise, please change sleep_us to 20000 and keep the timeout at 1 sec.
Regards,
Angelo
> + if (err < 0)
> + bt_dev_err(hdev, "Reset timeout");
>
> - bt_dev_dbg(hdev, "Polling Bluetooth Reset CR");
> - retry++;
> - msleep(MTK_BT_RESET_WAIT_MS);
> - } while (retry < MTK_BT_RESET_NUM_TRIES);
> + if (val & MTK_BT_RST_DONE)
> + bt_dev_dbg(hdev, "Bluetooth Reset Successfully");
>
> btusb_mtk_id_get(data, 0x70010200, &val);
> if (!val)
next prev parent reply other threads:[~2022-09-13 7:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 22:18 [PATCH 1/4] Bluetooth: btusb: mediatek: use readx_poll_timeout instead of open coding sean.wang
2022-09-12 22:18 ` [PATCH 2/4] Bluetooth: btmtk: introduce btmtk reset work sean.wang
2022-09-12 22:18 ` [PATCH 3/4] Bluetooth: btusb: mediatek: reset the device as WMT failed sean.wang
2022-09-13 7:49 ` AngeloGioacchino Del Regno
2022-09-14 22:34 ` Sean Wang
2022-09-14 22:45 ` Luiz Augusto von Dentz
2022-09-15 1:57 ` Sean Wang
2022-09-12 22:18 ` [PATCH 4/4] Bluetooth: btusb: mediatek: add MediaTek devcoredump support sean.wang
2022-09-13 6:29 ` kernel test robot
2022-09-13 10:56 ` kernel test robot
2022-09-13 10:56 ` kernel test robot
2022-09-12 23:10 ` [1/4] Bluetooth: btusb: mediatek: use readx_poll_timeout instead of open coding bluez.test.bot
2022-09-13 7:47 ` AngeloGioacchino Del Regno [this message]
2022-09-14 22:59 ` [PATCH 1/4] " Sean 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=8c734b83-aa2a-83a6-cb12-28e36ace2bbb@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=Deren.Wu@mediatek.com \
--cc=Eddie.Chen@mediatek.com \
--cc=Eric-SY.Chang@mediatek.com \
--cc=Leon.Yen@mediatek.com \
--cc=Soul.Huang@mediatek.com \
--cc=Stella.Chang@mediatek.com \
--cc=Tom.Chou@mediatek.com \
--cc=YN.Chen@mediatek.com \
--cc=abhishekpandit@chromium.org \
--cc=abhishekpandit@google.com \
--cc=ch.yeh@mediatek.com \
--cc=frankgor@google.com \
--cc=johan.hedberg@gmail.com \
--cc=jsiuda@google.com \
--cc=km.lin@mediatek.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mcchou@chromium.org \
--cc=michaelfsun@google.com \
--cc=posh.sun@mediatek.com \
--cc=robin.chiu@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shawnku@google.com \
--cc=steve.lee@mediatek.com \
--cc=ted.huang@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