On 11/10/2024 15:41, Rob Herring wrote:
But when a block is changed, any rule on sorting may go out
the window since we add new regions on the end.
Ah I see, I didn't TBH know that.
This one in particular I have to wonder why csiphy is not a separate
node.
Hmm, to be honest with you Rob, even though I realise I'm digging myself
into a hole of yet more work, yes - we should probably structure camss
along the lines of mdss which has separate nodes for DSI phys.
-> mdss: display-subsystem@ae00000{}
We have 4 SoCs "in flight" at the moment.
sdm670 and sc7280 don't require any real driver update to facilitate.
sm8550 and x1e80100 do require new VFE, CSID etc.
We've been debating how to model the regulators for the CSIPHYs too
which are on rails supplied by PMICs external to the SoC.
I'm congniscient of the fact 670, 7280 and to an extent sm8550 have been
on the list for quite some time, so I'd rather not push 670 and 7280 to
have to wait for a whole new way of doing CSIPHYs - especially because
these are old hardware with little to no driver change required to support.
OTOH x1e80100 and sm8550 already need development work so we can do the
CSIPHY transition there.
---
bod
