vc4-fkms: Add hotplug support
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- c
- Domain
- embedded-iot, operating-systems
Research direction
The proposal concerns FKMS HDMI hotplug control and DRM/KMS connector status; start by tracing how FKMS creates HDMI display outputs and reports connector state. Done means HDMI outputs are created consistently and monitor enable/disable behavior follows connector status for the supported HDMI, DSI, DPI, and SDTV combinations.
Written by the indexing model from the issue text.
Description
Task tracking / proposal.
As noted in https://github.com/raspberrypi/firmware/issues/1243, routing HDMI audio sensibly is currently a bit messy due to FKMS hiding whether it is connector HDMI0 or HDMI1 into which a monitor is connected. What DRM/KMS sees as HDMI-1 could therefore be a single monitor plugged into either connector.
Bottom line is we can have two displays active at a time due to only two HVS channels being available (the third channel is dedicated to the transposer).
The supported use cases are
- HDMI0 & HDMI1
- HDMI0 & DSI1
- HDMI0 & DPI
- SDTV.
(DSI and DPI are handled in the same way and named DSI-1 via DRM/KMS.)
If we add HDMI hotplug control to FKMS, then we can always create the HDMI display outputs in a consistent way, and the connector status should do the magic within the frameworks to enable and disable the monitors at appropriate times.
- Dominant language
- C
- Stars
- 13.2k
- Forks
- 5.5k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 21
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from raspberrypi/linux
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raspberrypi/linux#7415 · 2 comments · 1 reaction ·
-
rp1-cfe doesn't forward V4L2_EVENT_SOURCE_CHANGE event from csi-2 sensor driver to userspace app Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
raspberrypi/linux#7399 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
raspberrypi/linux#7357 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raspberrypi/linux#7054 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
raspberrypi/linux#7634 · 8 comments · 1 reaction ·
All issues in raspberrypi/linux
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
zephyrproject-rtos/zephyr#119726 ·
-
[Bounty proposal] fix(web): memory insights count an evening memory on the next day ($25 proposed) Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
BasedHardware/omi#15320 ·
-
[adam] AdamNet network read doesn't cap to MAX_ADAM_PACKET_LEN, overflows client receive buffers Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
FujiNetWIFI/fujinet-firmware#1649 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
HarbourMasters/Shipwright#7229 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
riscv-software-src/riscv-isa-sim#2435 · 1 comment ·