All of lore.kernel.org
 help / color / mirror / Atom feed
From: abhinavk@codeaurora.org
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
	Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
	Jonathan Marek <jonathan@marek.ca>,
	Stephen Boyd <sboyd@kernel.org>, David Airlie <airlied@linux.ie>,
	Daniel Vetter <daniel@ffwll.ch>,
	"open list:DRM DRIVER FOR MSM ADRENO GPU" 
	<linux-arm-msm@vger.kernel.org>,
	"open list:DRM DRIVER FOR MSM ADRENO GPU" 
	<dri-devel@lists.freedesktop.org>,
	freedreno <freedreno@lists.freedesktop.org>,
	David Heidelberg <david@ixit.cz>
Subject: Re: [Freedreno] [PATCH] drm/msm/dsi: do not install irq handler before power up the host
Date: Mon, 27 Sep 2021 18:19:26 -0700	[thread overview]
Message-ID: <1ebb9efd461e9a84027ea63f7141a208@codeaurora.org> (raw)
In-Reply-To: <CAA8EJpqvNJudg8-PActLEYf-BgmnJD3N7a4pMqb8VNf4hFiHdw@mail.gmail.com>

On 2021-09-27 18:06, Dmitry Baryshkov wrote:
> On Tue, 28 Sept 2021 at 03:22, <abhinavk@codeaurora.org> wrote:
>> 
>> On 2021-09-25 12:43, Dmitry Baryshkov wrote:
>> > On 21/09/2021 23:52, abhinavk@codeaurora.org wrote:
>> >> On 2021-09-21 10:47, Dmitry Baryshkov wrote:
>> >>> Hi,
>> >>>
>> >>> On Tue, 21 Sept 2021 at 20:01, <abhinavk@codeaurora.org> wrote:
>> >>>>
>> >>>> On 2021-09-21 09:22, Dmitry Baryshkov wrote:
>> >>>> > The DSI host might be left in some state by the bootloader. If this
>> >>>> > state generates an IRQ, it might hang the system by holding the
>> >>>> > interrupt line before the driver sets up the DSI host to the known
>> >>>> > state.
>> >>>> >
>> >>>> > Move the request/free_irq calls into msm_dsi_host_power_on/_off calls,
>> >>>> > so that we can be sure that the interrupt is delivered when the host is
>> >>>> > in the known state.
>> >>>> >
>> >>>> > Fixes: a689554ba6ed ("drm/msm: Initial add DSI connector support")
>> >>>> > Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>> >>>>
>> >>>> This is a valid change and we have seen interrupt storms in
>> >>>> downstream
>> >>>> happening
>> >>>> when like you said the bootloader leaves the DSI host in unknown
>> >>>> state.
>> >>>> Just one question below.
>> >>>>
>> >>>> > ---
>> >>>> >  drivers/gpu/drm/msm/dsi/dsi_host.c | 21 ++++++++++++---------
>> >>>> >  1 file changed, 12 insertions(+), 9 deletions(-)
>> >>>> >
>> >>>> > diff --git a/drivers/gpu/drm/msm/dsi/dsi_host.c
>> >>>> > b/drivers/gpu/drm/msm/dsi/dsi_host.c
>> >>>> > index e269df285136..cd842347a6b1 100644
>> >>>> > --- a/drivers/gpu/drm/msm/dsi/dsi_host.c
>> >>>> > +++ b/drivers/gpu/drm/msm/dsi/dsi_host.c
>> >>>> > @@ -1951,15 +1951,6 @@ int msm_dsi_host_modeset_init(struct
>> >>>> > mipi_dsi_host *host,
>> >>>> >               return ret;
>> >>>> >       }
>> >>>> >
>> >>>> > -     ret = devm_request_irq(&pdev->dev, msm_host->irq,
>> >>>> > -                     dsi_host_irq, IRQF_TRIGGER_HIGH | IRQF_ONESHOT,
>> >>>> > -                     "dsi_isr", msm_host);
>> >>>> > -     if (ret < 0) {
>> >>>> > -             DRM_DEV_ERROR(&pdev->dev, "failed to request IRQ%u: %d\n",
>> >>>> > -                             msm_host->irq, ret);
>> >>>> > -             return ret;
>> >>>> > -     }
>> >>>> > -
>> >>>> >       msm_host->dev = dev;
>> >>>> >       ret = cfg_hnd->ops->tx_buf_alloc(msm_host, SZ_4K);
>> >>>> >       if (ret) {
>> >>>> > @@ -2413,6 +2404,16 @@ int msm_dsi_host_power_on(struct mipi_dsi_host
>> >>>> > *host,
>> >>>> >       if (msm_host->disp_en_gpio)
>> >>>> >               gpiod_set_value(msm_host->disp_en_gpio, 1);
>> >>>> >
>> >>>> > +     ret = devm_request_irq(&msm_host->pdev->dev, msm_host->irq,
>> >>>> > +                     dsi_host_irq, IRQF_TRIGGER_HIGH | IRQF_ONESHOT,
>> >>>> > +                     "dsi_isr", msm_host);
>> >>>> > +     if (ret < 0) {
>> >>>> > +             DRM_DEV_ERROR(&msm_host->pdev->dev, "failed to request IRQ%u: %d\n",
>> >>>> > +                             msm_host->irq, ret);
>> >>>> > +             return ret;
>> >>>> > +     }
>> >>>> > +
>> >>>> > +
>> >>>>
>> >>>> Do you want to move this to msm_dsi_host_enable()?
>> >>>> So without the controller being enabled it is still in unknown
>> >>>> state?
>> >>>
>> >>> msm_dsi_host_power_on() reconfigures the host registers, so the state
>> >>> is known at the end of the power_on().
>> >>>
>> >>>> Also do you want to do this after dsi0 and dsi1 are initialized to
>> >>>> account for
>> >>>> dual dsi cases?
>> >>>
>> >>> I don't think this should matter. The host won't generate 'extra'
>> >>> interrupts in such case, will it?
>> >>>
>> >> We have seen cases where misconfiguration has caused interrupts to
>> >> storm only
>> >> on one DSI in some cases. So yes, I would prefer this is done after
>> >> both are
>> >> configured.
>> >
>> > I've checked. The power_on is called from dsi_mgr_bridge_pre_enable()
>> > when both DSI hosts should be bound.
>> 
>> DSI being bound is enough? I thought the issue we are trying to 
>> address
>> is that
>> we need to have called msm_dsi_host_power_on() for both the hosts so
>> that both are
>> put in the known state before requesting the irq.
>> 
>> OR in other words move the irq_enable() to below location.
>> 
>> 341 static void dsi_mgr_bridge_pre_enable(struct drm_bridge *bridge)
>> 342 {
>> ********************************
>> 364     ret = msm_dsi_host_power_on(host, &phy_shared_timings[id],
>> is_bonded_dsi, msm_dsi->phy);
>> 365     if (ret) {
>> 366             pr_err("%s: power on host %d failed, %d\n", __func__, 
>> id, ret);
>> 367             goto host_on_fail;
>> 368     }
>> 369
>> 370     if (is_bonded_dsi && msm_dsi1) {
>> 371             ret = msm_dsi_host_power_on(msm_dsi1->host,
>> 372                             &phy_shared_timings[DSI_1], 
>> is_bonded_dsi, msm_dsi1->phy);
>> 373             if (ret) {
>> 374                     pr_err("%s: power on host1 failed, %d\n",
>> 375                                                     __func__, 
>> ret);
>> 376                     goto host1_on_fail;
>> 377             }
>> 378     }
>> 
>> < move the irq enable here >
>> **********************************
> 
> Ah, I see your point. What about moving to msm_dsi_host_enable() then?

Yes, I had suggested this a few replies ago. But only at the dsi_msgr we 
know if DSI1 is also done.
So you can do it right after it in below location?

427 	if (is_dual_dsi && msm_dsi1) {
428 		ret = msm_dsi_host_enable(msm_dsi1->host);
429 		if (ret) {
430 			pr_err("%s: enable host1 failed, %d\n", __func__, ret);
431 			goto host1_en_fail;
432 		}
433 	}

<enable_irq here? >

> 
>> >>>> >       msm_host->power_on = true;
>> >>>> >       mutex_unlock(&msm_host->dev_mutex);
>> >>>> >
>> >>>> > @@ -2439,6 +2440,8 @@ int msm_dsi_host_power_off(struct mipi_dsi_host
>> >>>> > *host)
>> >>>> >               goto unlock_ret;
>> >>>> >       }
>> >>>> >
>> >>>> > +     devm_free_irq(&msm_host->pdev->dev, msm_host->irq, msm_host);
>> >>>> > +
>> >>>> >       dsi_ctrl_config(msm_host, false, NULL, NULL);
>> >>>> >
>> >>>> >       if (msm_host->disp_en_gpio)

  reply	other threads:[~2021-09-28  1:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20210921162311eucas1p203a8c6477b03f44887f76e99c9c60e28@eucas1p2.samsung.com>
2021-09-21 16:22 ` [PATCH] drm/msm/dsi: do not install irq handler before power up the host Dmitry Baryshkov
2021-09-21 17:00   ` [Freedreno] " abhinavk
2021-09-21 17:47     ` Dmitry Baryshkov
2021-09-21 20:52       ` abhinavk
2021-09-25 19:43         ` Dmitry Baryshkov
2021-09-28  0:22           ` abhinavk
2021-09-28  1:06             ` Dmitry Baryshkov
2021-09-28  1:19               ` abhinavk [this message]
2021-09-28  1:29                 ` Dmitry Baryshkov
2021-09-28  1:33                   ` abhinavk
2021-09-28  1:40                     ` Dmitry Baryshkov
2021-10-02  1:10                       ` Dmitry Baryshkov
2021-09-21 18:26   ` Andrzej Hajda
2021-09-25 19:44     ` Dmitry Baryshkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1ebb9efd461e9a84027ea63f7141a208@codeaurora.org \
    --to=abhinavk@codeaurora.org \
    --cc=airlied@linux.ie \
    --cc=bjorn.andersson@linaro.org \
    --cc=daniel@ffwll.ch \
    --cc=david@ixit.cz \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=jonathan@marek.ca \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=robdclark@gmail.com \
    --cc=sboyd@kernel.org \
    --cc=sean@poorly.run \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.