linux-kernel - Re: [PATCH v4 7/8] arm64: dts: Add ipq5018 SoC and rdp432-c2 board support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 12 May 2023 13:12:12 +0530
From:   Sricharan Ramabadhran <quic_srichara@...cinc.com>
To:     Robert Marko <robimarko@...il.com>
CC:     <agross@...nel.org>, <andersson@...nel.org>,
        <konrad.dybcio@...aro.org>, <robh+dt@...nel.org>,
        <krzysztof.kozlowski+dt@...aro.org>, <mturquette@...libre.com>,
        <sboyd@...nel.org>, <ulf.hansson@...aro.org>,
        <linus.walleij@...aro.org>, <catalin.marinas@....com>,
        <will@...nel.org>, <p.zabel@...gutronix.de>,
        <linux-arm-msm@...r.kernel.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <linux-mmc@...r.kernel.org>,
        <linux-gpio@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v4 7/8] arm64: dts: Add ipq5018 SoC and rdp432-c2 board
 support



On 5/11/2023 4:29 PM, Robert Marko wrote:
> On Thu, 11 May 2023 at 12:54, Sricharan Ramabadhran
> <quic_srichara@...cinc.com> 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.
> 

  Infact, no workaround. Only way is to add those additional SCM calls.
  That said, i will add this in the commit log here.

Regards,
  Sricharan