There are no in-kernel users of MSM_ENC_VBLANK wait type. Drop it
together with the corresponding wait_for_vblank callback.
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 3 --
.../gpu/drm/msm/disp/dpu1/dpu_encoder_phys.h | 1 -
.../drm/msm/disp/dpu1/dpu_e
Implement an alternative for the clk_rcg2_shared_ops, which also
implements a proper is_enabled callback. Note, to use
clk_rcg2_parked_ops one must remove XO (safe source) from the
parent_data, parent_map and freq_table.
Changes since v1:
- Replaced a call to clk_rcg2_is_enabled() with check of th
Add qcom_find_src_cfg(), a helper that maps P_something (src) to the
register value (cfg).
Signed-off-by: Dmitry Baryshkov
---
drivers/clk/qcom/common.c | 12
drivers/clk/qcom/common.h | 2 ++
2 files changed, 14 insertions(+)
diff --git a/drivers/clk/qcom/common.c b/drivers/clk/q
Switch MDP, AHB and ROT clocks to the clk_rcg2_parked_ops so that the
CCF can properly determine if the clock is enabled or disabled.
Signed-off-by: Dmitry Baryshkov
---
drivers/clk/qcom/dispcc-sm8250.c | 13 +++--
1 file changed, 3 insertions(+), 10 deletions(-)
diff --git a/drivers/cl
clk_rcg2_shared_ops implements support for the case of the RCG which
must not be completely turned off. However its design has one major
drawback: it doesn't allow us to properly implement the is_enabled
callback, which causes different kinds of misbehaviour from the CCF.
Follow the idea behind cl
Switch MDP, AHB and ROT clocks to the clk_rcg2_parked_ops so that the
CCF can properly determine if the clock is enabled or disabled.
Signed-off-by: Dmitry Baryshkov
---
drivers/clk/qcom/dispcc-sm8250.c | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff --git a/drivers/clk/qc
clk_rcg2_shared_ops implements support for the case of the RCG which
must not be completely turned off. However its design has one major
drawback: it doesn't allow us to properly implement the is_enabled
callback, which causes different kinds of misbehaviour from the CCF.
Follow the idea behind cl
Implement an alternative for the clk_rcg2_shared_ops, which also
implements a proper is_enabled callback. Note, to use
clk_rcg2_parked_ops one must remove XO (safe source) from the
parent_data and parent_map.
Dmitry Baryshkov (2):
clk: qcom: implement RCG2 'parked' clock support
clk: qcom: dis
On 10/3/2023 3:36 PM, Dmitry Baryshkov wrote:
On Wed, 4 Oct 2023 at 01:12, Kuogee Hsieh wrote:
On 10/3/2023 10:53 AM, Dmitry Baryshkov wrote:
On Tue, 3 Oct 2023 at 19:44, Kuogee Hsieh wrote:
On 9/27/2023 3:00 PM, Dmitry Baryshkov wrote:
On Wed, 27 Sept 2023 at 23:54, Kuogee Hsieh wrote:
On Wed, 4 Oct 2023 at 01:12, Kuogee Hsieh wrote:
>
>
> On 10/3/2023 10:53 AM, Dmitry Baryshkov wrote:
> > On Tue, 3 Oct 2023 at 19:44, Kuogee Hsieh wrote:
> >>
> >> On 9/27/2023 3:00 PM, Dmitry Baryshkov wrote:
> >>> On Wed, 27 Sept 2023 at 23:54, Kuogee Hsieh
> >>> wrote:
> After incorpor
On 10/3/2023 10:53 AM, Dmitry Baryshkov wrote:
On Tue, 3 Oct 2023 at 19:44, Kuogee Hsieh wrote:
On 9/27/2023 3:00 PM, Dmitry Baryshkov wrote:
On Wed, 27 Sept 2023 at 23:54, Kuogee Hsieh wrote:
After incorporated pm_runtime framework into eDP/DP driver, the
incorporating
original dp_pm
On Tue, 3 Oct 2023 at 23:18, Kuogee Hsieh wrote:
>
>
> On 10/3/2023 10:56 AM, Dmitry Baryshkov wrote:
> > On 03/10/2023 20:25, Kuogee Hsieh wrote:
> >>
> >> On 9/27/2023 2:57 PM, Dmitry Baryshkov wrote:
> >>> On Wed, 27 Sept 2023 at 23:54, Kuogee Hsieh
> >>> wrote:
> Currently eDP population
On 10/3/2023 10:56 AM, Dmitry Baryshkov wrote:
On 03/10/2023 20:25, Kuogee Hsieh wrote:
On 9/27/2023 2:57 PM, Dmitry Baryshkov wrote:
On Wed, 27 Sept 2023 at 23:54, Kuogee Hsieh
wrote:
Currently eDP population is done at msm_dp_modeset_init() which happen
at binding time. Move eDP populati
On 03/10/2023 20:25, Kuogee Hsieh wrote:
On 9/27/2023 2:57 PM, Dmitry Baryshkov wrote:
On Wed, 27 Sept 2023 at 23:54, Kuogee Hsieh
wrote:
Currently eDP population is done at msm_dp_modeset_init() which happen
at binding time. Move eDP population to be done at display probe time
so that probe
On Tue, 3 Oct 2023 at 19:44, Kuogee Hsieh wrote:
>
>
> On 9/27/2023 3:00 PM, Dmitry Baryshkov wrote:
> > On Wed, 27 Sept 2023 at 23:54, Kuogee Hsieh wrote:
> >> After incorporated pm_runtime framework into eDP/DP driver, the
> > incorporating
> >
> >
> >> original dp_pm_suspend() to handle power
On 9/27/2023 2:57 PM, Dmitry Baryshkov wrote:
On Wed, 27 Sept 2023 at 23:54, Kuogee Hsieh wrote:
Currently eDP population is done at msm_dp_modeset_init() which happen
at binding time. Move eDP population to be done at display probe time
so that probe deferral cases can be handled effectively
On Tue, 3 Oct 2023 at 20:16, Kuogee Hsieh wrote:
>
>
> On 9/27/2023 2:57 PM, Dmitry Baryshkov wrote:
> > On Wed, 27 Sept 2023 at 23:54, Kuogee Hsieh wrote:
> >> Currently eDP population is done at msm_dp_modeset_init() which happen
> >> at binding time. Move eDP population to be done at display p
On 9/27/2023 2:57 PM, Dmitry Baryshkov wrote:
On Wed, 27 Sept 2023 at 23:54, Kuogee Hsieh wrote:
Currently eDP population is done at msm_dp_modeset_init() which happen
at binding time. Move eDP population to be done at display probe time
so that probe deferral cases can be handled effectively
On 9/27/2023 3:00 PM, Dmitry Baryshkov wrote:
On Wed, 27 Sept 2023 at 23:54, Kuogee Hsieh wrote:
After incorporated pm_runtime framework into eDP/DP driver, the
incorporating
original dp_pm_suspend() to handle power off both DP phy and
controller during suspend and dp_pm_resume() to handl
On Fri, Sep 29, 2023 at 11:16 AM Adrián Larumbe
wrote:
>
> Some BO's might be mapped onto physical memory chunkwise and on demand,
> like Panfrost's tiler heap. In this case, even though the
> drm_gem_shmem_object page array might already be allocated, only a very
> small fraction of the BO is cur
On 03/10/2023 12:31, Dmitry Baryshkov wrote:
>>> +patternProperties:
>>> + "^display-controller@[0-9a-f]+$":
>>> +type: object
>>> +additionalProperties: true
>>> +
>>> +properties:
>>> + compatible:
>>> +const: qcom,sdm670-dpu
>>> +
>>> + "^displayport-controller@[0-9a-f
On Tue, 3 Oct 2023 at 11:48, Krzysztof Kozlowski
wrote:
>
> On 03/10/2023 03:21, Richard Acayan wrote:
> > Add documentation for the SDM670 display subsystem, adapted from the
> > SDM845 and SM6125 documentation.
> >
> > Signed-off-by: Richard Acayan
> > ---
> > .../display/msm/qcom,sdm670-mdss.
On Sunday, September 3rd, 2023 at 23:41, Dmitry Baryshkov
wrote:
> To facilitate this, reuse the 'PATH' property, which was used to
> describe the DP port in the DP MST configuration. Use either
> 'typec:portN' to point out to the Type-C port class device, or just
> 'typec:' if the corresponding
On Tue, Aug 08, 2023 at 03:19:50PM -0700, Kuogee Hsieh wrote:
> DP PHY re-initialization done using dp_ctrl_reinitialize_mainlink() will
> cause PLL unlocked initially and then PLL gets locked at the end of
> initialization. PLL_UNLOCKED interrupt will fire during this time if the
> interrupt mask
On 03/10/2023 03:21, Richard Acayan wrote:
> Add documentation for the SDM670 display subsystem, adapted from the
> SDM845 and SM6125 documentation.
>
> Signed-off-by: Richard Acayan
> ---
> .../display/msm/qcom,sdm670-mdss.yaml | 287 ++
> 1 file changed, 287 insertions(
On Tue, 3 Oct 2023 at 01:48, Kuogee Hsieh wrote:
>
>
> On 9/27/2023 2:41 PM, Dmitry Baryshkov wrote:
> > On Wed, 27 Sept 2023 at 23:54, Kuogee Hsieh wrote:
> >> Currently DP driver is executed independent of PM runtime framework.
> >> This lead to msm edp panel can not be detected by edp_panel dr
On Tue, 3 Oct 2023 at 04:33, Abhinav Kumar wrote:
>
>
>
> On 10/2/2023 3:58 PM, Stephen Boyd wrote:
> > Quoting Abhinav Kumar (2023-09-28 17:46:11)
> >> On 9/27/2023 3:01 PM, Stephen Boyd wrote:
> >>> Quoting Kuogee Hsieh (2023-09-25 09:07:18)
>
> However for external DP case, link train
27 matches
Mail list logo
