Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Feedback-ID: i01794759:Fastmail
User-Agent: Cyrus-JMAP/3.9.0-alpha0-238-g746678b8b6-fm-20230329.001-g746678b8
Mime-Version: 1.0
Message-Id: <126c5bce-6496-4744-9101-6a61f0fff106@app.fastmail.com>
In-Reply-To: <CACk7upyDgd8kCY+8j+RMJz35GXrF=bwRzDNH76Oh8q4nB8i0KQ@mail.gmail.com>
References: <CACk7upyDgd8kCY+8j+RMJz35GXrF=bwRzDNH76Oh8q4nB8i0KQ@mail.gmail.com>
Date:   Thu, 30 Mar 2023 22:50:02 -0700
From:   "Christopher Snowhill" <chris@kode54.net>
To:     "Raul Cheleguini" <raul.cheleguini@gmail.com>,
        linux-bluetooth@vger.kernel.org
Cc:     "Marcel Holtmann" <marcel@holtmann.org>, johan.hedberg@gmail.com,
        luiz.dentz@gmail.com
Subject: Re: unexpected SMP command errors with controller ATS2851
Content-Type: text/plain
Precedence: bulk

Would some pcapng logs be useful? It appears this device flags some commands as supported, while indicating their entire feature sets are not supported in the local supported features bitfields. Or that's as near as I can guess.

First is captured from a generic driver that works, the latter is captured from Linux 6.2.9. Included in the working capture is the beginning of an exchange with my Sony headphones. The latter stops logging after the first failed command.

https://f.losno.co/bluetooth_ats2851.pcapng.zst
https://f.losno.co/bluetooth_ats2851_broken.pcapng.zst