mirror of
https://github.com/AetherDroid/android_kernel_samsung_on5xelte.git
synced 2025-09-06 00:17:46 -04:00
Fixed MTP to work with TWRP
This commit is contained in:
commit
f6dfaef42e
50820 changed files with 20846062 additions and 0 deletions
|
@ -0,0 +1,67 @@
|
|||
* Device tree bindings for Texas Instruments keystone reset
|
||||
|
||||
This node is intended to allow SoC reset in case of software reset
|
||||
of selected watchdogs.
|
||||
|
||||
The Keystone SoCs can contain up to 4 watchdog timers to reset
|
||||
SoC. Each watchdog timer event input is connected to the Reset Mux
|
||||
block. The Reset Mux block can be configured to cause reset or not.
|
||||
|
||||
Additionally soft or hard reset can be configured.
|
||||
|
||||
Required properties:
|
||||
|
||||
- compatible: ti,keystone-reset
|
||||
|
||||
- ti,syscon-pll: phandle/offset pair. The phandle to syscon used to
|
||||
access pll controller registers and the offset to use
|
||||
reset control registers.
|
||||
|
||||
- ti,syscon-dev: phandle/offset pair. The phandle to syscon used to
|
||||
access device state control registers and the offset
|
||||
in order to use mux block registers for all watchdogs.
|
||||
|
||||
Optional properties:
|
||||
|
||||
- ti,soft-reset: Boolean option indicating soft reset.
|
||||
By default hard reset is used.
|
||||
|
||||
- ti,wdt-list: WDT list that can cause SoC reset. It's not related
|
||||
to WDT driver, it's just needed to enable a SoC related
|
||||
reset that's triggered by one of WDTs. The list is
|
||||
in format: <0>, <2>; It can be in random order and
|
||||
begins from 0 to 3, as keystone can contain up to 4 SoC
|
||||
reset watchdogs and can be in random order.
|
||||
|
||||
Example 1:
|
||||
Setup keystone reset so that in case software reset or
|
||||
WDT0 is triggered it issues hard reset for SoC.
|
||||
|
||||
pllctrl: pll-controller@02310000 {
|
||||
compatible = "ti,keystone-pllctrl", "syscon";
|
||||
reg = <0x02310000 0x200>;
|
||||
};
|
||||
|
||||
devctrl: device-state-control@02620000 {
|
||||
compatible = "ti,keystone-devctrl", "syscon";
|
||||
reg = <0x02620000 0x1000>;
|
||||
};
|
||||
|
||||
rstctrl: reset-controller {
|
||||
compatible = "ti,keystone-reset";
|
||||
ti,syscon-pll = <&pllctrl 0xe4>;
|
||||
ti,syscon-dev = <&devctrl 0x328>;
|
||||
ti,wdt-list = <0>;
|
||||
};
|
||||
|
||||
Example 2:
|
||||
Setup keystone reset so that in case of software reset or
|
||||
WDT0 or WDT2 is triggered it issues soft reset for SoC.
|
||||
|
||||
rstctrl: reset-controller {
|
||||
compatible = "ti,keystone-reset";
|
||||
ti,syscon-pll = <&pllctrl 0xe4>;
|
||||
ti,syscon-dev = <&devctrl 0x328>;
|
||||
ti,wdt-list = <0>, <2>;
|
||||
ti,soft-reset;
|
||||
};
|
|
@ -0,0 +1,26 @@
|
|||
Binding for the LTC2952 PowerPath controller
|
||||
|
||||
This chip is used to externally trigger a system shut down. Once the trigger has
|
||||
been sent, the chips' watchdog has to be reset to gracefully shut down.
|
||||
If the Linux systems decides to shut down it powers off the platform via the
|
||||
kill signal.
|
||||
|
||||
Required properties:
|
||||
|
||||
- compatible: Must contain: "lltc,ltc2952"
|
||||
- trigger-gpios: phandle + gpio-specifier for the GPIO connected to the
|
||||
chip's trigger line
|
||||
- watchdog-gpios: phandle + gpio-specifier for the GPIO connected to the
|
||||
chip's watchdog line
|
||||
- kill-gpios: phandle + gpio-specifier for the GPIO connected to the
|
||||
chip's kill line
|
||||
|
||||
Example:
|
||||
|
||||
ltc2952 {
|
||||
compatible = "lltc,ltc2952";
|
||||
|
||||
trigger-gpios = <&gpio0 1 GPIO_ACTIVE_LOW>;
|
||||
watchdog-gpios = <&gpio1 2 GPIO_ACTIVE_HIGH>;
|
||||
kill-gpios = <&gpio0 2 GPIO_ACTIVE_LOW>;
|
||||
};
|
11
Documentation/devicetree/bindings/power/reset/st-reset.txt
Normal file
11
Documentation/devicetree/bindings/power/reset/st-reset.txt
Normal file
|
@ -0,0 +1,11 @@
|
|||
*Device-Tree bindings for ST SW reset functionality
|
||||
|
||||
Required properties:
|
||||
- compatible: should be "st,<chip>-restart".
|
||||
- st,syscfg: should be a phandle of the syscfg node.
|
||||
|
||||
Example node:
|
||||
restart {
|
||||
compatible = "st,stih416-restart";
|
||||
st,syscfg = <&syscfg_sbc>;
|
||||
};
|
|
@ -0,0 +1,23 @@
|
|||
Generic SYSCON mapped register reset driver
|
||||
|
||||
This is a generic reset driver using syscon to map the reset register.
|
||||
The reset is generally performed with a write to the reset register
|
||||
defined by the register map pointed by syscon reference plus the offset
|
||||
with the mask defined in the reboot node.
|
||||
|
||||
Required properties:
|
||||
- compatible: should contain "syscon-reboot"
|
||||
- regmap: this is phandle to the register map node
|
||||
- offset: offset in the register map for the reboot register (in bytes)
|
||||
- mask: the reset value written to the reboot register (32 bit access)
|
||||
|
||||
Default will be little endian mode, 32 bit access only.
|
||||
|
||||
Examples:
|
||||
|
||||
reboot {
|
||||
compatible = "syscon-reboot";
|
||||
regmap = <®mapnode>;
|
||||
offset = <0x0>;
|
||||
mask = <0x1>;
|
||||
};
|
Loading…
Add table
Add a link
Reference in a new issue