On Thu, Oct 09, 2025 at 10:51:31AM +0200, Konrad Dybcio wrote: > On 10/8/25 8:57 PM, Dmitry Baryshkov wrote: > > On Wed, Oct 08, 2025 at 04:05:28PM +0200, David Heidelberg via B4 Relay > > wrote: > >> From: David Heidelberg <[email protected]> > >> > >> Basic description for S6E3FC2X01 DDIC with attached panel AMS641RW. > >> > >> Samsung AMS641RW is 6.41 inch, 1080x2340 pixels, 19.5:9 ratio panel > >> > >> Signed-off-by: David Heidelberg <[email protected]> > >> --- > >> .../bindings/display/panel/samsung,s6e3fc2x01.yaml | 78 > >> ++++++++++++++++++++++ > >> MAINTAINERS | 5 ++ > >> 2 files changed, 83 insertions(+) > >> > > > > Please also describe, why it's not enough to use defined compatible, > > samsung,s6e3fc2x01. Why do we need a separate schema and can't use the > > panel-simple-dsi.yaml > > panel-simple works for 'dumb' (perhaps a harsh word for 'made with > just the in-spec DCS commands in mind') panels, but Samsungs are > widely known to require a ton of vendor magic
The question is about the _schema_. I think it's fine to have a driver for a panel covered by panel-simple-dsi.yaml. > > Perhaps the original change was made with an "oh it just works > surely there's no drawbacks possible" attitude, as the panel > was left initialized by the bootloader -- With best wishes Dmitry
