Re: [PATCH v3 2/4] drm/msm/dpu: support binding to the mdp5 devices

2024-02-07 Thread Abhinav Kumar
On 2/7/2024 11:56 AM, Dmitry Baryshkov wrote: On Wed, 7 Feb 2024 at 20:48, Abhinav Kumar wrote: On 1/5/2024 3:34 PM, Dmitry Baryshkov wrote: Existing MDP5 devices have slightly different bindings. The main register region is called `mdp_phys' instead of `mdp'. Also vbif register regions

Re: [PATCH v3 2/4] drm/msm/dpu: support binding to the mdp5 devices

2024-02-07 Thread Dmitry Baryshkov
On Wed, 7 Feb 2024 at 20:48, Abhinav Kumar wrote: > > > > On 1/5/2024 3:34 PM, Dmitry Baryshkov wrote: > > Existing MDP5 devices have slightly different bindings. The main > > register region is called `mdp_phys' instead of `mdp'. Also vbif > > register regions are a part of the parent, MDSS

Re: [PATCH v3 2/4] drm/msm/dpu: support binding to the mdp5 devices

2024-02-07 Thread Abhinav Kumar
On 1/5/2024 3:34 PM, Dmitry Baryshkov wrote: Existing MDP5 devices have slightly different bindings. The main register region is called `mdp_phys' instead of `mdp'. Also vbif register regions are a part of the parent, MDSS device. Add support for handling this binding differences.

[PATCH v3 2/4] drm/msm/dpu: support binding to the mdp5 devices

2024-01-05 Thread Dmitry Baryshkov
Existing MDP5 devices have slightly different bindings. The main register region is called `mdp_phys' instead of `mdp'. Also vbif register regions are a part of the parent, MDSS device. Add support for handling this binding differences. Signed-off-by: Dmitry Baryshkov ---