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

2024-02-19 Thread Dmitry Baryshkov
On Fri, 9 Feb 2024 at 20:58, Dmitry Baryshkov wrote: > > On Fri, 9 Feb 2024 at 20:44, Abhinav Kumar wrote: > > > > > > > > On 2/8/2024 7:01 AM, Dmitry Baryshkov wrote: > > > Existing MDP5 devices have slightly different bindings. The main > > > register region is called `mdp_phys' instead of `mdp

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

2024-02-09 Thread Dmitry Baryshkov
On Fri, 9 Feb 2024 at 20:44, Abhinav Kumar wrote: > > > > On 2/8/2024 7:01 AM, 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 devic

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

2024-02-09 Thread Abhinav Kumar
On 2/8/2024 7:01 AM, 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. Signed-off-

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

2024-02-08 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 --- drivers/gpu/drm/msm/dis