Reminder: Any plan how to handle these patches? On Monday 26 December 2022 12:45:11 Pali Rohár wrote: > This new optional priority property allows to specify custom priority level > of reset device. Prior this change priority level was hardcoded to 192 and > not possible to specify or change. Specifying other value is needed for > some boards. Default level when not specified stays at 192 as before. > > Signed-off-by: Pali Rohár <pali@xxxxxxxxxx> > > --- > Changes in v4: > * Use restart-handler.yaml > > Changes in v3: > * Add explanation into commit message > > Changes in v2: > * Change sint32 to int32 > * Add default > --- > .../devicetree/bindings/power/reset/syscon-reboot.yaml | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/Documentation/devicetree/bindings/power/reset/syscon-reboot.yaml b/Documentation/devicetree/bindings/power/reset/syscon-reboot.yaml > index da2509724812..f721bdf63a98 100644 > --- a/Documentation/devicetree/bindings/power/reset/syscon-reboot.yaml > +++ b/Documentation/devicetree/bindings/power/reset/syscon-reboot.yaml > @@ -19,6 +19,9 @@ description: |+ > sub-node of a "syscon", "simple-mfd" node. Though the regmap property > pointing to the system controller node is also supported. > > +allOf: > + - $ref: restart-handler.yaml# > + > properties: > compatible: > const: syscon-reboot > @@ -42,6 +45,9 @@ properties: > $ref: /schemas/types.yaml#/definitions/uint32 > description: The reset value written to the reboot register (32 bit access). > > + priority: > + default: 192 > + > required: > - compatible > - offset > -- > 2.20.1 >
