zephyrproject-rtos/zephyr

Bluetooth, host: API to expose local controller version & manufacturer info to application

Open

#41,754 opened on Jan 12, 2022

View on GitHub
 (3 comments) (0 reactions) (1 assignee)C (9,144 forks)batch import
EnhancementGood first issuearea: APIarea: Bluetootharea: Bluetooth Host

Repository metrics

Stars
 (15,249 stars)
PR merge metrics
 (Avg merge 4d 21h) (1,000 merged PRs in 30d)

Description

Now one can print local controller and HCI info using BT_INFO, originating from https://github.com/zephyrproject-rtos/zephyr/blob/45a693a2a92412c8677cae9c3111bb4369272f42/subsys/bluetooth/host/hci_core.c#L3081

This is good, but it is desirable to have this information available to the application trough an API. Something similar to bt_dev_get_info() which returns bt_dev as a pointer, or it could be more specific, returning one of the

hci_version;
lmp_version;
hci_revision;
lmp_subversion;
manufacturer;

Parameters.

Contributor guide

Research direction
Implement a new function, e.g., bt dev get info(), that returns a struct containing hci version, lmp version, hci revision, lmp subversion, and manufacturer. Use existing BT INFO print logic to access the stored values in bt dev. Ensure the function is accessible from application code.
Tech stack
c
Domain
infrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65