9 Dec
2016
9 Dec
'16
1:55 a.m.
Hi Stephen
I don't see any reason why we need this patch though. The binding works as is, so supporting different styles doesn't seem like a good idea to me. Let's just keep what we have? Even if a sub-node like cpu or codec gets more than one element in the clocks list property, we can make that work by passing a clock-name then based on some sort of other knowledge.
OK, thanks. Let's skip this patch. But I believe this idea/method itself is not wrong (?)
Right it's not wrong, just seems confusing to have two methods.
Thanks. Very clear for me :)