dt-bindings: imx: gpcv2: add support for optional resets
For some domains the resets of the devices in the domain are not automatically triggered. Add an optional resets property to allow the GPC driver to trigger those resets explicitly. The resets belong to devices located inside the power domain, which need to be held in reset across the power-up sequence. So we have no means to specify what each reset is in a generic power-domain binding. Same situation as with the clocks in this binding actually. Tested-by: Frieder Schrempf <frieder.schrempf@kontron.de> Signed-off-by: Lucas Stach <l.stach@pengutronix.de> Signed-off-by: Peng Fan <peng.fan@nxp.com> Reviewed-by: Rob Herring <robh@kernel.org> Signed-off-by: Shawn Guo <shawnguo@kernel.org>
This commit is contained in:
parent
db34eb5cc4
commit
7ba861fff0
1 changed files with 10 additions and 0 deletions
|
|
@ -66,6 +66,16 @@ properties:
|
|||
|
||||
power-supply: true
|
||||
|
||||
resets:
|
||||
description: |
|
||||
A number of phandles to resets that need to be asserted during
|
||||
power-up sequencing of the domain. The resets belong to devices
|
||||
located inside the power domain, which need to be held in reset
|
||||
across the power-up sequence. So no means to specify what each
|
||||
reset is in a generic power-domain binding.
|
||||
minItems: 1
|
||||
maxItems: 4
|
||||
|
||||
required:
|
||||
- '#power-domain-cells'
|
||||
- reg
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue