From: patchwork-bot+bluetooth@kernel.org
To: Prathibha Madugonde <prathibha.madugonde@oss.qualcomm.com>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
quic_mohamull@quicinc.com, quic_hbandi@quicinc.com,
quic_anubhavg@quicinc.com
Subject: Re: [PATCH BlueZ v3] monitor: Parsing of cs step mode data in RAS Notifications
Date: Fri, 08 May 2026 19:20:04 +0000 [thread overview]
Message-ID: <177826800480.815206.7081384699011433194.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260508053819.3424918-1-prathm@qti.qualcomm.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 8 May 2026 11:08:19 +0530 you wrote:
> From: Prathibha Madugonde <prathibha.madugonde@oss.qualcomm.com>
>
> Sample Decoding Example:
> Subevent #0:
> Start ACL Connection Event: 406
> Frequency Compensation: -16384 (0.01 ppm)
> Ranging Done Status: Partial results, more to follow (0x1)
> Subevent Done Status: All results complete (0x0)
> Ranging Abort Reason: No abort (0x0)
> Subevent Abort Reason: No abort (0x0)
> Reference Power Level: -14 dBm
> Number of Steps Reported: 58
> Step 0
> Mode Type: 0
> Aborted: No
> Packet Quality: 0x00
> CS Access Address check is successful
> Bit errors: 0
> Packet RSSI: -52
> Packet Antenna: 1
> Step 1
> Mode Type: 0
> Aborted: No
> Packet Quality: 0x00
> CS Access Address check is successful
> Bit errors: 0
> Packet RSSI: -48
> Packet Antenna: 1
> Step 2
> Mode Type: 1
> Aborted: No
> Packet Quality: 0x00
> CS Access Address check is successful
> Bit errors: 0
> Packet NADM: Unknown NADM (0xff)
> Packet RSSI: -60
> ToA_ToD: 0xffffff45
> Packet Antenna: 1
> Step 3
> Mode Type: 1
> Aborted: No
> Packet Quality: 0x00
> CS Access Address check is successful
> Bit errors: 0
> Packet NADM: Unknown NADM (0xff)
> Packet RSSI: -54
> ToA_ToD: 0xffffff53
> Packet Antenna: 1
>
> [...]
Here is the summary with links:
- [BlueZ,v3] monitor: Parsing of cs step mode data in RAS Notifications
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=7cd27f4f66aa
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-05-08 19:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 5:38 [PATCH BlueZ v3] monitor: Parsing of cs step mode data in RAS Notifications Prathibha Madugonde
2026-05-08 7:09 ` [BlueZ,v3] " bluez.test.bot
2026-05-08 19:20 ` patchwork-bot+bluetooth [this message]
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=177826800480.815206.7081384699011433194.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=prathibha.madugonde@oss.qualcomm.com \
--cc=quic_anubhavg@quicinc.com \
--cc=quic_hbandi@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