AM43xx & OMAP5 DSS DT changes
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 6 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 6 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/6] AM43xx & OMAP5 DSS DT changes
Quoted 20 lines · Tomi Valkeinen
Quoted 19 lines · Tony Lindgren
Quoted 17 lines · Tomi Valkeinen
Quoted 8 lines · Tony Lindgren
Quoted 7 lines · Tomi Valkeinen
Hi,
Here are the AM43xx and OMAP5 display DT changes again. I've sent the clock related changes separately, and I removed OMAP5's RFBI node, which depends on more clock changes. The RFBI driver doesn't work at the moment anyway, so removing the RFBI node should not be an issue.
Quoted 6 lines
Quoted 2 lines
Tony, if these look fine (the rfbi change is the only one compared to the previous versions), can you queue them for 3.16?
Probably best that you do a late branch again after arm-soc dts changes have been merged. Sounds like you have at least that macro dependency to omap-for-v3.16/dt-v2 so you should probably base your branch on
There are no dependencies that I know of. Which macro dependency is that?
Quoted 8 lines
Quoted 2 lines
Oh for the "[PATCH v2] ARM: dts: duovero-parlor: Add HDMI output" that now uses the
OMAP4_IOPADmacro.Ok.
But generally, isn't it better if the .dts changes go through your tree? None of the display related .dts changes have any dependencies to omapdss as such.
Yes in general, but it's getting very late for v3.16, and..
Quoted 2 lines
I can collect the patches, as I've done, to let them mature a bit in my tree, but I'd rather get them merged via your dt branch.
..I may not queue any more patches for v3.16. The branches I've sent have not yet been merged into arm-soc, so at minimum I'm going to wait for that. If we have -rc6 tagged today and no -rc7, I'm switching into fixes only mode. So in this case it's probably best that you merge them so we can get the display dependency out of the way for v3.16.
Regards,
Tony