mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Janaki Ramaiah Thota <quic_janathot@quicinc.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	quic_mohamull@quicinc.com, quic_hbandi@quicinc.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] Bluetooth: hci_qca: Increase settling time for baudrate change VSC
Date: Mon, 17 Jun 2024 09:14:39 +0200	[thread overview]
Message-ID: <80ca0fd6-b666-4e84-a3eb-d3f6d9bfdc05@molgen.mpg.de> (raw)
In-Reply-To: <20240617070039.30824-1-quic_janathot@quicinc.com>

Dear Janaki,


Thank you for your patch. Please be more specific in the summary/title:

> Increase settling time for baudrate change VSC to 30 ms


Am 17.06.24 um 09:00 schrieb Janaki Ramaiah Thota:
> This change is done to align the settling time and
> synchronization for baudrate VSC for WCN6750.
> 
> In logging disabled builds and few devices
> baudrate change and flow control is taking time
> so increasing the wait time to controller and uart
> to handle baudrate change request properly.

Is the 30 ms documented in some datasheet?

Please use 75 characters per line.

Please document the test system.

> Signed-off-by: Janaki Ramaiah Thota <quic_janathot@quicinc.com>
> ---
>   drivers/bluetooth/hci_qca.c | 5 ++++-
>   1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/bluetooth/hci_qca.c b/drivers/bluetooth/hci_qca.c
> index 0c9c9ee56592..667687835306 100644
> --- a/drivers/bluetooth/hci_qca.c
> +++ b/drivers/bluetooth/hci_qca.c
> @@ -1356,12 +1356,15 @@ static int qca_set_baudrate(struct hci_dev *hdev, uint8_t baudrate)
>   	case QCA_WCN3990:
>   	case QCA_WCN3991:
>   	case QCA_WCN3998:
> -	case QCA_WCN6750:
>   	case QCA_WCN6855:
>   	case QCA_WCN7850:
>   		usleep_range(1000, 10000);
>   		break;
>   
> +	case QCA_WCN6750:
> +		msleep(30);

Why not usleep_range?

> +		break;
> +
>   	default:
>   		msleep(300);
>   	}


Kind regards,

Paul

  reply	other threads:[~2024-06-17  7:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-17  7:00 Janaki Ramaiah Thota
2024-06-17  7:14 ` Paul Menzel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-03 12:53 [PATCH] PENDING: Bluetooth: " Janaki Ramaiah Thota
2024-06-03 12:53 ` [PATCH v1] Bluetooth: hci_qca: " Janaki Ramaiah Thota

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=80ca0fd6-b666-4e84-a3eb-d3f6d9bfdc05@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=quic_hbandi@quicinc.com \
    --cc=quic_janathot@quicinc.com \
    --cc=quic_mohamull@quicinc.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®