Hi Mark, I'm (hopefully) picking up the work for this series. On Mon, Jun 30, 2014 at 5:48 PM, Mark Rutland <mark.rutland@xxxxxxx> wrote: > On Sun, Jun 29, 2014 at 07:23:52PM +0100, Carlo Caione wrote: >> Bindings documentation for the AXP20x driver. In this file also >> sub-nodes are documented. >> >> Signed-off-by: Carlo Caione <carlo@xxxxxxxxxx> >> Acked-by: Maxime Ripard <maxime.ripard@xxxxxxxxxxxxxxxxxx> >> --- >> Documentation/devicetree/bindings/mfd/axp20x.txt | 93 ++++++++++++++++++++++++ >> 1 file changed, 93 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/mfd/axp20x.txt >> >> diff --git a/Documentation/devicetree/bindings/mfd/axp20x.txt b/Documentation/devicetree/bindings/mfd/axp20x.txt >> new file mode 100644 >> index 0000000..cc9e01b >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/mfd/axp20x.txt >> @@ -0,0 +1,93 @@ >> +AXP202/AXP209 device tree bindings >> + >> +The axp20x family current members :- >> +axp202 (X-Powers) >> +axp209 (X-Powers) >> + >> +Required properties: >> +- compatible: "x-powers,axp202" or "x-powers,axp209" >> +- reg: The I2C slave address for the AXP chip >> +- interrupt-parent: The parent interrupt controller >> +- interrupts: Interrupt specifiers for interrupt sources > > How many, what are they? Now reads: SoC external interrupt / NMI connected to the PMIC's IRQ pin >> +- interrupt-controller: axp20x has its own internal IRQs >> +- #interrupt-cells: Should be set to 1 >> +- acin-supply: The input supply for LDO1 >> +- vin2-supply: The input supply for DCDC2 >> +- vin3-supply: The input supply for DCDC3 >> +- ldo24in-supply: The input supply for LDO2, LDO4 >> +- ldo3in-supply: The input supply for LDO3 >> +- ldo5in-supply: The input supply for LDO5 >> + >> +- regulators: A node that houses a sub-node for each regulator. The regulators are >> + bound using their name as listed here: dcdc2, dcdc3, ldo1, ldo2, >> + ldo3, ldo4, ldo5. The bindings details of individual regulator >> + device can be found in: >> + Documentation/devicetree/bindings/regulator/regulator.txt with >> + the exception of x-powers,dcdc-freq >> +- x-powers,dcdc-freq: defines the work frequency of DC-DC in KHz >> + (range: 750-1875). Default: 1.5MHz >> + >> +Optional properties for DCDCs: >> +- x-powers,dcdc-workmode: 1 for PWM mode, 0 for AUTO mode >> + Default: AUTO mode > > When would I want to select PWM mode, and why should this be in the DT? Expanded description: """ The DCDC regulators work in a mixed PWM/PFM mode, using PFM under light loads and switching to PWM for heavier loads. Forcing PWM mode trades efficiency under light loads for lower output noise. This probably makes sense for HiFi audio related applications that aren't battery constrained. """ As I'm not an electronics person, I really can't say under what circumstances one would force the PMIC into PWM mode. The expanded description is an educated guess based on research on the internet about PWM and PFM. I think it makes sense to put this in the DT. The vendor building the board/DT is in the best position to know the constraints and requirements of the board, and can decide whether the trade off makes sense. As for the boards/DTs already out there, we can just leave it in auto mode. Regards ChenYu -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
