Re: [PATCH v4 0/5] Add Qualcomm JPEG V4L2 encoder for SM8250

[Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>]

On 7/7/26 12:41 PM, Bryan O'Donoghue wrote:
> On 07/07/2026 11:11, Konrad Dybcio wrote:
>> On 7/7/26 12:00 PM, Bryan O'Donoghue wrote:
>>> On 07/07/2026 10:24, Konrad Dybcio wrote:
>>>> On 7/6/26 3:37 PM, Bryan O'Donoghue wrote:
>>>>> On 06/07/2026 14:02, Vladimir Zapolskiy wrote:

[...]

> OK, I can see how this thread is confusing.
> 
> The idea is to start to declare sub-nodes "on the road" to making camss into a bus. The legacy binding we have is really for the IFE domain - that is CSIPHY, CSID, IFE.
> 
> Right now the camss binding describes those things - so linking say OPE or JPEG back to the thing that describes those isn't right.
> 
> OTOH we _want_ to make the top-level binding into a bus, we've discussed that several times.
> 
> To transition from monolith IFE-domain only, to camss-bus, we should have the sub-nodes fully describe themselves as "camss-bus" doesn't exist yet.
> 
> Once we have compat="camss-bus" then fine, make that linkage, I fully support that.
> 
> That roadmap BTW is why I'm asking Antanas and Loic to make JPEG and OPE sub-nodes of camss - but make them complete sub-nodes - power-domains, clocks, nocs, including the TOP_GDSC.

I think this needlessly increases the amount of combinations we'll
have to keep supporting down the line (with a ton of compatibility
boilerplate code)

Konrad

> It means we can work on splitting apart the existing camss node in isolation to make CSID, IFE as peer sub-nodes.
> 
> We definitely shouldn't be making those sub-nodes dependent on compat="camss" but they definitely will be dependent once we finish making compat="camss-bus".
> 
> When that is done I fully agree TOP_GDSC belongs in the bus node, like MDSS.
> 
> I hope that makes sense.