<tambarus>
krzk: Hi! Tudor Ambarus here. Maybe you can guide me with something. I see that all exynos MUX clocks set the CLK_SET_RATE_NO_REPARENT, which forbids MUX clocks to reparent on clock rate change
<tambarus>
this is since the introduction of the flag in 2013, 819c1de344c5 ("clk: add CLK_SET_RATE_NO_REPARENT flag")
<tambarus>
was there any attempt to remove the CLK_SET_RATE_NO_REPARENT flag for samsung?
<tambarus>
I need to reparent MUX clocks for gs101. I see that exynos850 can benefit of it too.
<tambarus>
I think I'll introduce some MUXN()/MUXN_F macros where CLK_SET_RATE_NO_REPARENT is not set and use it for GS101. N from new maybe? Ideally __MUX() shall remove the CLK_SET_RATE_NO_REPARENT flag once all samsung platforms use MUXN
<krzk>
tambarus: I don't recall any work on removing the flag, so allowing to reparent on rate change. As you see in commit msg, they just preserved existing behavior.
<tambarus>
krzk: Okay, thanks. I'll come up with something.
<krzk>
tambarus: removing the flag would require testing, so probably older platforms should stay as is unless you can find someone testing it for you
<tambarus>
krzk: yeah, I agree. That's why maybe I shall introduce a new MUX() macro. Maybe MUXN -> n from selectable (from 1 to n), or as in New
<tambarus>
and use it just for GS101 ..., or granularly, only on the clocks that are tested in GS101
Peng_Fan has quit [Quit: Connection closed for inactivity]
GNUtoo has quit [Ping timeout: 260 seconds]
GNUtoo has joined #linux-exynos
chewitt has quit [Quit: Zzz..]
GNUtoo has quit [Read error: Connection reset by peer]
GNUtoo has joined #linux-exynos
GNUtoo has quit [Remote host closed the connection]