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

[Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>]

On Fri, Jul 10, 2026 at 02:33:53PM +0200, Konrad Dybcio wrote:
> On 7/10/26 2:28 PM, Dmitry Baryshkov wrote:
> > On Thu, Jul 09, 2026 at 08:16:21PM +0200, Konrad Dybcio wrote:
> >> On 7/9/26 9:33 AM, Dmitry Baryshkov wrote:
> >>> On Wed, Jul 08, 2026 at 10:21:43PM +0100, Bryan O'Donoghue wrote:
> >>>> On 08/07/2026 13:19, Konrad Dybcio wrote:
> >>>>> 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:
> 
> [...]
> 
> >>> Which way of representing device nodes makes it easier to migrate
> >>> existing platform to the CSI PHY driver, while keeping compatibility
> >>> with old DTs (yeah, ABI, old DTs must continue to work)?
> >>
> >> Quite frankly, I don't consider the existing (meganode) description
> >> any valid, and would vote to rip it the second a replacement is
> >> available. But once, not N times.
> > 
> > Rip without providing backwards compatibility?
> 
> Because the existing bindings make ensuring the required performance
> state of power domains impossible, yes

Then, should it just be 'write new set of bindings and drivers for the
platform XYZ', then completely migrate existing platforms one by one.

-- 
With best wishes
Dmitry