11:58 <bryanodonoghue> z3ntu fp4 or fp5 has a CPHY somewhere as I recall right ?

11:59 <z3ntu> bryanodonoghue: FP5 has one camera connected with C-PHY, the other two are D-PHY

11:59 <z3ntu> And FP4 is all D-PHY if I'm not mistaken

12:00 <z3ntu> yep FP4 is all D-PHY according to schematics

12:06 <z3ntu> bryanodonoghue: you saw the message where I pinged you on Friday, right?

12:35 <bryanodonoghue> yes

12:35 <bryanodonoghue> i have two bits of hardware with a CPHY to my knowledge

12:35 <bryanodonoghue> fp5 is one of them

12:36 <bryanodonoghue> my own priority is landing x1e80100 support + associated sensor drivers

12:36 <bryanodonoghue> phy work next all things being equal

12:42 <z3ntu> great :)

16:32 <Tofe_> I wonder, I have a pm8058-pwm driver in downstream code, but there's no such thing in current mainline linux code: do I need to import the code, or can I reuse and configure a generic pwm driver?

16:34 <Tofe_> Basically I just want a pwm handle for my backlight, but right now apart from the corresponding gpio on the pm8058 I don't have anything to provide

20:08 <z3ntu> Hi! I have a problem with camcc driver on sm6350. When I try to enable <&camcc CAMCC_MCLK0_CLK> the clock is stuck "camcc_mclk0_clk status stuck at 'off'"

20:09 <z3ntu> When I add ".flags = ALWAYS_ON," to the titan_top_gdsc in camcc driver then it seems to go away consistently, so seems that clock depends on the pd being on.

20:09 <z3ntu> Is there any way to model this? I don't see any significant differences between sm6350 camcc and any other camcc driver in that regard

20:11 <z3ntu> One thing, camcc itself doesn't have a power-domain defined, but since we're not getting a board reset when touching camcc I'd think that's not an issue, whatever powers camcc is probably on anyways due to lots of other components

21:50 <z3ntu> I feel like my camcc issue is a combination of a bunch of things and I can't really figure out even a reliable workaround. I think GCC_CAMERA_AHB_CLK is also somehow involved in the whole thing...