linux-kernel - Re: (subset) [PATCH v8 0/6] Implement vendor resets for PSCI SYSTEM

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]

Message-Id: <173136321437.772650.9632330958815794111.b4-ty@collabora.com>
Date: Mon, 11 Nov 2024 23:13:34 +0100
From: Sebastian Reichel <sebastian.reichel@...labora.com>
To: Bjorn Andersson <andersson@...nel.org>, 
 Sebastian Reichel <sre@...nel.org>, Rob Herring <robh@...nel.org>, 
 Conor Dooley <conor+dt@...nel.org>, Vinod Koul <vkoul@...nel.org>, 
 Andy Yan <andy.yan@...k-chips.com>, 
 Lorenzo Pieralisi <lpieralisi@...nel.org>, 
 Mark Rutland <mark.rutland@....com>, 
 Bartosz Golaszewski <bartosz.golaszewski@...aro.org>, 
 Arnd Bergmann <arnd@...db.de>, Olof Johansson <olof@...om.net>, 
 Catalin Marinas <catalin.marinas@....com>, Will Deacon <will@...nel.org>, 
 cros-qcom-dts-watchers@...omium.org, 
 Krzysztof Kozlowski <krzk+dt@...nel.org>, 
 Konrad Dybcio <konradybcio@...nel.org>, 
 Konrad Dybcio <konradybcio@...nel.org>, 
 Elliot Berman <quic_eberman@...cinc.com>
Cc: Satya Durga Srinivasu Prabhala <quic_satyap@...cinc.com>, 
 Melody Olvera <quic_molvera@...cinc.com>, 
 Shivendra Pratap <quic_spratap@...cinc.com>, devicetree@...r.kernel.org, 
 linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, 
 Florian Fainelli <florian.fainelli@...adcom.com>, 
 Stephen Boyd <swboyd@...omium.org>, linux-pm@...r.kernel.org, 
 linux-arm-msm@...r.kernel.org
Subject: Re: (subset) [PATCH v8 0/6] Implement vendor resets for PSCI
 SYSTEM_RESET2


On Thu, 07 Nov 2024 15:38:24 -0800, Elliot Berman wrote:
> The PSCI SYSTEM_RESET2 call allows vendor firmware to define additional
> reset types which could be mapped to the reboot argument.
> 
> Setting up reboot on Qualcomm devices can be inconsistent from chipset
> to chipset. Generally, there is a PMIC register that gets written to
> decide the reboot type. There is also sometimes a cookie that can be
> written to indicate that the bootloader should behave differently than a
> regular boot. These knobs evolve over product generations and require
> more drivers. Qualcomm firmwares are beginning to expose vendor
> SYSTEM_RESET2 types to simplify driver requirements from Linux.
> 
> [...]

Applied, thanks!

[1/6] dt-bindings: power: reset: Convert mode-.* properties to array
      commit: 05d9044177c3e910921522e0209640d3b825a6ae

Best regards,
-- 
Sebastian Reichel <sebastian.reichel@...labora.com>