buzzmarshall has quit [Quit: Konversation terminated!]
ldevulder has joined #linux-amlogic
ebach has joined #linux-amlogic
Daaanct12 has quit [Ping timeout: 240 seconds]
paddymahoney has quit [Ping timeout: 240 seconds]
paddymahoney has joined #linux-amlogic
paddymahoney has quit [Ping timeout: 265 seconds]
<rockosov_>
narmstrong: Greetings Neil! I hope you're doing great today. Could you please advise me on the optimal timing for submitting changes to A1 dts that involve clock drivers and other related components. Specifically, I'm curious if it's necessary to hold off and wait for the 6.5 release with clock drivers in the stable tree before sending patches, or if it's acceptable to send them now.
gis has quit [Ping timeout: 256 seconds]
rockosov_ has quit [Ping timeout: 240 seconds]
rockosov_ has joined #linux-amlogic
ldevulder has quit [Quit: Leaving]
<rockosov_>
I'm back, sorry
ldevulder has joined #linux-amlogic
f_ has joined #linux-amlogic
gis has joined #linux-amlogic
f_ has quit [Quit: f_]
buzzmarshall has joined #linux-amlogic
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #linux-amlogic
naoki has joined #linux-amlogic
naoki has quit [Client Quit]
<narmstrong>
rockosov_: if jbrunet can provide me an immutable branch with the clocks bindings, then I can merge the DT with clocks
<rockosov_>
narmstrong: If I understand correctly, I can submit all the changes presently, and their processing will be contingent on the state of the clock drivers branch. It's fine, I am content with this arrangement and will try to send them today