Sylwester Nawrocki wrote: > > Hi Shaik, > > On 03/15/2013 10:00 AM, Shaik Ameer Basha wrote: > > On Thu, Mar 7, 2013 at 9:05 PM, Sylwester Nawrocki > > <s.nawrocki@xxxxxxxxxxx> wrote: > ... > >> May I ask what do you need this for ? This code won't be used for > >> Exynos4 and Exynos5 SoCs starting from 3.10. And it is going to be > >> removed once other platforms are converted to the new Samsung clocks > >> driver. > > > > I had some issues in exynos5 with out this implementation. > > But yes... you are right, once we move to common clock framework (CCF) > > we don't require this change, as CCF doesn't use this (for exynos 4/5). > > > > What about all old non-dt based platforms? > > Cant they use this change until they move to DT and CCF? > > I have nothing against the patch, I was just curious if you need > it for the new SOCs where the new clocks driver is supposed to be used. > Of course other Samsung platforms could switch to CCF before having > support for the device tree. > Sorry for late response on this... Yes, I think, as many guys said, this is not required for now for exynos4/5. But the reason is different, I think, because the parent clock should be set depends on each board. That's why there are many parent clocks hardware providing. Sometimes just one parent clock can be used as a default though. - Kukjin -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |