Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp4376010ybg; Tue, 29 Oct 2019 06:18:02 -0700 (PDT) X-Google-Smtp-Source: APXvYqytXyoWjf6+nS65gtYxJOL3tZ6NUWtQQFmHW6IRrJ7KuzQWuKr5TJPrRoAkJ3zvHWrvcNyP X-Received: by 2002:a50:c2c2:: with SMTP id u2mr25949278edf.133.1572355082612; Tue, 29 Oct 2019 06:18:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1572355082; cv=none; d=google.com; s=arc-20160816; b=Kz9biEpI9S31+aiiYzqaAyO5mVfi5Jt5/lvNJ7DZmrdmTGvLXKQjUVFICA2OumKHly ioHFU3sh/gQF6BtxlS4yTpbqtJOya+mJLiiHTWZFaqTy9EH2RqNXxJN3TkR6WJ4BW41z WNuii5797WY7BN8HnFklaNQV/gvK7wu7QFLhL4dkHEqrJ7Qw9t5rb23vfB7u9iim9XFW 5sCsE00keXFJTb80k7drhpGfGf+7g+iyEeG4QVYz5prVpgov4bThUVsda3zipQfY/4VW fEwZ5ATZrrJTWO1dCh978LpUNCjHnYHjcRzjoTiOywt6C0o/WuqILkjETLl/aAZLKkw5 o3vA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=Ecq5l3NGTkSNMMtdvtGS8c5Oc1a8hh41Azf6zC4hq04=; b=Hik66ClL1QOoAAMRriOdPZWFF6uaBfRxnYsxYx2l133SC2mCaoE2tdSgpIKa0pW0o3 VXd9Ud2AU3/OTNQWkAdbgRP76i/TcBPFzskJG4Fr8CRoVXJBb5T5LTOKNcSCpyoIkchP bWutqIWCV+LDuWGzEwd4nUMA4oQBnBLiwQRxnmCf7uaocj+UL91QyfvW6kW2Inm//Gkt 2grG77wCa9iTDOJmwLaKObUfeYJ6ak5EGr960CYVuNSDwEIduGm5jGt0fi+8d7WXKApB uDLTzxg0RxpLsn3P0Ib1lhZ7DCBo0NK0ToadwvirT85cD52ck8t2gON4LCR9G/xVD3QO 8vaQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=RVM+eRIA; spf=pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q26si8341607ejz.43.2019.10.29.06.17.25; Tue, 29 Oct 2019 06:18:02 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=RVM+eRIA; spf=pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388324AbfJ2NQo (ORCPT + 99 others); Tue, 29 Oct 2019 09:16:44 -0400 Received: from mail-ot1-f67.google.com ([209.85.210.67]:36692 "EHLO mail-ot1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388322AbfJ2NQo (ORCPT ); Tue, 29 Oct 2019 09:16:44 -0400 Received: by mail-ot1-f67.google.com with SMTP id c7so9701817otm.3 for ; Tue, 29 Oct 2019 06:16:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Ecq5l3NGTkSNMMtdvtGS8c5Oc1a8hh41Azf6zC4hq04=; b=RVM+eRIAVbrIfLi2NPuJ6Lm5RXXve66zj+8YhcUBxbB7RFinn6OCx9OQ5bmpJrLN3H hWi7Wx6QR/cy+YFkP7yXhr2aah/MWEAv5ZVdnWZU3fcpeZBHdTtfgdmaaIRVNFGCWtNO gAk5Q9tplHV+i6d4NCRXRPFa7trGE2xFJEtwG0/P6517uSIDHI0/HXAHvIHz3pEcwAhi 32259jLlVXPFiX8sCTzTkI2wIgoseiLWkkDpsYwWE9n5cLwEhaNSvYZqsuOxTaiCzKy2 VDMW0ToobApis3jCGRAHT3J/Sq6fCZ+Pa5ymPSMZV//rH4Z4SLjgIV3OPls6U2gUCsJC YTVg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Ecq5l3NGTkSNMMtdvtGS8c5Oc1a8hh41Azf6zC4hq04=; b=aHti47sFM5VxGaI27aDoq8nbpXf3x2imxnxOQLtA18ULy6QRYLLdobtGMT6PCkcF5+ nQ5I6r5dbEXwnozxfV7uffnft4pKw71Zpz7kx/wO6GaBvXvwqZbm6IV+67aQ0RhWn/rT 2f/0x41qjKwBUpbXg9WIWW6feqfMCZ3ZQQc3X5mRL491qq/O17ZW3uY2GjMnUuwBdsjU VUYjVARFFIilBXBBNVpcIK2K132VtrHtUSA15DmL9aGawX2/bTIeviKVi0TPG6r+FrN4 zdG3VvFjaVyebnBxav0zyCptE9QFLBun42sD4lu4LRjyQUxIVKvYM0Vct5KiNUsCZlEQ rRrg== X-Gm-Message-State: APjAAAXVEJctC2MMgE9qduBpQ42KGBXc3BgfpyhqMbviBncuZrFAXhry nOuKU0j87j3IKRRGk3b1gmlbjFLMH4qAwjTAPxWDR+igfes= X-Received: by 2002:a9d:620c:: with SMTP id g12mr8384234otj.11.1572355003359; Tue, 29 Oct 2019 06:16:43 -0700 (PDT) MIME-Version: 1.0 References: <1571913139-6477-1-git-send-email-jaganath.kanakkassery@intel.com> <585F2A10-B16E-46BD-8EF6-4FD904A485AC@holtmann.org> <368BD38D-6FFB-412D-A6A9-364B3B5374F0@holtmann.org> In-Reply-To: From: Luiz Augusto von Dentz Date: Tue, 29 Oct 2019 15:16:30 +0200 Message-ID: Subject: Re: [PATCH] Bluetooth: Always set scannable for Adv instance 0 To: Jaganath K Cc: Marcel Holtmann , "open list:BLUETOOTH DRIVERS" , Jaganath Kanakkassery Content-Type: text/plain; charset="UTF-8" Sender: linux-bluetooth-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org Hi Jaganath, On Mon, Oct 28, 2019 at 6:50 PM Jaganath K wrote: > > Hi Marcel, > > On Sat, Oct 26, 2019 at 11:02 AM Marcel Holtmann wrote: > > > > Hi Jaganath, > > > > >>> By default for instance 0, local name will be added for scan rsp > > >>> data, but currently the property is set as non scannable and hence > > >>> Set Adv parameter fails with Invalid parameter. > > >> > > >> can you be a bit more specific why this is the correct behavior. We must have documented in mgmt-api.txt somewhere, right? Or is this something that used to be correct, but we broke it with adding extended advertising? > > > > > > It seems to be functionally broken in legacy adv as well as we set scan rsp > > > for instance 0 always but Adv Properties is set to non connectable (if > > > connectable > > > is not set). Even we need to fix mgmt-api.txt as well as you pointed out. > > > > > > But in legacy case commands do not fail as scan rsp can be set even before > > > Set Adv Param where as in extended case Adv param for an Adv set has to be set > > > first before sending Scan rsp and other commands for that particular Adv set. > > > > how does this intersect with the patches that Luiz was sending earlier? > > > I think Luiz patches covers both the issues. Yep, my patches were actually targeting the same issues, though you had a better description, anyway it is a fix nevertheless. -- Luiz Augusto von Dentz