The patch titled Subject: rtc: bq32000: add trickle charger device tree binding has been removed from the -mm tree. Its filename was rtc-bq32000-add-trickle-charger-device-tree-binding.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ From: Pavel Machek <pavel@xxxxxx> Subject: rtc: bq32000: add trickle charger device tree binding BQ32000 have "trickle chargers". Introduce a device tree binding for specifying the trickle charger configuration for that. Signed-off-by: Pavel Machek <pavel@xxxxxxx> Reviewed-by: Jason Cooper <jason@xxxxxxxxxxxxxx> Cc: Matti Vaittinen <matti.vaittinen@xxxxxxx> Cc: Rob Herring <robh+dt@xxxxxxxxxx> Cc: Ian Campbell <ijc+devicetree@xxxxxxxxxxxxxx> Cc: Alessandro Zummo <a.zummo@xxxxxxxxxxxx> Cc: Guenter Roeck <linux@xxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- Documentation/devicetree/bindings/i2c/ti,bq32k.txt | 18 +++++++++++ 1 file changed, 18 insertions(+) diff -puN /dev/null Documentation/devicetree/bindings/i2c/ti,bq32k.txt --- /dev/null +++ a/Documentation/devicetree/bindings/i2c/ti,bq32k.txt @@ -0,0 +1,18 @@ +* TI BQ32000 I2C Serial Real-Time Clock + +Required properties: +- compatible: Should contain "ti,bq32000". +- reg: I2C address for chip + +Optional properties: +- trickle-resistor-ohms : Selected resistor for trickle charger + Values usable are 1120 and 20180 + Should be given if trickle charger should be enabled +- trickle-diode-disable : Do not use internal trickle charger diode + Should be given if internal trickle charger diode should be disabled +Example: + bq32000: rtc@68 { + compatible = "ti,bq32000"; + trickle-resistor-ohms = <1120>; + reg = <0x68>; + }; _ Patches currently in -mm which might be from pavel@xxxxxx are origin.patch input-route-kbd-leds-through-the-generic-leds-layer.patch lib-vsprintf-add-%pt-format-specifier.patch linux-next.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html