mirror of
https://github.com/torvalds/linux.git
synced 2026-04-18 23:03:57 -04:00
Pull devicetree updates from Rob Herring:
"Bindings:
- Convert Qcom IOMMU, Amlogic timer, Freescale sec-v4.0, Toshiba
TC358764 display bridge, Parade PS8622 display bridge, and Xilinx
FPGA bindings to DT schema format
- Add qdu1000 and sa8775p SoC support to Qcom PDC interrupt
controller
- Add MediaTek MT8365 UART and SYSIRQ bindings
- Add Arm Cortex-A78C and X1C core compatibles
- Add vendor prefix for Novatek
- Remove bindings for stih415, sti416, stid127 platforms
- Drop uneeded quotes in schema files. This is preparation for
yamllint checking quoting for us.
- Add missing (unevaluated|additional)Properties constraints on child
node schemas
- Clean-up schema comments formatting
- Fix I2C and SPI node bus names in schema examples
- Clean-up some display compatibles schema syntax
- Fix incorrect references to lvds.yaml
- Gather all cache controller bindings in a common directory
DT core:
- Convert unittest to new void .remove platform device hook
- kerneldoc fixes for DT address of_pci_range_to_resource/
of_address_to_resource functions"
* tag 'devicetree-for-6.4-1' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux: (46 commits)
dt-bindings: rng: Drop unneeded quotes
dt-bindings: arm/soc: mediatek: Drop unneeded quotes
dt-bindings: soc: qcom: Drop unneeded quotes
dt-bindings: i2c: samsung: Fix 'deprecated' value
dt-bindings: display: Fix lvds.yaml references
dt-bindings: display: simplify compatibles syntax
dt-bindings: display: mediatek: simplify compatibles syntax
dt-bindings: drm/bridge: ti-sn65dsi86: Fix the video-interfaces.yaml references
dt-bindings: timer: Drop unneeded quotes
dt-bindings: interrupt-controller: qcom,pdc: document qcom,qdu1000-pdc
dt-bindings: interrupt-controller: qcom-pdc: add compatible for sa8775p
dt-bindings: reset: remove stih415/stih416 reset
dt-bindings: net: dwmac: sti: remove stih415/sti416/stid127
dt-bindings: irqchip: sti: remove stih415/stih416 and stid127
dt-bindings: iommu: Convert QCOM IOMMU to YAML
dt-bindings: irqchip: ti,sci-inta: Add optional power-domains property
dt-bindings: Add missing (unevaluated|additional)Properties on child node schemas
of: address: Reshuffle to remove forward declarations
of: address: Fix documented return value of of_pci_range_to_resource()
of: address: Document return value of of_address_to_resource()
...
157 lines
5.6 KiB
YAML
157 lines
5.6 KiB
YAML
# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
|
|
%YAML 1.2
|
|
---
|
|
$id: http://devicetree.org/schemas/regulator/rohm,bd71847-regulator.yaml#
|
|
$schema: http://devicetree.org/meta-schemas/core.yaml#
|
|
|
|
title: ROHM BD71847 and BD71850 Power Management Integrated Circuit regulators
|
|
|
|
maintainers:
|
|
- Matti Vaittinen <mazziesaccount@gmail.com>
|
|
|
|
description: |
|
|
List of regulators provided by this controller. BD71847 regulators node
|
|
should be sub node of the BD71847 MFD node. See BD71847 MFD bindings at
|
|
Documentation/devicetree/bindings/mfd/rohm,bd71847-pmic.yaml
|
|
Regulator nodes should be named to BUCK_<number> and LDO_<number>. The
|
|
definition for each of these nodes is defined using the standard
|
|
binding for regulators at
|
|
Documentation/devicetree/bindings/regulator/regulator.txt.
|
|
Note that if BD71847 starts at RUN state you probably want to use
|
|
regulator-boot-on at least for BUCK5. LDO6 is supplied by it and it must
|
|
not be disabled by driver at startup. If BUCK5 is disabled at startup the
|
|
voltage monitoring for LDO5/LDO6 can cause PMIC to reset.
|
|
|
|
# The valid names for BD71847 regulator nodes are:
|
|
# BUCK1, BUCK2, BUCK3, BUCK4, BUCK5, BUCK6
|
|
# LDO1, LDO2, LDO3, LDO4, LDO5, LDO6
|
|
|
|
patternProperties:
|
|
"^LDO[1-6]$":
|
|
type: object
|
|
$ref: regulator.yaml#
|
|
description:
|
|
Properties for single LDO regulator.
|
|
|
|
properties:
|
|
regulator-name:
|
|
pattern: "^ldo[1-6]$"
|
|
description:
|
|
should be "ldo1", ..., "ldo6"
|
|
|
|
unevaluatedProperties: false
|
|
|
|
"^BUCK[1-6]$":
|
|
type: object
|
|
$ref: regulator.yaml#
|
|
description:
|
|
Properties for single BUCK regulator.
|
|
|
|
properties:
|
|
regulator-name:
|
|
pattern: "^buck[1-6]$"
|
|
description:
|
|
should be "buck1", ..., "buck6"
|
|
|
|
rohm,dvs-run-voltage:
|
|
$ref: /schemas/types.yaml#/definitions/uint32
|
|
minimum: 0
|
|
maximum: 1300000
|
|
description:
|
|
PMIC default "RUN" state voltage in uV. See below table for
|
|
bucks which support this. 0 means disabled.
|
|
|
|
rohm,dvs-idle-voltage:
|
|
$ref: /schemas/types.yaml#/definitions/uint32
|
|
minimum: 0
|
|
maximum: 1300000
|
|
description:
|
|
PMIC default "IDLE" state voltage in uV. See below table for
|
|
bucks which support this. 0 means disabled.
|
|
|
|
rohm,dvs-suspend-voltage:
|
|
$ref: /schemas/types.yaml#/definitions/uint32
|
|
minimum: 0
|
|
maximum: 1300000
|
|
description:
|
|
PMIC default "SUSPEND" state voltage in uV. See below table for
|
|
bucks which support this. 0 means disabled.
|
|
|
|
# Supported default DVS states:
|
|
#
|
|
# BD71847:
|
|
# buck | dvs-run-voltage | dvs-idle-voltage | dvs-suspend-voltage
|
|
# ----------------------------------------------------------------
|
|
# 1 | supported | supported | supported
|
|
# ----------------------------------------------------------------
|
|
# 2 | supported | supported | not supported
|
|
# ----------------------------------------------------------------
|
|
# rest | not supported | not supported | not supported
|
|
|
|
# BD718(47/50) power outputs can either be controlled by the PMIC internal
|
|
# hardware state machine or by software. If you need regulators to be
|
|
# turned ON/OFF for example based on PMIC_STBY_REQ line (which toggles
|
|
# PMIC HW state machine) - then you should set this property.
|
|
# Tradeoff is that then SW can't control the ON/OFF state for this
|
|
# regulator (other than invoking a PMIC state change).
|
|
rohm,no-regulator-enable-control:
|
|
description: |
|
|
Enable/Disable control of this regulator must be left to the
|
|
PMIC hardware state machine.
|
|
type: boolean
|
|
|
|
# Setups where regulator (especially the buck8) output voltage is scaled
|
|
# by adding external connection where some other regulator output is
|
|
# connected to feedback-pin (over suitable resistors) is getting popular
|
|
# amongst users of BD71837. (This allows for example scaling down the
|
|
# buck8 voltages to suit lover GPU voltages for projects where buck8 is
|
|
# (ab)used to supply power for GPU.
|
|
#
|
|
# So we allow describing this external connection from DT and scale the
|
|
# voltages accordingly. This is what the connection should look like:
|
|
#
|
|
# |---------------|
|
|
# | buck 8 |-------+----->Vout
|
|
# | | |
|
|
# |---------------| |
|
|
# | |
|
|
# | |
|
|
# +-------+--R2----+
|
|
# |
|
|
# R1
|
|
# |
|
|
# V FB-pull-up
|
|
#
|
|
# Here the buck output is sifted according to formula:
|
|
#
|
|
# Vout_o = Vo - (Vpu - Vo)*R2/R1
|
|
# Linear_step = step_orig*(R1+R2)/R1
|
|
#
|
|
# where:
|
|
# Vout_o is adjusted voltage output at vsel reg value 0
|
|
# Vo is original voltage output at vsel reg value 0
|
|
# Vpu is the pull-up voltage V FB-pull-up in the picture
|
|
# R1 and R2 are resistor values.
|
|
|
|
rohm,fb-pull-up-microvolt:
|
|
description:
|
|
Feedback-pin has pull-up connection to adjust voltage range. This is
|
|
the used pull-up voltage before R1.
|
|
|
|
rohm,feedback-pull-up-r1-ohms:
|
|
description:
|
|
Feedback-pin has pull-up connection to adjust voltage range. This is
|
|
the used R1 resistor.
|
|
|
|
rohm,feedback-pull-up-r2-ohms:
|
|
description:
|
|
Feedback-pin has pull-up connection to adjust voltage range. This is
|
|
the used R2 resistor.
|
|
|
|
required:
|
|
- regulator-name
|
|
|
|
unevaluatedProperties: false
|
|
|
|
additionalProperties: false
|