Add support for DRM display subsystem
Get series with b4
b4 am [email protected]Versions newest first
- v2 Latest0 of 3 patches 0 repliesNew
Patches in v2 No applies recorded yet
None of the 3 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCHv2 0/3] Add support for DRM display subsystem
Quoted 8 lines · Kyungmin Park
Quoted 5 lines
And I won't apply new feature for non-dt board file from now on. I think, we
need to support DT in mach-exynos/ instead of non-DT and DT together, so please consider to move on dt supporting for Samsung mobile boards.Probably you misunderstand Arnd word.
Quoted 8 lines
"From the statements made so far, I can see no clear policy that we can apply to everyone. My take on this is that for any work I spend on multiplatform kernel, I concentrate on the DT-based board files and get them to work together first, but leave it up to the individual subarch maintainers whether they want to add other board files into the mix."
It doesn't mean add new feature to non-DT board. don't add new board file.
This is a completely separate discussion, the problem at hand doesn't have anything to do with building a kernel for multiple mach-* directories combined that I was referring to in the text you quote.
Quoted 4 lines
In this case, DRM is not yet ready to support DT.
Okay, you can just drop this patches. but please note that this patches are posted at Mar 13 before you decide.
I think it's a good idea to make new features DT-only because this way we don't get any regressions and everyone who want to use the new feature will be able to test the DT support on his board.
This of course requires that basic DT support is available for the systems in question so we don't regress when moving away from the old board files. My impression is that we're getting close to that point on exynos thanks to Thomas' work on this. AFAICT we don't have a DT binding for screen timings yet, so you will still have to use auxdata for that or put the timings into the driver.
Arnd