docs(cubie a7s): clarify onboard audio interfaces in audio-usage page - #43
Open
tangzz-radxa wants to merge 1 commit into
Open
docs(cubie a7s): clarify onboard audio interfaces in audio-usage page#43tangzz-radxa wants to merge 1 commit into
tangzz-radxa wants to merge 1 commit into
Conversation
The Cubie A7S audio-usage page imports a generic common MDX whose default output priority is hardcoded to 'Bluetooth Audio > Headphones > HDMI Audio'. This priority does not match A7S hardware, since A7S has no HDMI port and no 3.5mm headphone jack — digital audio is only available through USB-C 2 DisplayPort Alt Mode and Bluetooth. Add a board-specific :::warning callout at the top of the A7S wrapper to spell out the actual audio output paths and link to the hardware interfaces page for reference. The common MDX itself is left untouched so other boards with different audio options (A7A, A7Z, A5E, etc.) keep their existing behaviour. Triggers GitHub Discussion radxa-docs#1881 (owlstead, 2026-06-26) where the customer explicitly noted that the A7S audio-usage page 'doesn't seem to be particular to this board at all' and asked why the default priority lists HDMI / Analogue output. Docs-only wrapper change: 2 files (zh + en), +16/-0 lines. Ref: radxa-docs#1881
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Add a board-specific
:::warningcallout at the top of the Cubie A7Saudio-usage page (zh + en) so users see A7S's actual audio output paths
before reading the generic common MDX.
Why
GitHub Discussion radxa-docs#1881 (owlstead, 2026-06-26) explicitly noted that
the A7S audio-usage page is not specific to A7S and that the default
"Headphones > HDMI" priority does not match A7S hardware.
A7S exposes only USB-C 2 DisplayPort Alt Mode for digital audio
output (no HDMI port, no 3.5mm headphone jack). The current page
shows the generic common MDX with the hardcoded
"Bluetooth Audio > Headphones > HDMI Audio" priority, which is
misleading for A7S users. This has been unanswered on the GitHub side
for 3.5 days at the time of opening this PR.
Scope
docs/cubie/a7s/system-config/audio-usage.md(zh),i18n/en/.../cubie/a7s/system-config/audio-usage.md(en)docs/cubie/a7s(matches thegithub_pr_guard1-scope-per-PR rule)
docs/common/radxa-os/system-config/_audio_usage.mdx)is untouched — it remains the source of truth for boards where
the generic priority actually applies (A7A has all three audio
paths; A7Z / A5E have different gaps and can be addressed in
separate scoped PRs).
Reference