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: <20210902214708.1776690-1-robimarko@gmail.com> <YUf3aKn78+41Cb/G@builder.lan>
 <CAOX2RU5b46H7nqm6G4mHLSqEhGiWktwWjUKF5w10Ut+AdKea-A@mail.gmail.com>
 <632a7d28c23a8497d35ea009bfe89883@codeaurora.org> <CAOX2RU5+jeXiqz8oss8Sd-BWa059uAv5xu=7nx_YF4RYpG2S6w@mail.gmail.com>
 <YUurqDL/S15RziCQ@builder.lan> <20211006182419.GC33862@thinkpad>
 <CAOX2RU43D72yx1Kyb0jRMMOLgBd1OMscWLH-dEdp0P=L-5quHQ@mail.gmail.com> <20211006184404.GD33862@thinkpad>
In-Reply-To: <20211006184404.GD33862@thinkpad>
From:   Robert Marko <robimarko@gmail.com>
Date:   Wed, 6 Oct 2021 21:09:31 +0200
Message-ID: <CAOX2RU44mp2MfbEsjziV_X7SdO1wf+ptPbF-51Tc8FPzQcozJw@mail.gmail.com>
Subject: Re: [PATCH] arm64: dts: qcom: ipq8074: add SMEM support
To:     Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc:     Bjorn Andersson <bjorn.andersson@linaro.org>,
        Kathiravan T <kathirav@codeaurora.org>, agross@kernel.org,
        robh+dt@kernel.org, linux-arm-msm@vger.kernel.org,
        devicetree@vger.kernel.org,
        open list <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Wed, 6 Oct 2021 at 20:44, Manivannan Sadhasivam
<manivannan.sadhasivam@linaro.org> wrote:
>
> On Wed, Oct 06, 2021 at 08:26:10PM +0200, Robert Marko wrote:
> > On Wed, 6 Oct 2021 at 20:24, Manivannan Sadhasivam
> > <manivannan.sadhasivam@linaro.org> wrote:
> > >
>
> [...]
>
> > > Sorry, missed this earlier. I did face the probe deferral issue before and
> > > submitted a small series for fixing that:
> > >
> > > https://lore.kernel.org/linux-mtd/20210302132757.225395-1-manivannan.sadhasivam@linaro.org/
> > >
> > > These 2 patches are in mainline now. Robert, can you make sure that you have
> > > these 2 patches in your tree?
> >
> > Hi Mani,
> > Yes, I have those patches as I am running this on top of 5.15-rc4 currently.
> >
>
> Hmm. So if both SMEM and NAND drivers are added to the probe deferral list then
> the issue is likely not related to probe ordering.
>
> Can you nail down the point where the board starts rebooting?

Unfortunately not, I can see that it resets after the NAND driver
requesting probe deferral but I cannot pinpoint the exact thing that
resets it
as there is no stack trace.

Regards,
Robert
>
> Thanks,
> Mani
>
> > Regards,
> > Robert
> > >
> > > Thanks,
> > > Mani
> > >
> > > > Thanks,
> > > > Bjorn