From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4132BC433F5 for ; Wed, 6 Oct 2021 19:09:45 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 22DB8611C0 for ; Wed, 6 Oct 2021 19:09:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239311AbhJFTLg (ORCPT ); Wed, 6 Oct 2021 15:11:36 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47408 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239314AbhJFTLg (ORCPT ); Wed, 6 Oct 2021 15:11:36 -0400 Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 88314C061746; Wed, 6 Oct 2021 12:09:43 -0700 (PDT) Received: by mail-qt1-x82f.google.com with SMTP id r1so3714988qta.12; Wed, 06 Oct 2021 12:09:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VL8huvHNt0AW4VbvHoyUVP6MU5/wX3Bj6/diTCZsDhw=; b=nEfMYzi66QIGok2oQdVZQIYT1PqFopAy8Md5kYeZVvtvZCrh0S/5Tb9Na/zmFrVA8L 0fM47209loAcRogudkTHSmAtX7ogUbikzNDP2dCvvFEyh4NmWJX/Wmuij/pT1Hh6Blet 2iB45DdHw3DfnROu9GEetkcQpZSo/I3P3pbkJRd6q7vgvLOH8CfV7oKLIcLDGSU0LSUS kx7fKtdXj6OF0FHw3FAARnC6ueNLZErsQ24y+RY2c9rmAe3eUvt1UiOt/azZ1ZjWqara dnkNkE9ymjW9dC6u78KAJ5zy4UkX4Gf+p13asciqvMqtbK1BM4q460rO/WqAQY73sS70 7CHw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VL8huvHNt0AW4VbvHoyUVP6MU5/wX3Bj6/diTCZsDhw=; b=ynOaEen/mOv65VbopjYg7i9T+Wq3qdOqNVJi799T8bR/X8TEl2o/WtR9kZ1zM9VzzT zp+JSzehtBnp6TVTvk5EQKUdsASViCLZHWrBL2anc37zQjdk2jvydCBOzpEf9NeJppKB g+orJb2NlJxcGyB7iVLUvrsUThjfj10O2vMLQyJpg1m0rGiXrvOyqztxr5aCcRQHY0Jh ioch5stSpBfx3SkE2i5k7OovpjW7FQXGcRVeRI/mxB29etrDO3w3Z3KEHlOg5wf+wOQ+ daj+vbgLCFwtemG0NAHR6x7p1g633DnJRCq53rISQCCM0DfQ2I3tTJe6vwqK1frAbb8r CzIg== X-Gm-Message-State: AOAM531AcXDYa1vRSL50Ehbbs1jTfZIMQ0X121LPxJf0mYEtQSJ3qfVY hK6Jelgoqod9aEF57nDs0Lflt8U2+i1XQU0EPhs= X-Google-Smtp-Source: ABdhPJyuoHhYVDdnFB0RJ7H6Qb8GSeTcN1K+azR1B1QNT9f5CUZ/P8aZh1M6ZZpIf09WbGXeunb+0JQDx5QqMJvzaPk= X-Received: by 2002:ac8:4313:: with SMTP id z19mr536654qtm.356.1633547382635; Wed, 06 Oct 2021 12:09:42 -0700 (PDT) MIME-Version: 1.0 References: <20210902214708.1776690-1-robimarko@gmail.com> <632a7d28c23a8497d35ea009bfe89883@codeaurora.org> <20211006182419.GC33862@thinkpad> <20211006184404.GD33862@thinkpad> In-Reply-To: <20211006184404.GD33862@thinkpad> From: Robert Marko Date: Wed, 6 Oct 2021 21:09:31 +0200 Message-ID: Subject: Re: [PATCH] arm64: dts: qcom: ipq8074: add SMEM support To: Manivannan Sadhasivam Cc: Bjorn Andersson , Kathiravan T , agross@kernel.org, robh+dt@kernel.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, open list Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org On Wed, 6 Oct 2021 at 20:44, Manivannan Sadhasivam wrote: > > On Wed, Oct 06, 2021 at 08:26:10PM +0200, Robert Marko wrote: > > On Wed, 6 Oct 2021 at 20:24, Manivannan Sadhasivam > > 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