* [PATCH v2] drm/msm/dpu: Correct dpu destroy and disable order
@ 2018-11-02 12:49 Jayant Shekhar
[not found] ` <1541162957-12796-1-git-send-email-jshekhar-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
0 siblings, 1 reply; 6+ messages in thread
From: Jayant Shekhar @ 2018-11-02 12:49 UTC (permalink / raw)
To: dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW,
linux-arm-msm-u79uwXL29TY76Z2rM5mHXA,
freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW,
devicetree-u79uwXL29TY76Z2rM5mHXA
Cc: abhinavk-sgV2jX0FEOL9JmXXK+q4OQ, Jayant Shekhar,
robdclark-Re5JQEeQqe8AvxtiuMwx3w, nganji-sgV2jX0FEOL9JmXXK+q4OQ,
seanpaul-F7+t8E8rja9g9hUCZPvPmw,
hoegsberg-F7+t8E8rja9g9hUCZPvPmw, jsanka-sgV2jX0FEOL9JmXXK+q4OQ,
chandanu-sgV2jX0FEOL9JmXXK+q4OQ
In case of msm drm bind failure, dpu_mdss_destroy is triggered.
In this function, resources are freed and pm runtime disable is
called, which triggers dpu_mdss_disable. Now in dpu_mdss_disable,
driver tries to access a memory which is already freed. This
results in kernel panic. Fix this by ensuring proper sequence
of dpu destroy and disable calls.
Changes in v2:
- Removed double spacings [Jeykumar]
Signed-off-by: Jayant Shekhar <jshekhar@codeaurora.org>
---
drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c b/drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c
index fd9c893..902bb4c 100644
--- a/drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c
+++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c
@@ -156,18 +156,15 @@ static void dpu_mdss_destroy(struct drm_device *dev)
struct dpu_mdss *dpu_mdss = to_dpu_mdss(priv->mdss);
struct dss_module_power *mp = &dpu_mdss->mp;
+ pm_runtime_disable(dev->dev);
_dpu_mdss_irq_domain_fini(dpu_mdss);
-
free_irq(platform_get_irq(pdev, 0), dpu_mdss);
-
msm_dss_put_clk(mp->clk_config, mp->num_clk);
devm_kfree(&pdev->dev, mp->clk_config);
if (dpu_mdss->mmio)
devm_iounmap(&pdev->dev, dpu_mdss->mmio);
dpu_mdss->mmio = NULL;
-
- pm_runtime_disable(dev->dev);
priv->mdss = NULL;
}
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
_______________________________________________
Freedreno mailing list
Freedreno@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/freedreno
^ permalink raw reply related [flat|nested] 6+ messages in thread
* Re: [PATCH v2] drm/msm/dpu: Correct dpu destroy and disable order
[not found] ` <1541162957-12796-1-git-send-email-jshekhar-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
@ 2018-11-02 13:15 ` Sean Paul
2018-11-02 14:32 ` Jordan Crouse
` (2 subsequent siblings)
3 siblings, 0 replies; 6+ messages in thread
From: Sean Paul @ 2018-11-02 13:15 UTC (permalink / raw)
To: Jayant Shekhar
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA,
linux-arm-msm-u79uwXL29TY76Z2rM5mHXA,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW,
robdclark-Re5JQEeQqe8AvxtiuMwx3w, nganji-sgV2jX0FEOL9JmXXK+q4OQ,
seanpaul-F7+t8E8rja9g9hUCZPvPmw, abhinavk-sgV2jX0FEOL9JmXXK+q4OQ,
hoegsberg-F7+t8E8rja9g9hUCZPvPmw,
freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW,
jsanka-sgV2jX0FEOL9JmXXK+q4OQ, chandanu-sgV2jX0FEOL9JmXXK+q4OQ
On Fri, Nov 02, 2018 at 06:19:17PM +0530, Jayant Shekhar wrote:
> In case of msm drm bind failure, dpu_mdss_destroy is triggered.
> In this function, resources are freed and pm runtime disable is
> called, which triggers dpu_mdss_disable. Now in dpu_mdss_disable,
> driver tries to access a memory which is already freed. This
> results in kernel panic. Fix this by ensuring proper sequence
> of dpu destroy and disable calls.
>
> Changes in v2:
> - Removed double spacings [Jeykumar]
>
> Signed-off-by: Jayant Shekhar <jshekhar@codeaurora.org>
Reviewed-by: Sean Paul <sean@poorly.run>
> ---
> drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c b/drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c
> index fd9c893..902bb4c 100644
> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c
> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c
> @@ -156,18 +156,15 @@ static void dpu_mdss_destroy(struct drm_device *dev)
> struct dpu_mdss *dpu_mdss = to_dpu_mdss(priv->mdss);
> struct dss_module_power *mp = &dpu_mdss->mp;
>
> + pm_runtime_disable(dev->dev);
> _dpu_mdss_irq_domain_fini(dpu_mdss);
> -
> free_irq(platform_get_irq(pdev, 0), dpu_mdss);
> -
> msm_dss_put_clk(mp->clk_config, mp->num_clk);
> devm_kfree(&pdev->dev, mp->clk_config);
>
> if (dpu_mdss->mmio)
> devm_iounmap(&pdev->dev, dpu_mdss->mmio);
> dpu_mdss->mmio = NULL;
> -
> - pm_runtime_disable(dev->dev);
> priv->mdss = NULL;
> }
>
> --
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> a Linux Foundation Collaborative Project
>
--
Sean Paul, Software Engineer, Google / Chromium OS
_______________________________________________
Freedreno mailing list
Freedreno@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/freedreno
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH v2] drm/msm/dpu: Correct dpu destroy and disable order
[not found] ` <1541162957-12796-1-git-send-email-jshekhar-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-11-02 13:15 ` Sean Paul
@ 2018-11-02 14:32 ` Jordan Crouse
2018-11-05 19:31 ` Doug Anderson
2018-11-09 6:07 ` Rajendra Nayak
3 siblings, 0 replies; 6+ messages in thread
From: Jordan Crouse @ 2018-11-02 14:32 UTC (permalink / raw)
To: Jayant Shekhar
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA,
linux-arm-msm-u79uwXL29TY76Z2rM5mHXA,
abhinavk-sgV2jX0FEOL9JmXXK+q4OQ,
robdclark-Re5JQEeQqe8AvxtiuMwx3w, nganji-sgV2jX0FEOL9JmXXK+q4OQ,
seanpaul-F7+t8E8rja9g9hUCZPvPmw,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW,
hoegsberg-F7+t8E8rja9g9hUCZPvPmw,
freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW,
jsanka-sgV2jX0FEOL9JmXXK+q4OQ, chandanu-sgV2jX0FEOL9JmXXK+q4OQ
On Fri, Nov 02, 2018 at 06:19:17PM +0530, Jayant Shekhar wrote:
> In case of msm drm bind failure, dpu_mdss_destroy is triggered.
> In this function, resources are freed and pm runtime disable is
> called, which triggers dpu_mdss_disable. Now in dpu_mdss_disable,
> driver tries to access a memory which is already freed. This
> results in kernel panic. Fix this by ensuring proper sequence
> of dpu destroy and disable calls.
Since you are in this specific area, I noticed we also had some memory leaks
on bind "failure" and I just sent out a patch for that.
Jordan
--
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
_______________________________________________
Freedreno mailing list
Freedreno@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/freedreno
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH v2] drm/msm/dpu: Correct dpu destroy and disable order
[not found] ` <1541162957-12796-1-git-send-email-jshekhar-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-11-02 13:15 ` Sean Paul
2018-11-02 14:32 ` Jordan Crouse
@ 2018-11-05 19:31 ` Doug Anderson
2018-11-09 6:07 ` Rajendra Nayak
3 siblings, 0 replies; 6+ messages in thread
From: Doug Anderson @ 2018-11-05 19:31 UTC (permalink / raw)
To: jshekhar-sgV2jX0FEOL9JmXXK+q4OQ
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA, linux-arm-msm, dri-devel,
Rob Clark, nganji-sgV2jX0FEOL9JmXXK+q4OQ, Sean Paul,
Abhinav Kumar, Kristian H. Kristensen, freedreno,
Jeykumar Sankaran, Chandan Uddaraju
Hi,
On Fri, Nov 2, 2018 at 5:49 AM Jayant Shekhar <jshekhar@codeaurora.org> wrote:
>
> In case of msm drm bind failure, dpu_mdss_destroy is triggered.
> In this function, resources are freed and pm runtime disable is
> called, which triggers dpu_mdss_disable. Now in dpu_mdss_disable,
> driver tries to access a memory which is already freed. This
> results in kernel panic. Fix this by ensuring proper sequence
> of dpu destroy and disable calls.
>
> Changes in v2:
> - Removed double spacings [Jeykumar]
>
> Signed-off-by: Jayant Shekhar <jshekhar@codeaurora.org>
> ---
> drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
I can confirm that this fixes a crash I was running into.
Specifically it looked like this:
---
msm_dsi ae94000.dsi: ae94000.dsi supply gdsc not found, using dummy regulator
msm_dsi ae94000.dsi: Linked as a consumer to regulator.0
msm_dsi ae94000.dsi: Dropping the link to regulator.0
msm_dsi ae94000.dsi: Linked as a consumer to regulator.35
msm_dsi_manager_register: failed to register mipi dsi host for DSI 0
msm_dsi ae94000.dsi: Dropping the link to regulator.35
msm ae00000.mdss: failed to bind ae94000.dsi (ops dsi_ops): -517
Unable to handle kernel paging request at virtual address 006b6b6b6b6b6b6b
...
Workqueue: pm pm_runtime_work
...
Call trace:
clk_disable+0x24/0x4c
msm_dss_enable_clk+0xec/0x164
dpu_mdss_disable+0x2c/0x84
msm_runtime_suspend+0x50/0x5c
pm_generic_runtime_suspend+0x3c/0x48
genpd_runtime_suspend+0xf4/0x1cc
__rpm_callback+0x128/0x1a4
rpm_callback+0x70/0x90
rpm_suspend+0x2f4/0x564
rpm_idle+0x3c0/0x3d8
pm_runtime_work+0x6c/0xa0
process_one_work+0x38c/0x634
worker_thread+0x218/0x360
kthread+0x130/0x138
ret_from_fork+0x10/0x18
---
Thus:
Tested-by: Douglas Anderson <dianders@chromium.org>
>
> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c b/drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c
> index fd9c893..902bb4c 100644
> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c
> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c
> @@ -156,18 +156,15 @@ static void dpu_mdss_destroy(struct drm_device *dev)
> struct dpu_mdss *dpu_mdss = to_dpu_mdss(priv->mdss);
> struct dss_module_power *mp = &dpu_mdss->mp;
>
> + pm_runtime_disable(dev->dev);
> _dpu_mdss_irq_domain_fini(dpu_mdss);
> -
> free_irq(platform_get_irq(pdev, 0), dpu_mdss);
> -
> msm_dss_put_clk(mp->clk_config, mp->num_clk);
> devm_kfree(&pdev->dev, mp->clk_config);
>
> if (dpu_mdss->mmio)
> devm_iounmap(&pdev->dev, dpu_mdss->mmio);
> dpu_mdss->mmio = NULL;
> -
> - pm_runtime_disable(dev->dev);
> priv->mdss = NULL;
> }
>
> --
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> a Linux Foundation Collaborative Project
>
_______________________________________________
Freedreno mailing list
Freedreno@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/freedreno
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH v2] drm/msm/dpu: Correct dpu destroy and disable order
[not found] ` <1541162957-12796-1-git-send-email-jshekhar-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
` (2 preceding siblings ...)
2018-11-05 19:31 ` Doug Anderson
@ 2018-11-09 6:07 ` Rajendra Nayak
[not found] ` <a2c1906e-f61d-3da2-45a4-3bc14c4201dd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
3 siblings, 1 reply; 6+ messages in thread
From: Rajendra Nayak @ 2018-11-09 6:07 UTC (permalink / raw)
To: Jayant Shekhar, dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW,
linux-arm-msm-u79uwXL29TY76Z2rM5mHXA,
freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW,
devicetree-u79uwXL29TY76Z2rM5mHXA
Cc: abhinavk-sgV2jX0FEOL9JmXXK+q4OQ,
robdclark-Re5JQEeQqe8AvxtiuMwx3w, nganji-sgV2jX0FEOL9JmXXK+q4OQ,
seanpaul-F7+t8E8rja9g9hUCZPvPmw, jsanka-sgV2jX0FEOL9JmXXK+q4OQ,
hoegsberg-F7+t8E8rja9g9hUCZPvPmw,
chandanu-sgV2jX0FEOL9JmXXK+q4OQ
On 11/2/2018 6:19 PM, Jayant Shekhar wrote:
> In case of msm drm bind failure, dpu_mdss_destroy is triggered.
> In this function, resources are freed and pm runtime disable is
> called, which triggers dpu_mdss_disable. Now in dpu_mdss_disable,
> driver tries to access a memory which is already freed. This
> results in kernel panic. Fix this by ensuring proper sequence
> of dpu destroy and disable calls.
>
> Changes in v2:
> - Removed double spacings [Jeykumar]
>
> Signed-off-by: Jayant Shekhar <jshekhar@codeaurora.org>
I was testing this patch out and in my setup I see that with this
change, during a dsi probe defer case, a dpu_mdss_enable() is called
followed by a dpu_mdss_destroy() but dpu_mdss_disable() is never called.
This results in a mismatch in clock usecount causing the mdp clocks to
stay enabled even with display turned off.
localhost ~ # cat /sys/kernel/debug/clk/clk_summary | grep mdss
disp_cc_mdss_rscc_ahb_clk 0 0 0 0 0 0 50000
disp_cc_mdss_axi_clk 0 0 0 0 0 0 50000
disp_cc_mdss_ahb_clk 0 0 0 0 0 0 50000
disp_cc_mdss_mdp_clk_src 1 1 0 19200000 0 0 50000
disp_cc_mdss_mdp_lut_clk 0 0 0 19200000 0 0 50000
disp_cc_mdss_mdp_clk 1 1 0 19200000 0 0 50000
disp_cc_mdss_vsync_clk_src 0 0 0 19200000 0 0 50000
Also to note, on an older 4.14 kernel, I do not see any issue in the order in which
these functions are called in the dsi probe defer case, i.e its an enable followed by
a disable and then a destroy (and that's without this patch)
> ---
> drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c b/drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c
> index fd9c893..902bb4c 100644
> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c
> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c
> @@ -156,18 +156,15 @@ static void dpu_mdss_destroy(struct drm_device *dev)
> struct dpu_mdss *dpu_mdss = to_dpu_mdss(priv->mdss);
> struct dss_module_power *mp = &dpu_mdss->mp;
>
> + pm_runtime_disable(dev->dev);
> _dpu_mdss_irq_domain_fini(dpu_mdss);
> -
> free_irq(platform_get_irq(pdev, 0), dpu_mdss);
> -
> msm_dss_put_clk(mp->clk_config, mp->num_clk);
> devm_kfree(&pdev->dev, mp->clk_config);
>
> if (dpu_mdss->mmio)
> devm_iounmap(&pdev->dev, dpu_mdss->mmio);
> dpu_mdss->mmio = NULL;
> -
> - pm_runtime_disable(dev->dev);
> priv->mdss = NULL;
> }
>
>
_______________________________________________
Freedreno mailing list
Freedreno@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/freedreno
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH v2] drm/msm/dpu: Correct dpu destroy and disable order
[not found] ` <a2c1906e-f61d-3da2-45a4-3bc14c4201dd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
@ 2018-11-13 15:40 ` Sean Paul
0 siblings, 0 replies; 6+ messages in thread
From: Sean Paul @ 2018-11-13 15:40 UTC (permalink / raw)
To: Rajendra Nayak
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA,
linux-arm-msm-u79uwXL29TY76Z2rM5mHXA,
abhinavk-sgV2jX0FEOL9JmXXK+q4OQ, Jayant Shekhar,
robdclark-Re5JQEeQqe8AvxtiuMwx3w, nganji-sgV2jX0FEOL9JmXXK+q4OQ,
seanpaul-F7+t8E8rja9g9hUCZPvPmw,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW,
jsanka-sgV2jX0FEOL9JmXXK+q4OQ,
freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW,
hoegsberg-F7+t8E8rja9g9hUCZPvPmw,
chandanu-sgV2jX0FEOL9JmXXK+q4OQ
On Fri, Nov 09, 2018 at 11:37:17AM +0530, Rajendra Nayak wrote:
>
> On 11/2/2018 6:19 PM, Jayant Shekhar wrote:
> > In case of msm drm bind failure, dpu_mdss_destroy is triggered.
> > In this function, resources are freed and pm runtime disable is
> > called, which triggers dpu_mdss_disable. Now in dpu_mdss_disable,
> > driver tries to access a memory which is already freed. This
> > results in kernel panic. Fix this by ensuring proper sequence
> > of dpu destroy and disable calls.
> >
> > Changes in v2:
> > - Removed double spacings [Jeykumar]
> >
> > Signed-off-by: Jayant Shekhar <jshekhar@codeaurora.org>
>
> I was testing this patch out and in my setup I see that with this
> change, during a dsi probe defer case, a dpu_mdss_enable() is called
> followed by a dpu_mdss_destroy() but dpu_mdss_disable() is never called.
>
> This results in a mismatch in clock usecount causing the mdp clocks to
> stay enabled even with display turned off.
This suggests an unmatched pm_runtime_get/put. I just audited the code and
nothing stuck out to me in the probe defer case, things seem to be well matched.
Could you instrument the pm_runtime_* calls in msm/dpu and see if there's a _get
without a _put?
Sean
>
> localhost ~ # cat /sys/kernel/debug/clk/clk_summary | grep mdss
> disp_cc_mdss_rscc_ahb_clk 0 0 0 0 0 0 50000
> disp_cc_mdss_axi_clk 0 0 0 0 0 0 50000
> disp_cc_mdss_ahb_clk 0 0 0 0 0 0 50000
> disp_cc_mdss_mdp_clk_src 1 1 0 19200000 0 0 50000
> disp_cc_mdss_mdp_lut_clk 0 0 0 19200000 0 0 50000
> disp_cc_mdss_mdp_clk 1 1 0 19200000 0 0 50000
> disp_cc_mdss_vsync_clk_src 0 0 0 19200000 0 0 50000
>
> Also to note, on an older 4.14 kernel, I do not see any issue in the order in which
> these functions are called in the dsi probe defer case, i.e its an enable followed by
> a disable and then a destroy (and that's without this patch)
>
> > ---
> > drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c | 5 +----
> > 1 file changed, 1 insertion(+), 4 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c b/drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c
> > index fd9c893..902bb4c 100644
> > --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c
> > +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c
> > @@ -156,18 +156,15 @@ static void dpu_mdss_destroy(struct drm_device *dev)
> > struct dpu_mdss *dpu_mdss = to_dpu_mdss(priv->mdss);
> > struct dss_module_power *mp = &dpu_mdss->mp;
> > + pm_runtime_disable(dev->dev);
> > _dpu_mdss_irq_domain_fini(dpu_mdss);
> > -
> > free_irq(platform_get_irq(pdev, 0), dpu_mdss);
> > -
> > msm_dss_put_clk(mp->clk_config, mp->num_clk);
> > devm_kfree(&pdev->dev, mp->clk_config);
> > if (dpu_mdss->mmio)
> > devm_iounmap(&pdev->dev, dpu_mdss->mmio);
> > dpu_mdss->mmio = NULL;
> > -
> > - pm_runtime_disable(dev->dev);
> > priv->mdss = NULL;
> > }
> >
> _______________________________________________
> Freedreno mailing list
> Freedreno@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/freedreno
--
Sean Paul, Software Engineer, Google / Chromium OS
_______________________________________________
Freedreno mailing list
Freedreno@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/freedreno
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2018-11-13 15:40 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-11-02 12:49 [PATCH v2] drm/msm/dpu: Correct dpu destroy and disable order Jayant Shekhar
[not found] ` <1541162957-12796-1-git-send-email-jshekhar-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-11-02 13:15 ` Sean Paul
2018-11-02 14:32 ` Jordan Crouse
2018-11-05 19:31 ` Doug Anderson
2018-11-09 6:07 ` Rajendra Nayak
[not found] ` <a2c1906e-f61d-3da2-45a4-3bc14c4201dd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-11-13 15:40 ` Sean Paul
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.