ChanServ changed the topic of #linux-msm to:
<bamse> fun stuff
Danct12 has quit [Remote host closed the connection]
marvin24_ has joined #linux-msm
qyousef has joined #linux-msm
marvin24 has quit [Ping timeout: 480 seconds]
qyousef_ has quit [Ping timeout: 480 seconds]
jhovold has joined #linux-msm
pevik has joined #linux-msm
Danct12 has joined #linux-msm
Guest205 is now known as go4godvin
Giant_Bool has joined #linux-msm
Giant_Bool is now known as Giant_Bootleg_Defensor
Giant_Bootleg_Defensor has quit [Remote host closed the connection]
pevik_ has quit [Remote host closed the connection]
gpiccoli has quit [Quit: Bears...Beets...Battlestar Galactica]
gpiccoli has joined #linux-msm
lumag_ has joined #linux-msm
Danct12 has quit [Quit: Leaving]
<Mis012[m]> bamse: would it be possible to somewhat easily support Linux applying the static configuration, assuming that it needs to be described in the device tree anyway?
<Mis012[m]> could make running Linux in EL2 quite a bit easier
<Mis012[m]> though I guess for keeping the security properties, one would have to put the static configuration in TZ
<Mis012[m]> not like it makes more sense to have it in the hypervisor when it's concerning completely different cores as well
<Mis012[m]> could also do it in u-boot while it's in EL3, but not exactly sure how that would work
pespin has joined #linux-msm
<bamse> Mis012[m]: i don't know, but i think the "stream mapping registers are read only" is a rather concrete problem to discuss/solve
<Mis012[m]> well, would definitely be nice to have it as quirk for the generic smmu driver
<Mis012[m]> bamse: would you happen to have any pointers as to what the `snps_ctrl_usb2_phy` and `usb2_utmi_clk_en` bits do?
<Mis012[m]> they don't seem to be femtophy signals
<Mis012[m]> but they're treated similarly by the magic init seq
Danct12 has joined #linux-msm
Danct12 has quit [Quit: Quitting]
Danct12 has joined #linux-msm
Danct12 has quit [Remote host closed the connection]
Danct12 has joined #linux-msm
<bamse> Mis012[m]: i'm not familiar with those and i'm not sure where to look
<Mis012[m]> apparently not femtophy databook :/
<Mis012[m]> msm8976 register description probably
<Mis012[m]> or qcs405
<Mis012[m]> for qcs405, I still wonder if the reset values are different from msm8976
<Mis012[m]> because if not, then half of the overrides it's setting are not overrides
diederik_ has joined #linux-msm
diederik has quit [Ping timeout: 480 seconds]
diederik_ is now known as diederik
jhovold has quit [Ping timeout: 480 seconds]
pevik has quit [Ping timeout: 480 seconds]
Danct12 has quit [Ping timeout: 480 seconds]
lumag_ has quit [Ping timeout: 480 seconds]
lumag_ has joined #linux-msm
<Mis012[m]> uh hm...
<Mis012[m]> bamse: does this also apply for qcs405?
<Mis012[m]> it seems that `UTMI_PHY_CMN_CTRL_OVERRIDE_EN` should be used instead, but the qcs405 init seq uses `PICOPHY_UTMI_CONTROL_OVERWRITE_EN`...
<Mis012[m]> hm, actually nvm
<Mis012[m]> `PICOPHY_UTMI_CONTROL_OVERWRITE_EN` is enabled on reset
<Mis012[m]> and the PICOPHY part does hint at it not being too relevant
<Mis012[m]> but then on 8976 and 8937, the reset value for `UTMI_PHY_CMN_CTRL_OVERRIDE_EN` is 0...
<Mis012[m]> so is it different on qcs405?
<Mis012[m]> the init seq doesn't make any attempt at setting it to 1...
<Mis012[m]> managed to get a FLAT fro qcs40x
<Mis012[m]> seems that the reset value is the same
<Mis012[m]> bamse: how the HELL does the init sequence do anything when `UTMI_PHY_CMN_CTRL_OVERRIDE_EN` stays at `0` the whole time????
cxl000 has quit [Quit: Leaving]
<bamse> :)
<Mis012[m]> bamse: don't :) me
<Mis012[m]> is there some magic making `UTMI_PHY_CMN_CTRL_OVERRIDE_EN` redundant or have I just wasted a bunch of time again
<bamse> as i said, i don't know the usb phys well enough to know
<Mis012[m]> bamse: oh, stupid me, turns out that the overrides which are not NOOPs don't have that disclaimer?
<Mis012[m]> except one
<Mis012[m]> well, that's not an override, but it's used as part of the init seq
<Mis012[m]> looks like I will need more testing than I though, because now I wonder of if the USB2_SUSPEND_N_SEL toggling is necessary or not
<Mis012[m]> *thought
<Mis012[m]> and if it is necessary, then whether it's only necessary because it works around the POR changes being NOOPs
<Mis012[m]> actually, there's another fun possibility...
<Mis012[m]> that the overrides are not in fact applied, but since the things that are technically not overrides are what's really important for usb to work, noone ever noticed
<Mis012[m]> bamse: considering how busy the qcs40x owner probably is, I'm afraid getting my theories tested will be a nightmare...
Danct12 has joined #linux-msm
anholt_ has joined #linux-msm
anholt has quit [Ping timeout: 480 seconds]
pespin has quit []