<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
<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