ChanServ changed the topic of #linux-msm to:
pg12 has quit [Ping timeout: 480 seconds]
pg12 has joined #linux-msm
Danct12 has joined #linux-msm
pg12_ has joined #linux-msm
pg12 has quit [Ping timeout: 480 seconds]
pg12_ is now known as pg12
Daanct12 has quit [Ping timeout: 480 seconds]
marvin24_ has joined #linux-msm
marvin24 has quit [Ping timeout: 480 seconds]
Daanct12 has joined #linux-msm
Daanct12 has quit [Remote host closed the connection]
svarbanov_ has joined #linux-msm
svarbanov has quit [Ping timeout: 480 seconds]
svarbanov__ has joined #linux-msm
svarbanov_ has quit [Ping timeout: 480 seconds]
<lumag> strongtz[m], sure, thank you.
enick_702 is now known as go4godvin
pespin has joined #linux-msm
marvin24 has joined #linux-msm
<Danct12> aka_[m]: seems like pmi8950 is only used for backlight stuffs
<Danct12> only the pm8937 appears need to be ported
<Danct12> this is getting spooky
marvin24_ has quit [Ping timeout: 480 seconds]
<Danct12> i did check revid, there is pm8937 there
<Danct12> but seems like there's no reference to it outside the defines
<aka_[m]> Danct12 also for fuel gauge and charger
<aka_[m]> And others
<aka_[m]> PM89XX.DTSI are mostly copy-paste
<aka_[m]> Most diffs wirh gpio/mpp holes
<aka_[m]> As you know 8917 is just cut down 8937
<Danct12> hmm, then i guess i can just cpypaste and that mostly will work
<Danct12> what about the spmi regulators?
<Danct12> that thing is a little bit confusing for me
<aka_[m]> these are used for cpu vdd i believe
<aka_[m]> you have msm8937-regulator.dtsi and something like msm8937-rpm-regulator
<Danct12> /quit
Danct12 has quit [Quit: WeeChat 4.1.0]
f_ has joined #linux-msm
Danct12 has joined #linux-msm
<strongtz[m]> lumag: With charger plugged in at boot, I got these:... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/CUzJnpBQeCEhLFEuUKqANyhd>)
<strongtz[m]> Without a charger at boot, there will be some failures when I plug in a type-c dongle, which doesn't seem to harm much.... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/edYWqoCJycaNknuLLAeMpgCK>)
ungeskriptet is now known as Guest4701
ungeskriptet has joined #linux-msm
ungeskriptet is now known as Guest4702
ungeskriptet has joined #linux-msm
Guest4701 has quit [Ping timeout: 480 seconds]
Guest4702 has quit [Ping timeout: 480 seconds]
<lumag> strongtz[m], ack, thank you. This is indeed the typical GET_PDOS issue, which should likely be fixed by the patchset that I posted. You might need to opt-in to use the workaround.
<lumag> If you have to do that, please respond to the series I've posted.
<strongtz[m]> lumag nice, thanks for your patchset. I'll reply to the series after testing.
<mal> bryanodonoghue: hi, I was looking at your named power domain patchset for camss and was wondering about ispif_reset function in camss-ispif.c which calls camss_pm_domain_on using the PM_DOMAIN_VFEX enums and I need to add third VFE power domain for SC7280 which I think would break in that case platforms with fewer power domains
<mal> should that code also somehow use named power domains or do I misunderstand how things work
pespin has quit [Remote host closed the connection]
mripard has quit [Quit: mripard]
<bryanodonoghue> So ispif is for the 8916/8917 SoC series
<bryanodonoghue> for sc7280 you'd want a more modern VFE/CSID and CSIPHY set
<mal> hmm, ok
<mal> so I misunderstood how the whole thing is done
<bryanodonoghue> lets have a quick look at sc7280 VFE and CSID versions
<mal> it's close to sdm845 and sm8250
<mal> now that I looking at the structs more carefully I think that ispif is not defined
<bryanodonoghue> sdm845 is vfe17x sm8250 is vfe480
<mal> this is vfe165
<mal> same registers as vfe170
<bryanodonoghue> so I think z3ntu has some stuff for sc7280/qcs6490/sm7325 already
<z3ntu> not yet, mal has been faster with starting on something ;)
<bryanodonoghue> ah right
<bryanodonoghue> if 165 is a subset of 17x where 175 is 170 with a few additional registers, then you probably can reuse vfe17x
<bryanodonoghue> you need to work out which CSID you have
<z3ntu> qcom,vfe165_160 / qcom,vfe-lite165 -> vfe0, vfe1, vfe2, vfe_lite0, vfe_lite1
<z3ntu> qcom,csid165_204 / qcom,csid-lite165 -> csid0, csid1, csid2, csid_lite0, csid_lite1
<z3ntu> qcom,csiphy-v1.2.1 -> csiphy0, csiphy1, csiphy2, csiphy3, csiphy4
<mal> bryanodonoghue: one more question, in downstream sm8250 there are csid registers but not in mainline? are those not needed? just using that as comparison for checking how things should be done
<bryanodonoghue> yeah no so that's what I mean for new major silicon versions an address space is allocated
<bryanodonoghue> it can be filled up with additional regs as the versions bump
<bryanodonoghue> but its additive
<bryanodonoghue> so, if you have support for VFE 170, you should be fine to use VFE 175, provided you don't want any of the functionality that 175 provides over 170
<bryanodonoghue> I think you should be fine with csid-gen2
<bryanodonoghue> the registers appear to line up
<mal> thanks, that is what I was using
Ristovski has joined #linux-msm
marvin24_ has joined #linux-msm
marvin24 has quit [Ping timeout: 480 seconds]