RFCing Panel Drivers -- a proposal for a new type of display driver

[Victor Costan]

Dear FEC,

I'd like to try going through the RFC process with a proposal I've put together. I've been advised to get agreement on the high-level vision first, so I'm only including that vision (the division of responsibilities) in the RFC.

I socialized the proposal at go/fuchsia-panel-drivers and I think it's ready for a broader set of eyes. It now lives at

https://fuchsia.devsite.corp.google.com/preview/costan/fuchsia-src/contribute/governance/rfcs/0000_panel_drivers.md?skip_cache=true

Please help me navigate the RFC process. Thank you very much!

    Victor

[Carlos Pizano Uribe]

Hi,

Of course.

First of all, great doc! really.

Now, it takes a lot of reading to get to the "ask", which is "We propose having a display engine driver be responsible for the display engine block on the host processor, and having a panel driver be responsible for the display panel and its integration with the rest of the device hardware."

I strongly suggest you put some form of that in the front.

Secondly, I don't know what are the tradeoffs, what becomes hard or what becomes much more complex, with that part then it's easier to see if we need an RFC.

The complexity of the whole thing is such that these things are not obvious to me and I suspect, to much of the Fuchsia team.

Finally

-cpu

 

    Victor

--
All posts must follow the Fuchsia Code of Conduct https://fuchsia.dev/fuchsia-src/CODE_OF_CONDUCT or may be removed.
---
You received this message because you are subscribed to the Google Groups "eng-council" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eng-council...@fuchsia.dev.
To view this discussion visit https://groups.google.com/a/fuchsia.dev/d/msgid/eng-council/CAA6qCNevpF_fDu6Dq4%3DJ5DFZNyP2icaD2SxsPOTkAV2H4fBPTA%40mail.gmail.com.

[Yilong Li]

Hi Carlos (sorry it's too late!) and FEC,

I am taking over this RFC as @Victor Costan is out of office. The new updates of the RFC will be available at 

https://fuchsia.devsite.corp.google.com/preview/liyl/fuchsia-src/contribute/governance/rfcs/0000_panel_drivers.md?skip_cache=true (Google internal)

and will be uploaded to the RFC CL (https://fxrev.dev/1317834) publicly. 

I updated the RFC to address the previous comments:

On Wed, Jul 9, 2025 at 3:13 PM Carlos Pizano Uribe <c...@google.com> wrote:

First of all, great doc! really.

Now, it takes a lot of reading to get to the "ask", which is "We propose having a display engine driver be responsible for the display engine block on the host processor, and having a panel driver be responsible for the display panel and its integration with the rest of the device hardware."

I strongly suggest you put some form of that in the front.

Victor has added a Summary section in the beginning of the doc to better summarize the requests.

 

Secondly, I don't know what are the tradeoffs, what becomes hard or what becomes much more complex, with that part then it's easier to see if we need an RFC.

The complexity of the whole thing is such that these things are not obvious to me and I suspect, to much of the Fuchsia team.

I added a few sections to this doc: "Principles" before our design to better address what we would like to achieve, "Challenges' specifies the tradeoffs and what could be more complex with the new panel driver architecture.

Please take another look and let me know if there's anything we need to do to move forward with the RFC process.

Thank you,

Yilong