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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5B08DC77B7C for ; Thu, 11 May 2023 10:59:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237854AbjEKK7t (ORCPT ); Thu, 11 May 2023 06:59:49 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45812 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237540AbjEKK7o (ORCPT ); Thu, 11 May 2023 06:59:44 -0400 Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1AB2E5B84; Thu, 11 May 2023 03:59:42 -0700 (PDT) Received: by mail-pj1-x1036.google.com with SMTP id 98e67ed59e1d1-24e5d5782edso7983207a91.0; Thu, 11 May 2023 03:59:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683802781; x=1686394781; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=P7WwGv5KdS3JZFK3LNUp5MC3xbE7T89T2fedtq/0oXc=; b=N26j+VMrYeUL3Ark717FdrXcfToyaCqMS6iY+FeQsEcpY7/CRFjD3pm8JXhDkmG3rx JV0ZiQt4bw3mexLUenLy6ujL4q3ujgm8A+Ky29XFZV3Cj5OOPV1IuAYRDbLkbE8gSwNP ywrBKf0PMdL1wJ+gR09fiRNI/cpEZtY7GuL8jWl0vqi1X94S2LgmJC1/evJ1HdjdJC0K IYgieE/37snCsLXQaF8f5r4cL6BKYkUXVhwaUOBe56uWmG0bvuwHgLD/s6OIf2Tm5q8K NgRDEHB2S0dD5M7Cq5Tn85z0vO5dJ6Om9XNEau6HgDD8HJ0yPSUvBO8Z3w7n6dthvgh3 LIVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683802781; x=1686394781; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=P7WwGv5KdS3JZFK3LNUp5MC3xbE7T89T2fedtq/0oXc=; b=BItbdS9mgDU3PuCUwT91l1oKsxqHaM6N+Zpwi5SP3z7jmm6+ZJrU6NWv59CtprUrJZ pFcQlBZuHWKiYz3/vS6TRAlLoWFyT3kProSTcRyZ3bLRje4jfb1XBFshqDe7XtHCUNpW VAc4w2/RNz9zsAXoQUo+FXQBYBzsFwXd+yBZcOPQ3x1XCiEV4iXKS0Ybyes++iAFQWT4 b8Cm/N3UMJ15XZssNPTWrT5sjBId4pnXuLSFkHNzggu7PTVtPipufEGW7RPYSZW+Va/k 8rYYghqXQUz6RGEOfK//XmpHjTCl64qkJKtquAY9A/3Kn5U9eFuryxv8UfMPA11l7Xei 6d2w== X-Gm-Message-State: AC+VfDxZ19aCFhhH9EuDRmVplHosnS/hhQuUnduewqGcep2rMmxHSyhT Omml8tkuq34LywBZ4eK39rvp5MprpFs+YfxBs+0= X-Google-Smtp-Source: ACHHUZ4GERe0mUrXPvRcXq786LmJzoOQzwlw+H1gHijJA7ExVdrv/E5/FTfzxC5+hMYC4qyX3FLDtumdrE0sbuVolo4= X-Received: by 2002:a17:90b:1296:b0:24e:596:624f with SMTP id fw22-20020a17090b129600b0024e0596624fmr20866667pjb.22.1683802781153; Thu, 11 May 2023 03:59:41 -0700 (PDT) MIME-Version: 1.0 References: <20230510134121.1232286-1-quic_srichara@quicinc.com> <20230510134121.1232286-8-quic_srichara@quicinc.com> <8f5040e0-169b-554b-c9e6-479b8f098bc6@gmail.com> In-Reply-To: From: Robert Marko Date: Thu, 11 May 2023 12:59:30 +0200 Message-ID: Subject: Re: [PATCH v4 7/8] arm64: dts: Add ipq5018 SoC and rdp432-c2 board support To: Sricharan Ramabadhran Cc: agross@kernel.org, andersson@kernel.org, konrad.dybcio@linaro.org, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, mturquette@baylibre.com, sboyd@kernel.org, ulf.hansson@linaro.org, linus.walleij@linaro.org, catalin.marinas@arm.com, will@kernel.org, p.zabel@pengutronix.de, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org, linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 11 May 2023 at 12:54, Sricharan Ramabadhran wrote: > > > > On 5/11/2023 3:54 PM, Robert Marko wrote: > > > > On 10. 05. 2023. 15:41, Sricharan Ramabadhran wrote: > >> Add initial device tree support for the Qualcomm IPQ5018 SoC and > >> rdp432-c2 board. > > > > Hi, does reboot work for you with this patchset? > > I have tested on 2 different IPQ5018 boards and they wont reboot, > > I get the: > > Requesting system reboot > > [ 321.005977] qcom_scm firmware:scm: No available mechanism for setting > > download mode > > [ 321.006128] reboot: Restarting system > > > > And then it just hangs there. > > > > Yes, that is because SDI disabling using separate SCM is still not > there. I will add support for that in a separate series. Do you maybe have a workaround for this, as it's driving me crazy to have to pull power? Also, it would probably be good to note this in the commit to avoid more questions like this. Regards, Robert > > Regards, > Sricharan