Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[PW_SID:918708] Expand firmware-name property to load specific #2624

Open
wants to merge 3 commits into
base: workflow
Choose a base branch
from
Open

[PW_SID:918708] Expand firmware-name property to load specific #2624

wants to merge 3 commits into from

Conversation

BluezTestBot
Copy link
Owner

Expand the firmware-name property to specify the names of NVM and
rampatch firmware to load. This update will support loading specific
firmware (nvm and rampatch) for certain chips, like the QCA6698
Bluetooth chip, which shares the same IP core as the WCN6855 but has
different RF components and RAM sizes, requiring new firmware files.

We might use different connectivity boards on the same platform. For
example, QCA6698-based boards can support either a two-antenna or
three-antenna solution, both of which work on the sa8775p-ride platform.
Due to differences in connectivity boards and variations in RF
performance from different foundries, different NVM configurations are
used based on the board ID.

So In firmware-name, if the NVM file has an extension, the NVM file will
be used. Otherwise, the system will first try the .bNN (board ID) file,
and if that fails, it will fall back to the .bin file.

Possible configurations:
firmware-name = "QCA6698/hpnv21.bin", "QCA6698/hpbtfw21.tlv";
firmware-name = "QCA6698/hpnv21", "QCA6698/hpbtfw21.tlv";
firmware-name = "QCA6698/hpnv21.bin";

Acked-by: Krzysztof Kozlowski [email protected]
Signed-off-by: Cheng Jiang [email protected]

.../bindings/net/bluetooth/qualcomm-bluetooth.yaml | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)

Cheng Jiang added 3 commits December 17, 2024 14:44
@tedd-an
dt-bindings: net: bluetooth: qca: Expand firmware-name property
4ebaa66 
Expand the firmware-name property to specify the names of NVM and
rampatch firmware to load. This update will support loading specific
firmware (nvm and rampatch) for certain chips, like the QCA6698
Bluetooth chip, which shares the same IP core as the WCN6855 but has
different RF components and RAM sizes, requiring new firmware files.

We might use different connectivity boards on the same platform. For
example, QCA6698-based boards can support either a two-antenna or
three-antenna solution, both of which work on the sa8775p-ride platform.
Due to differences in connectivity boards and variations in RF
performance from different foundries, different NVM configurations are
used based on the board ID.

So In firmware-name, if the NVM file has an extension, the NVM file will
be used. Otherwise, the system will first try the .bNN (board ID) file,
and if that fails, it will fall back to the .bin file.

Possible configurations:
firmware-name = "QCA6698/hpnv21.bin", "QCA6698/hpbtfw21.tlv";
firmware-name = "QCA6698/hpnv21", "QCA6698/hpbtfw21.tlv";
firmware-name = "QCA6698/hpnv21.bin";

Acked-by: Krzysztof Kozlowski <[email protected]>
Signed-off-by: Cheng Jiang <[email protected]>
@tedd-an
Bluetooth: qca: Update firmware-name to support board specific nvm
bfabf97 
Different connectivity boards may be attached to the same platform. For
example, QCA6698-based boards can support either a two-antenna or
three-antenna solution, both of which work on the sa8775p-ride platform.
Due to differences in connectivity boards and variations in RF
performance from different foundries, different NVM configurations are
used based on the board ID.

Therefore, in the firmware-name property, if the NVM file has an
extension, the NVM file will be used. Otherwise, the system will first
try the .bNN (board ID) file, and if that fails, it will fall back to
the .bin file.

Possible configurations:
firmware-name = "QCA6698/hpnv21";
firmware-name = "QCA6698/hpnv21.bin";

Signed-off-by: Cheng Jiang <[email protected]>
@tedd-an
Bluetooth: qca: Expand firmware-name to load specific rampatch
b59bc6e 
The firmware-name property has been expanded to specify the names of NVM
and rampatch firmware for certain chips, such as the QCA6698 Bluetooth
chip. Although it shares the same IP core as the WCN6855, the QCA6698
has different RF components and RAM sizes, necessitating new firmware
files. This change allows for the configuration of NVM and rampatch in
DT.

Possible configurations:
firmware-name = QCA6698/hpnv21.bin, QCA6698/hpbtfw21.tlv;
firmware-name = QCA6698/hpnv21, QCA6698/hpbtfw21.tlv;

Signed-off-by: Cheng Jiang <[email protected]>
@github-actions GitHub Actions
Copy link

CheckPatch
Desc: Run checkpatch.pl script
Duration: 0.24 seconds
Result: PENDING

@github-actions GitHub Actions
Copy link

GitLint
Desc: Run gitlint
Duration: 0.24 seconds
Result: PENDING

@github-actions GitHub Actions
Copy link

SubjectPrefix
Desc: Check subject contains "Bluetooth" prefix
Duration: 0.60 seconds
Result: FAIL
Output:

"Bluetooth: " prefix is not specified in the subject

@github-actions GitHub Actions
Copy link

BuildKernel
Desc: Build Kernel for Bluetooth
Duration: 24.81 seconds
Result: PASS

@github-actions GitHub Actions
Copy link

CheckAllWarning
Desc: Run linux kernel with all warning enabled
Duration: 27.29 seconds
Result: PASS

@github-actions GitHub Actions
Copy link

CheckSparse
Desc: Run sparse tool with linux kernel
Duration: 30.85 seconds
Result: PASS

@github-actions GitHub Actions
Copy link

BuildKernel32
Desc: Build 32bit Kernel for Bluetooth
Duration: 24.89 seconds
Result: PASS

@github-actions GitHub Actions
Copy link

TestRunnerSetup
Desc: Setup kernel and bluez for test-runner
Duration: 435.80 seconds
Result: PASS

@github-actions GitHub Actions
Copy link

TestRunner_l2cap-tester
Desc: Run l2cap-tester with test-runner
Duration: 20.49 seconds
Result: PASS

@github-actions GitHub Actions
Copy link

TestRunner_iso-tester
Desc: Run iso-tester with test-runner
Duration: 32.72 seconds
Result: PASS

@github-actions GitHub Actions
Copy link

TestRunner_bnep-tester
Desc: Run bnep-tester with test-runner
Duration: 7.83 seconds
Result: PASS

@github-actions GitHub Actions
Copy link

TestRunner_mgmt-tester
Desc: Run mgmt-tester with test-runner
Duration: 119.87 seconds
Result: FAIL
Output:

Total: 490, Passed: 484 (98.8%), Failed: 2, Not Run: 4

Failed Test Cases
LL Privacy - Add Device 3 (AL is full)               Failed       0.185 seconds
LL Privacy - Set Flags 1 (Add to RL)                 Failed       0.143 seconds

@github-actions GitHub Actions
Copy link

TestRunner_rfcomm-tester
Desc: Run rfcomm-tester with test-runner
Duration: 7.65 seconds
Result: PASS

@github-actions GitHub Actions
Copy link

TestRunner_sco-tester
Desc: Run sco-tester with test-runner
Duration: 9.40 seconds
Result: PASS

@github-actions GitHub Actions
Copy link

TestRunner_ioctl-tester
Desc: Run ioctl-tester with test-runner
Duration: 8.19 seconds
Result: PASS

@github-actions GitHub Actions
Copy link

TestRunner_mesh-tester
Desc: Run mesh-tester with test-runner
Duration: 6.81 seconds
Result: FAIL
Output:

Total: 10, Passed: 9 (90.0%), Failed: 1, Not Run: 0

Failed Test Cases
Mesh - Send cancel - 2                               Failed       0.110 seconds

@github-actions GitHub Actions
Copy link

TestRunner_smp-tester
Desc: Run smp-tester with test-runner
Duration: 7.05 seconds
Result: PASS

@github-actions GitHub Actions
Copy link

TestRunner_userchan-tester
Desc: Run userchan-tester with test-runner
Duration: 5.03 seconds
Result: PASS

@github-actions GitHub Actions
Copy link

IncrementalBuild
Desc: Incremental build with the patches in the series
Duration: 0.57 seconds
Result: PENDING

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@BluezTestBot