From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2B43EC43381 for ; Wed, 27 Feb 2019 20:35:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id EDBAF20818 for ; Wed, 27 Feb 2019 20:35:57 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="PfNeTMDq" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729412AbfB0Uf5 (ORCPT ); Wed, 27 Feb 2019 15:35:57 -0500 Received: from mail-pf1-f194.google.com ([209.85.210.194]:45743 "EHLO mail-pf1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728397AbfB0Uf5 (ORCPT ); Wed, 27 Feb 2019 15:35:57 -0500 Received: by mail-pf1-f194.google.com with SMTP id v21so8539871pfm.12 for ; Wed, 27 Feb 2019 12:35:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=GNwThvtjzGpzi0d/OiEgtviNMmvlYQ4OUgMES2ZulRY=; b=PfNeTMDqAOGPJMr+73KPK2ePi0n90oWAeLegQjTvCoRQdh1lkmO/apbcThS5wK72v0 KxJWWFmXUcJEMydS6amkjvWwwNoHh/1pTZDa5qk9CcmuLDWTjmk6hICl97x8L2Cuba4Q UU96qkk+T3wvnxGhOBJrg0VpJkj5VSSyX5F94= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=GNwThvtjzGpzi0d/OiEgtviNMmvlYQ4OUgMES2ZulRY=; b=mA2/nL/M4znDVSQId6rQLtg2n7sOZZpluGXqmjbimXE5HeQgEvzBP7dPp4/lPUrspb hnPy80jDQecwT1nje/FhAp8dF8NXpeYoMBsrVWrpZtSvVGEdyaDOrpykYDth3Mu5Ih9I Eb2oQLUNJNdv9RCZBByuQE9DwPIwibXCF9LPntyyCFhuB1Fai5eKwdX1Ba76dJX/Sw6l imTfBV8ivufNo9530hLQq36a4lBK+zuTeur/bfx5srjV/CmBI4pouMB7tob58RLQQlTj 3bP7jbzN4wCzdXmA1+hoCgK4wd+RizhjfT1UGOm78Sj+kNy+vuRhgVCnjNLR44ma8UgL NmPg== X-Gm-Message-State: AHQUAuY3qepcRruoBiqzbCq0uibIo4BcgBmNRqpp558qOIYIuS+rif37 cQNad8KpOIRimBpFkUrLTgfj8CeVkSE= X-Google-Smtp-Source: AHgI3IYjOI5P9YUp6paCrXzbnJMcUQqt4eH1NHHkkVAA+kvlvmnxeDNZPQ8mDOLiSNpMYw2V3A2oRA== X-Received: by 2002:a63:8b42:: with SMTP id j63mr4678231pge.79.1551299756740; Wed, 27 Feb 2019 12:35:56 -0800 (PST) Received: from localhost ([2620:15c:202:1:75a:3f6e:21d:9374]) by smtp.gmail.com with ESMTPSA id a24sm21495528pfn.85.2019.02.27.12.35.55 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 27 Feb 2019 12:35:56 -0800 (PST) Date: Wed, 27 Feb 2019 12:35:55 -0800 From: Matthias Kaehlcke To: Marcel Holtmann Cc: Johan Hedberg , linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org, Balakrishna Godavarthi , Hemantg Subject: Re: [PATCH 0/2] Reduce delay after sending baudrate request for WCN3990 Message-ID: <20190227203555.GA192510@google.com> References: <20190226200848.154216-1-mka@chromium.org> <45D9EB4B-C81A-4970-9ED1-3737A0AF771F@holtmann.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <45D9EB4B-C81A-4970-9ED1-3737A0AF771F@holtmann.org> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-bluetooth-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org Hi Marcel, On Wed, Feb 27, 2019 at 08:48:31AM +0100, Marcel Holtmann wrote: > Hi Matthias, > > > The current 300ms delay after a baudrate change is extremely long. > > For WCM3990 it is sufficient to wait 10ms after the baudrate change > > request has been sent over the wire. > > > > Also use msleep() instead of a set_current_state() / schedule_timeout() > > combo. > > > > Matthias Kaehlcke (2): > > hci_qca: Use msleep() instead of open coding it > > hci_qca: Reduce delay after sending baudrate request for WCN3990 > > > > drivers/bluetooth/hci_qca.c | 30 +++++++++++++++++++++--------- > > 1 file changed, 21 insertions(+), 9 deletions(-) > > patch 1/2 has been applied to bluetooth-next tree. Thanks! > The patch 2/2 fails to apply. Right, the series "Bluetooth: hci_qca: Add delay after power-off pulse" that was just applied touches the same code. I'll send a rebased version soon. Cheers Matthias