Re: [PATCH v6 1/5] media: dt-bindings: Add CAMSS device for Kaanapali

[Bryan O'Donoghue]

On 17/12/2025 00:02, Vladimir Zapolskiy wrote:
> My concern is that it makes very little sense to throw any not clearly
> defined hardware properties and interconnections into an unorganized and
> unmanageable pile of everything, because this closes the door to ever 
> update
> the upstream CAMSS driver by adding better CAMSS IP support for any already
> manufactured and sold Qualcomm SoC powered board with done CAMSS support.
>
> If some user already holds a phone, a laptop and expects to offload CPU to
> CAMSS IP one happy day, it's pretty unsatisfactory to say that it will 
> never
> happen on legacy hardware, because there was done an unrecoverable mistake
> by adding never tested properties into CAMSS DT bindings, and the remained
> option is to "wait for future chipsets". Each added unsupported and unused
> property boards up the window of better CAMSS support on manufactured 
> boards.
>
> I don't understand a reason why to do worse for the upstream, when there is
> a clear and feasible alternative not to do worse, thus my misunderstanding
> and my grief for upstream CAMSS are my concerns.

I don't think this answers the question on how describing all of the 
CAMSS hardware precludes switching on demosiac.

To be frank, I don't see any specific arguments here at all.

---
bod