ChanServ changed the topic of #linux-msm to:
logicalerzor has joined #linux-msm
logicalerzor has quit [Quit: Connection closed for inactivity]
junari has joined #linux-msm
junari has quit [Remote host closed the connection]
logicalerzor has joined #linux-msm
logicalerzor[m] has joined #linux-msm
logicalerzor has left #linux-msm [#linux-msm]
<sgerhold> aka_[m]: I'm quite sure you need both clocks running for (certain?) register accesses to succeed. I guess you can try that, but perhaps the clock is even running by default when the DSP starts. Would need to explicitly "disable" it to be sure
mani_s has joined #linux-msm
mani_s has left #linux-msm [#linux-msm]
Caterpillar has quit [Quit: Konversation terminated!]
mani_s has joined #linux-msm
mani_s has quit []
<aka_[m]> sgerhold: issue is without DIG_CLK enabled in machine driver mi2s fails to start
<sgerhold> dsp returns an error?
<aka_[m]> would dumping registers pre and post dig_clk enablement help?
<aka_[m]> yea
<aka_[m]> 110
<aka_[m]> maybe there is some gating?
<aka_[m]> like top_ctl have its own clock
<aka_[m]> digital codec kinda does mclk setting
<aka_[m]> CDC_TOP_CTL RESET_VALUE 0x00000001
<sgerhold> hm I'm not entirely sure about the startup sequence, perhaps the codec would always already be running at that point
<aka_[m]> maybe there is something more to it like qdsp also voting for voltages on clock enable
<aka_[m]> i seen some mentions of lpaif dig codec having to be enabled before afe_port_cmd_device_start is issued
<aka_[m]> whatever, pm patches could slide i think
<aka_[m]> sgerhold: i have weird idea
<aka_[m]> there is a clock on 8953/8976 which seems to not exist on 8916
<aka_[m]> what is description is wrong
<aka_[m]> and codec root is 5
<aka_[m]> guess i should read this register pre/post enablement
z_z3ntu_bouncer has quit [Quit: ZNC 1.9.1 - https://znc.in]
z_z3ntu_bouncer has joined #linux-msm
xtex has quit [Remote host closed the connection]
xtex has joined #linux-msm
<aka_[m]> Affe Null: out of wonder
<aka_[m]> have you tested these q6afe patches you made on 8916 while reverting stuff?
<aka_[m]> i mean making it inline with newer socs
<aka_[m]> like there is no ahb passed to wcd-digital
danylo has quit [Quit: Ping timeout (120 seconds)]
danylo has joined #linux-msm
<aka_[m]> great
<aka_[m]> ADSL dead
<aka_[m]> wrong chat lol soory
stefan-schmidt[m] has joined #linux-msm
<JIaxyga[m]> Hey, krzk:. Do you agree with Vladimir's advice?... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/kNTXZZqTVrZNELwuuyHtethg>)
<aka_[m]> sgerhold: uh i took a look at wcd-digital passed clocks and it passes IXFABRIC but also i took a look at other clocks like base AHB ones and it seems on 8916 reset always toggle CLK_OFF bit
<aka_[m]> not a case on 8976/8953
<aka_[m]> however enable so bit[0] is also 9
<aka_[m]> *0
<aka_[m]> not even mentioning on 8916 there is single register for that and on 8976 there is also SPDMTM one
<aka_[m]> seems a case on other clocks too
<aka_[m]> like CODEC_DIGCODEC_CBCR
<krzk> JIaxyga[m]: just paste the link if you want me to go somewhere...
<krzk> matrix messages do not work in IRC
<JIaxyga[m]> Do you agree with Vladimir's advice?
<krzk> JIaxyga[m]: I don't know, you tell me. Are the clocks valid for sm8450 since they are put in the sm8450 bindings?
<krzk> Anyway, any include won't work because both headers might go their own way
<JIaxyga[m]> krzk: No, this clocks is not valid for sm8450. But at the same time we need to have them in this header, as the sm8450 (to support sm8475) driver needs it. So creating sm8475 header file and importing sm8450 is not such a bad idea. In the driver I will replace sm8450.h with sm8475.h
<krzk> JIaxyga[m]: and how will it work when we add one more ID to sm8450?
<krzk> As I said, headers will go their own way. Have their own IDs.
<JIaxyga[m]> krzk: We define them as NULL in the driver
<JIaxyga[m]> And then change to:
<JIaxyga[m]> gcc_sm8450_desc.clks[GCC_GPLL2] = &gcc_gpll2.clkr;
<JIaxyga[m]> gcc_sm8450_desc.clks[GCC_GPLL3] = &gcc_gpll3.clkr;
<JIaxyga[m]> if compatible = sm8475
<krzk> How does it help? I am talking about duplicated define!
<JIaxyga[m]> What do you suggest then? Completely rewrite the driver for sm8475?
<krzk> Depends how anyone plans to grow sm8475. It could be one header with sm8475 defines prepended with prefix.
<JIaxyga[m]> krzk: Just in case, here is the downstream commit:
<JIaxyga[m]> cape = sm8475
<JIaxyga[m]> waipio = sm8450
<JIaxyga[m]> krzk: By prefix do you mean GCC_SM8475_GPLL2? Or what?
<krzk> JIaxyga[m]: yes
<krzk> rather SM8475_whatever_name
<JIaxyga[m]> Okay thank you
<JIaxyga[m]> Then another question for you konradybcio lumag . Where is it better to write sm8475 prefix in the name of structures? At the beginning of the name or at the end or as it is now?
Adrian[m] has joined #linux-msm
<Adrian[m]> https://lore.kernel.org/linux-arm-msm/20240804-sm8350-fixes-v1-0-1149dd8399fe@linaro.org/T/#m5024e9c7de42ea0217f0e94495a2656d1502f7fe lumag just FYI: MASTER_MDP_DISP is used in sm8450.dtsi, your patch breaks it :)
stefan-schmidt[m] has quit [Quit: Reconnecting]
stefan-schmidt[m] has joined #linux-msm
stefan-schmidt[m] is now known as stefan-schmidt
stefan-schmidt has quit [Quit: Reconnecting]
stefan-schmidt has joined #linux-msm
stefan-schmidt has quit []
stefan-schmidt has joined #linux-msm