Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20211025144345.267107-1-tadeusz.struk@linaro.org>
 <CALAqxLXjh9o925G9smW+uwWqKDarsvrBuzr+UL1CsQc4m7W+oQ@mail.gmail.com> <5c3d9b0a-8c68-feec-74b6-59f2e29b1d11@linaro.org>
In-Reply-To: <5c3d9b0a-8c68-feec-74b6-59f2e29b1d11@linaro.org>
From:   John Stultz <john.stultz@linaro.org>
Date:   Wed, 27 Oct 2021 19:36:56 -0700
Message-ID: <CALAqxLVn0ZARrj1Syvie30Tw__NdNN4-KUCdm8wSfc9aWha3kQ@mail.gmail.com>
Subject: Re: [PATCH] media: venus: Synchronize probe() between venus_core and enc/dec
To:     Tadeusz Struk <tadeusz.struk@linaro.org>
Cc:     Stanimir Varbanov <stanimir.varbanov@linaro.org>,
        Andy Gross <agross@kernel.org>,
        Bjorn Andersson <bjorn.andersson@linaro.org>,
        Mauro Carvalho Chehab <mchehab@kernel.org>,
        Lee Jones <lee.jones@linaro.org>,
        Amit Pundir <amit.pundir@linaro.org>,
        linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
        linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Wed, Oct 27, 2021 at 5:19 PM Tadeusz Struk <tadeusz.struk@linaro.org> wrote:
>
> Hi John,
> On 10/27/21 17:01, John Stultz wrote:
> >    Thanks so much for sending this out, I definitely would like to see
> > these crashes sorted!
> >
> > Unfortunately this patch causes some odd behavior when I use it with a
> > modular config.  The display does not start up and trying to reboot
> > the board ends up with it hanging instead of rebooting.
> >
> > And booting with this patch in my non-modular config, it just seems to
> > get stuck during bootup (I suspect waiting on firmware that's not yet
> > mounted?).
> >
>
> Thanks for trying the patch. With this patch I was able to boot android13
> running 5.15.0-rc4-mainlineon on my Dragonboard 845c with the default
> config common/build.config.db845c. Without it it was crashing.

Hrm.. For my module enabled build I'm using the current
android-mainline as well w/ AOSP.

Still seeing some odd behavior, but I'm trying to isolate what change
in your patch is causing it (as it's not obvious).

thanks
-john