Hi, On Mon, Nov 09, 2026 at 04:47:29PM +0100, Ulf Hansson wrote: > On Thu, Oct 29, 2026 at 10:01 AM Shivendra Pratap > wrote: > > > > Userspace should be able to initiate device reboots using the various > > PSCI SYSTEM_RESET and SYSTEM_RESET2 types defined by PSCI spec. This > > patch series introduces psci-reboot-mode driver that will induce > > command-based resets to psci driver for executing the device reset. > > > > The PSCI system reset calls takes two arguments: reset_type and cookie. > > It defines predefined reset types, such as warm and cold reset, and > > vendor-specific reset types which are SoC vendor specific. To support > > these requirements, the reboot-mode framework is enhanced in two key > > ways: > > 1. Support upto three 32 bit magic values as arguments. This enables to > > support for a 32 bit reset_type and a 64 bit cookie). > > 2. Predefined modes: Add support for predefined reboot modes in the > > framework. > > > > With these enhancements, the patch series enables: > > - Arch Warm reset and system reset cold as predefined reboot modes. > > - Vendor-specific resets, configurable via the SoC-specific device tree. > > > > Together, these changes allow userspace to trigger all above PSCI resets > > from userspace. > > > > Note on introducing psci aux devices: > > Based on feedback from Bart, Lee and Ufee, PSCI child functionality now > > uses aux devices instead of an MFD driver, with psci-cpuidle-domain and > > psci-reboot-mode probed through a common PSCI aux device enumerator. > > Reference discussions on this: > > https://lore.kernel.org/all/CAPx+jO9Hi2R_UnCEhsXLwf74c3RTb+RodaJ6SOVXbQX_eHt++A@mail.gmail.com/ > > > > --- > > The patch is tested on rb3Gen2, lemans-ride, lemans-evk, monaco-ride, > > qcs615-ride. > > > > Signed-off-by: Shivendra Pratap > > > > Changes in v27: > > - Removed unnecessary headers from psci-reboot-mode - By Bart > > - Rebased onto current linux-next. > > - Link to v26: https://patch.msgid.link/20260928-arm-psci-system_reset2-vendor-reboots-v26-0-b24e2348e8e1@oss.qualcomm.com > > Overall this looks reasonable to me, but I will take a closer look in > the next few days. > > When it comes to the merging strategy, it seems like the best way > would be to funnel this via my pmdomain tree. But I need an ack from > the relevant maintainers to make sure there are no issues with that. Works for me. Greetings, -- Sebastian