-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge tag 'mfd-for-linus-3.16' of git://git.kernel.org/pub/scm/linux/…
…kernel/git/lee/mfd into next Pull MFD updates from Lee Jones: "Changes to existing drivers: - increase DT coverage: arizona, mc13xxx, stmpe-i2c, syscon, sun6i-prcm - regmap use of and/or clean-up: tps65090, twl6040 - basic renaming: max14577 - use new cpufreq helpers: db8500-prcmu - increase regulator support: stmpe, arizona, wm5102 - reduce legacy GPIO overhead: stmpe - provide necessary remove path: bcm590xx - expand sysfs presence: kempld - move driver specific code out to drivers: rtc-s5m, arizona - clk handling: twl6040 - use managed (devm_*) resources: ipaq-micro - clean-up/remove unused/duplicated code: tps65218, sec, pm8921, abx500-core, db8500-prcmu, menelaus - build/boot/sematic bug fixes: rtsx_usb, stmpe, bcm590xx, abx500, mc13xxx, rdc321x-southbridge, mfd-core, sec, max14577, syscon, cros_ec_spi - constify stuff: sm501, tps65910, tps6507x, tps6586x, max77686, max8997, kempld, max77693, max8907, rtsx_usb, db8500-prcmu, max8998, wm8400, sec, lp3943, max14577, as3711, omap-usb-host, ipaq-micro Support for new devices: - add support for max77836 into max14577 - add support for tps658640 into tps6586x - add support for cros-ec-i2c-tunnel into cros_ec - add new driver for rtsx_usb_sdmmc and rtsx_usb_ms - add new driver for axp20x - add new driver for sun6i-prcm - add new driver for ipaq-micro" * tag 'mfd-for-linus-3.16' of git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd: (77 commits) mfd: wm5102: Correct default for LDO Control 2 register mfd: menelaus: Use module_i2c_driver mfd: tps65218: Terminate of match table mfd: db8500-prcmu: Remove check for CONFIG_DBX500_PRCMU_DEBUG mfd: ti-keystone-devctrl: Add bindings for device state control mfd: palmas: Format the header file mfd: abx500-core: Remove unused function abx500_dump_all_banks() mfd: arizona: Correct addresses of always-on trigger registers mfd: max14577: Cast to architecture agnostic data type i2c: ChromeOS EC tunnel driver mfd: cros_ec: Sync to the latest cros_ec_commands.h from EC sources mfd: cros_ec: spi: Increase cros_ec_spi deadline from 5ms to 100ms mfd: cros_ec: spi: Make the cros_ec_spi timeout more reliable mfd: cros_ec: spi: Add mutex to cros_ec_spi mfd: cros_ec: spi: Calculate delay between transfers correctly mfd: arizona: Correct error message for addition of main IRQ chip mfd: wm8997: Add registers for high power mode mfd: arizona: Add MICVDD to mapped regulators mfd: ipaq-micro: Make mfd_cell array const mfd: ipaq-micro: Use devm_ioremap_resource() ...
- Loading branch information
Showing
76 changed files
with
6,641 additions
and
1,673 deletions.
There are no files selected for viewing
39 changes: 39 additions & 0 deletions
39
Documentation/devicetree/bindings/i2c/i2c-cros-ec-tunnel.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
I2C bus that tunnels through the ChromeOS EC (cros-ec) | ||
====================================================== | ||
On some ChromeOS board designs we've got a connection to the EC (embedded | ||
controller) but no direct connection to some devices on the other side of | ||
the EC (like a battery and PMIC). To get access to those devices we need | ||
to tunnel our i2c commands through the EC. | ||
|
||
The node for this device should be under a cros-ec node like google,cros-ec-spi | ||
or google,cros-ec-i2c. | ||
|
||
|
||
Required properties: | ||
- compatible: google,cros-ec-i2c-tunnel | ||
- google,remote-bus: The EC bus we'd like to talk to. | ||
|
||
Optional child nodes: | ||
- One node per I2C device connected to the tunnelled I2C bus. | ||
|
||
|
||
Example: | ||
cros-ec@0 { | ||
compatible = "google,cros-ec-spi"; | ||
|
||
... | ||
|
||
i2c-tunnel { | ||
compatible = "google,cros-ec-i2c-tunnel"; | ||
#address-cells = <1>; | ||
#size-cells = <0>; | ||
|
||
google,remote-bus = <0>; | ||
|
||
battery: sbs-battery@b { | ||
compatible = "sbs,sbs-battery"; | ||
reg = <0xb>; | ||
sbs,poll-retry-count = <1>; | ||
}; | ||
}; | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,59 @@ | ||
* Allwinner PRCM (Power/Reset/Clock Management) Multi-Functional Device | ||
|
||
PRCM is an MFD device exposing several Power Management related devices | ||
(like clks and reset controllers). | ||
|
||
Required properties: | ||
- compatible: "allwinner,sun6i-a31-prcm" | ||
- reg: The PRCM registers range | ||
|
||
The prcm node may contain several subdevices definitions: | ||
- see Documentation/devicetree/clk/sunxi.txt for clock devices | ||
- see Documentation/devicetree/reset/allwinner,sunxi-clock-reset.txt for reset | ||
controller devices | ||
|
||
|
||
Example: | ||
|
||
prcm: prcm@01f01400 { | ||
compatible = "allwinner,sun6i-a31-prcm"; | ||
reg = <0x01f01400 0x200>; | ||
|
||
/* Put subdevices here */ | ||
ar100: ar100_clk { | ||
compatible = "allwinner,sun6i-a31-ar100-clk"; | ||
#clock-cells = <0>; | ||
clocks = <&osc32k>, <&osc24M>, <&pll6>, <&pll6>; | ||
}; | ||
|
||
ahb0: ahb0_clk { | ||
compatible = "fixed-factor-clock"; | ||
#clock-cells = <0>; | ||
clock-div = <1>; | ||
clock-mult = <1>; | ||
clocks = <&ar100_div>; | ||
clock-output-names = "ahb0"; | ||
}; | ||
|
||
apb0: apb0_clk { | ||
compatible = "allwinner,sun6i-a31-apb0-clk"; | ||
#clock-cells = <0>; | ||
clocks = <&ahb0>; | ||
clock-output-names = "apb0"; | ||
}; | ||
|
||
apb0_gates: apb0_gates_clk { | ||
compatible = "allwinner,sun6i-a31-apb0-gates-clk"; | ||
#clock-cells = <1>; | ||
clocks = <&apb0>; | ||
clock-output-names = "apb0_pio", "apb0_ir", | ||
"apb0_timer01", "apb0_p2wi", | ||
"apb0_uart", "apb0_1wire", | ||
"apb0_i2c"; | ||
}; | ||
|
||
apb0_rst: apb0_rst { | ||
compatible = "allwinner,sun6i-a31-clock-reset"; | ||
#reset-cells = <1>; | ||
}; | ||
}; |
19 changes: 19 additions & 0 deletions
19
Documentation/devicetree/bindings/mfd/ti-keystone-devctrl.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
* Device tree bindings for Texas Instruments keystone device state control | ||
|
||
The Keystone II devices have a set of registers that are used to control | ||
the status of its peripherals. This node is intended to allow access to | ||
this functionality. | ||
|
||
Required properties: | ||
|
||
- compatible: "ti,keystone-devctrl", "syscon" | ||
|
||
- reg: contains offset/length value for device state control | ||
registers space. | ||
|
||
Example: | ||
|
||
devctrl: device-state-control@0x02620000 { | ||
compatible = "ti,keystone-devctrl", "syscon"; | ||
reg = <0x02620000 0x1000>; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.