On 22/02/16 18:49, Tony Lindgren wrote: >>> I think separate .dtb files are the best option at the moment, and >>> choose the right one in the bootloader. > > That's not going to work for many boards as there are just too many > combinations to support. I think it's fine if there's just one "base" .dts file, so for N panels you'll end up with N .dtbs. The problems start if you have multiple base .dts files for, say, different board and SoC revisions. Then the amount of .dtbs explode. >>> Hopefully DT overlays will provide a better solution in the near future. > > And that's been already years in making. > > I think the only current real fix for issues like this is to include > multiple configurations in the panel code that can then be selected > based on the device tree compatible flag or kernel cmdline. Well, there are a few options other than the DT overlays and dealing with this in the bootloader, and each of those options is hacky. - board specific platform code detects the display, and appends the necessary DT data (or uses platform data, but I'd rather get rid of pdata, not add more). - create board specific drivers that detect the display and use the correct video timings. - abuse the board's .dts, and fill in all the possible panels there, and then at runtime somehow choose which one is used. Well, nothing else comes to my mind. And those above are roughly in my least-bad-to-most-bad order. Tomi
Attachment:
signature.asc
Description: OpenPGP digital signature
