fix(boards): add full_name to xiao_nrf54l15 board.yml for Zephyr 4.4 schema

[Mikefly123]

What

Adds the required full_name: XIAO NRF54L15 field to boards/seeed/xiao_nrf54l15/board.yml.

Why

Zephyr 4.4's board-schema.yaml requires name + full_name (or extend). The vendored xiao_nrf54l15 board.yml predates this requirement and was missing full_name, which broke board discovery globally under Zephyr 4.4 (not just for this board). This matches the in-tree Zephyr 4.4.1 board metadata for the same board.

Validation

• HWIL-proven as carried patch (fixed global board-discovery breakage under Zephyr 4.4); validated as part of proves-core-reference PR #439: feat: UHF radio port to Semtech USP — v5e board, UspRadio integration, carried patches (central tracking PR) proves-core-reference#439

[coderabbitai]

Warning

Review limit reached

@Mikefly123, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 376edb6a-f167-4876-a8fe-ad8cbe81b98e

📥 Commits

Reviewing files that changed from the base of the PR and between bfacd43 and 5ffd7ad.

📒 Files selected for processing (8)

• boards/seeed/xiao_nrf54l15/board.yml
• drivers/usp/Kconfig
• drivers/usp/sx126x/sx126x_board.c
• drivers/usp/sx126x/sx126x_hal.c
• drivers/usp/sx126x/sx126x_hal_context.h
• dts/bindings/usp/semtech,sx126x-new-common.yaml
• modules/smtc_modem_hal/smtc_modem_hal.c
• modules/usp_drivers/dev_env.cmake

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Mikefly123]

Stack position 6/6 (top) of stack Lora-net#8: base #5. Stack-top tree verified identical to former integration PR #7 (0bf3e20).