Hi, Marek Szyprowski wrote: > Hello, > > On 2014-07-01 10:46, Tobias Jakobi wrote: >> Hello Marek, >> >> I think this particular clock setup should already be handled by this >> patch: >> http://www.spinics.net/lists/arm-kernel/msg320013.html >> >> Or am I missing something here? > > The patch you have pointed requires adding support for SET_PARENT_PARENT > feature to clock core, which has not been accepted yet. Only then Exynod > DRM drivers can be updated to correctly handle the changed clock tree. I'm aware of this, but my point is: Wouldn't it be better to get the SET_PARENT_PARENT upstream instead of applying a work-around (I am assuming of course that SET_PARENT_PARENT is the correct way of handling these clocks), which would be reverted later anyway? Also this looks like similar to the work duplication issue that was raised before here on the ml. Different groups working on the same thing, but with no or little coordination between them. Might be just me though... > My approach is to introduce minimal changes and use the code which is > already in the exynos drm/hdmi driver (it already manages 'mout_hdmi/mixer' > clocks). If other solution is finally accepted, the code can be simplified > and mout_hdmi/mixer clocks simply ignored. For now - my changes are needed > to get HDMI output working and have least dependencies. > > Best regards With best wishes, Tobias _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
