Hi Paul,
On 4/12/2012 7:06 PM, Paul Walmsley wrote:
Hi
On Thu, 12 Apr 2012, Rajendra Nayak wrote:
On OMAP4+, the clkdm association is moved to hwmod while on older OMAPs'
its associated with a clk.
Sounds like this should be conditional based on the platform, then,
rather than weakening the warning for all platforms ?
Well, as already discussed the clockdomain information is mostly useless
for most clock nodes because the HW is taking care of the dependencies,
so highlighting only the ones missing in hwmod is far from enough and
will avoid scaring people with something that is normal.
Considering that OMAP4 clock domain partition is way more complex than
it was on OMAP2 & 3, if OMAP4 can leave without that, I doubt OMAP2 & 3
clock nodes will ever need it, except HW bugs, as usual.
But still, it is an exception more than the regular case.
Hence look for a clkdm in both clk and hwmod and warn only when
its missing in both. Also fix the pr_warning() to print the correct
hwmod name.
Signed-off-by: Rajendra Nayak<rnayak@xxxxxx>
Acked-by: Benoit Cousson <b-cousson@xxxxxx>
Regards,
Benoit
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
