regulator/OMAP: Support TI Adaptive Body Bias(ABB) on-chip LDO driver
Subsystems (2)
v3 cover regulator/OMAP: Support TI Adaptive Body Bias(ABB) on-chip LDO driver
Adaptive Body Biasing (ABB) modulates transistor bias voltages dynamically in order to optimize switching speed versus leakage.
Texas Instruments' SoC processors have an on chip LDO subsystem which is part of the SmartReflex 2 technology and provides support for this power management technique with Forward Body Biasing (FBB) and Reverse Body Biasing (RBB). These modulate the body voltage of transistor cells or blocks dynamically to gain performance and reduce leakage.
This series introduces ABB regulator and associated data for controlling ABB module on OMAP3630+ TI SoCs. Usage of ABB LDO is part of SoC's OPP voltage transition sequence. We just introduce the regulator in this series for LDO control, however, the actual sequence of control of this regulator is left to the implementation of SoC OPP voltage transition of the appropriate domain.
Note: We only support device tree supported boot in this series.
Testing and Caveats:
- Sanity tested on OMAP3,4,5 platforms - verified with omapconf.
- Testing performed with regulator virtual consumer:
http://pastebin.com/Knp1fSxA
- OMAP5 clock nodes are introduced, but clock data is missing in upstream - tested with private tree with requisite clock nodes introduced. Clock node has been commented out in this series.
V3 of this series also available (with testing patch):
http link: https://github.com/nmenon/linux-2.6-playground/commits/devel/abb-regulator-v3
git link: git://github.com/nmenon/linux-2.6-playground.git
branch: devel/abb-regulator-v3
Changes in V3:
- Regulator is purely meant to control ABB LDO.
- The "regulator chaining" for doing voltage scale for entire SoC voltage domain has been dropped.
- Debugfs entries meant to expose ABB registers has been dropped as the same functionality can be achieved with readmem like omapconf application.
- Re-factored regulator logic to make it simpler using the existing voltage indexing support of regulator framework.
- Implemented efuse based detection strategy and provided requisite data to cover all existing OMAPs using ABB.
- Depends on OMAP clock driver introduced in:
http://marc.info/?t=136580758500001&r=1&w=2
V2: http://marc.info/?t=136603261400007&r=1&w=2&n=3
V1/RFC: http://marc.info/?l=linux-omap&m=136449099409794&w=2
Andrii.Tseglytskyi (5):
regulator: Introduce TI Adaptive Body Bias(ABB) on-chip LDO driver
ARM: dts: OMAP36xx: Add device node for ABB
ARM: dts: OMAP443x: Add device nodes for ABB
ARM: dts: OMAP4460: Add device nodes for ABB
ARM: dts: OMAP5: Add device nodes for ABB
.../bindings/regulator/ti-abb-regulator.txt | 128 +++ arch/arm/boot/dts/omap3.dtsi | 5 + arch/arm/boot/dts/omap36xx.dtsi | 20 + arch/arm/boot/dts/omap4.dtsi | 32 + arch/arm/boot/dts/omap443x.dtsi | 26 + arch/arm/boot/dts/omap4460.dtsi | 38 + arch/arm/boot/dts/omap5.dtsi | 67 ++ drivers/regulator/Kconfig | 10 + drivers/regulator/Makefile | 1 + drivers/regulator/ti-abb-regulator.c | 912 ++++++++++++++++++++ 10 files changed, 1239 insertions(+) create mode 100644 Documentation/devicetree/bindings/regulator/ti-abb-regulator.txt create mode 100644 drivers/regulator/ti-abb-regulator.c
Signature · 1 line
1.7.9.5
PATCH v3 1/5 regulator: Introduce TI Adaptive Body Bias(ABB) on-chip LDO driver
From: "Andrii.Tseglytskyi" <[email protected]>
Adaptive Body Biasing (ABB) modulates transistor bias voltages dynamically in order to optimize switching speed versus leakage.
Texas Instruments' SmartReflex 2 technology provides support for this power management technique with Forward Body Biasing (FBB) and Reverse Body Biasing (RBB). These modulate the body voltage of transistor cells or blocks dynamically to gain performance and reduce leakage. TI's SmartReflex white paper[1] has further information for usage in conjunction with other power management techniques.
The application of FBB/RBB technique is determined for each unique device in some process nodes, whereas, they are mandated on other process nodes.
In a nutshell, ABB technique is implemented on TI SoC as an on-chip LDO which has ABB module controlling the bias voltage. However, the voltage is unique per device. These vary per SoC family and the manner in which these techniques are used may vary depending on the Operating Performance Point (OPP) voltage targeted. For example:
OMAP3630/OMAP4430: certain OPPs mandate usage of FBB independent of
devices.
OMAP4460/OMAP4470: certain OPPs mandate usage of FBB, while others may
optionally use FBB or optimization with RBB.
OMAP5: ALL OPPs may optionally use ABB, and ABB biasing voltage is
influenced by vset fused in s/w and requiring s/w override of default values.
Further, two generations of ABB module are used in various TI SoCs. They have remained mostly register field compatible, however the register offset had switched between versions.
We introduce ABB LDO support in the form of a regulator which is controlled by voltages denoting the desired Operating Performance Point which is targeted. However, since ABB transition is part of OPP change sequence, the sequencing required to ensure sane operation w.r.t OPP change is left to the controlling driver (example: cpufreq SoC driver) using standard regulator operations.
The driver supports all ABB modes and ability to override ABB LDO vset control efuse based ABB mode detection etc.
Current implementation is heavily influenced by the original patch series [2][3] from Mike Turquette. However, the current implementation supports only device tree based information.
[1] http://www.ti.com/pdfs/wtbu/smartreflex_whitepaper.pdf
[2] http://marc.info/?l=linux-omap&m=134931341818379&w=2
[3] http://marc.info/?l=linux-arm-kernel&m=134931402406853&w=2
---
V2: http://marc.info/?l=linux-omap&m=136611169104414&w=2
V1: http://marc.info/?l=linux-omap&m=136481444405843&w=2
.../bindings/regulator/ti-abb-regulator.txt | 128 +++ drivers/regulator/Kconfig | 10 + drivers/regulator/Makefile | 1 + drivers/regulator/ti-abb-regulator.c | 912 ++++++++++++++++++++ 4 files changed, 1051 insertions(+) create mode 100644 Documentation/devicetree/bindings/regulator/ti-abb-regulator.txt create mode 100644 drivers/regulator/ti-abb-regulator.c
Documentation/devicetree/bindings/regulator/ti-abb-regulator.txt new file +128 -0
@@ -0,0 +1,128 @@ +Adaptive Body Bias(ABB) SoC internal LDO regulator for Texas Instruments SoCs + +Required Properties: +- compatible: Should be one of: + - "ti,abb-v1" for older SoCs like OMAP3 + - "ti,abb-v2" for newer SoCs like OMAP4, OMAP5 +- reg: Address and length of the register set for the device. It contains + the information of registers in the same order as described by reg-names +- reg-names: Should contain the reg names + - "base-address" - contains base address of ABB module + - "int-address" - contains address of interrupt register for ABB module + (also see Optional properties) +- #address-cell: should be 0 +- #size-cell: should be 0 +- clocks: should point to the clock node used by ABB module +- ti,settling-time: Settling time in uSecs from SoC documentation for ABB module + to settle down(target time for SR2_WTCNT_VALUE). +- ti,clock-cycles: SoC specific data about count of system ti,clock-cycles used for + computing settling time from SoC Documentation for ABB module(clock + cycles for SR2_WTCNT_VALUE). +- ti,tranxdone-status-mask: Mask to the int-register to write-to-clear mask + indicating LDO tranxdone (operation complete). +- ti,abb_info: An array of 6-tuples u32 items providing information about ABB + configuration needed per operational voltage of the device. + Each item consists of the following in the same order: + volt: voltage in uV - Only used to index ABB information. + ABB mode: one of the following: + 0-bypass + 1-Forward Body Bias(FBB) + 3-Reverse Body Bias(RBB) + efuse: (see Optional properties) + RBB enable efuse Mask: (See Optional properties) + FBB enable efuse Mask: (See Optional properties) + Vset value efuse Mask: (See Optional properties) + + NOTE: If more than 1 entry is present, then regulator is setup to change + voltage, allowing for various modes to be selected indexed off + the regulator. Further, ABB LDOs are considered always-on by + default. + +Optional Properties: +- reg-names: In addition to the required properties, the following are optional + - "efuse-address" - Contains efuse base address used to pick up ABB info. + - "ldo-address" - Contains address of ABB LDO overide register address. + "efuse-address" is required for this. +- ti,ldovbb-vset-mask - Required if ldo-address is set, mask for LDO override + register to provide override vset value. +- ti,ldovbb-override-mask - Required if ldo-address is set, mask for LDO + override register to enable override vset value. +- ti,abb_opp_sel: Addendum to the description in required properties + efuse: Mandatory if 'efuse-address' register is defined. Provides offset + from efuse-address to pick up ABB characteristics. Set to 0 if + 'efuse-address' is not defined. + RBB enable efuse Mask: Optional if 'efuse-address' register is defined. + 'ABB mode' is force set to RBB mode if value at "efuse-address" + + efuse maps to RBB mask. Set to 0 to ignore this. + FBB enable efuse Mask: Optional if 'efuse-address' register is defined. + 'ABB mode' is force set to FBB mode if value at "efuse-address" + + efuse maps to FBB mask (valid only if RBB mask does not match) + Set to 0 to ignore this. + Vset value efuse Mask: Mandatory if ldo-address is set. Picks up from + efuse the value to set in 'ti,ldovbb-vset-mask' at ldo-address. + +Example #1: Simplest configuration (no efuse data, hard coded ABB table): +abb_x: regulator-abb-x { + compatible = "ti,abb-v1"; + regulator-name = "abb_x"; + #address-cell = <0>; + #size-cells = <0>; + reg = <0x483072f0 0x8>, <0x48306818 0x4>; + reg-names = "base-address", "int-address"; + ti,tranxdone-status-mask = <0x4000000>; + clocks = <&sysclk>; + ti,settling-time = <30>; + ti,clock-cycles = <8>; + ti,abb_info = < + /* uV ABB efuse rbb_m fbb_m vset_m */ + 1012500 0 0 0 0 0 /* Bypass */ + 1200000 3 0 0 0 0 /* RBB mandatory */ + 1320000 1 0 0 0 0 /* FBB mandatory */ + >; +}; + +Example #2: Efuse bits contain ABB mode setting (no LDO override capability) +abb_y: regulator-abb-y { + compatible = "ti,abb-v2"; + regulator-name = "abb_y"; + #address-cell = <0>; + #size-cells = <0>; + reg = <0x4a307bd0 0x8>, <0x4a306014 0x4>, <0x4A002268 0x8>; + reg-names = "base-address", "int-address", "efuse-address"; + ti,tranxdone-status-mask = <0x4000000>; + clocks = <&sysclk>; + ti,settling-time = <50>; + ti,clock-cycles = <16>; + ti,abb_info = < + /* uV ABB efuse rbb_m fbb_m vset_m */ + 975000 0 0 0 0 0 /* Bypass */ + 1012500 0 0 0x40000 0 0 /* RBB optional */ + 1200000 0 0x4 0 0x40000 0 /* FBB optional */ + 1320000 1 0 0 0 0 /* FBB mandatory */ + >; +}; + +Example #3: Efuse bits contain ABB mode setting and LDO override capability +abb_z: regulator-abb-z { + compatible = "ti,abb-v2"; + regulator-name = "abb_z"; + #address-cell = <0>; + #size-cells = <0>; + reg = <0x4ae07ce4 0x8>, <0x4ae06010 0x4>, + <0x4a002194 0x8>, <0x4ae0C314 0x4>; + reg-names = "base-address", "int-address", + "efuse-address", "ldo-address"; + ti,tranxdone-status-mask = <0x8000000>; + /* LDOVBBMM_MUX_CTRL */ + ti,ldovbb-override-mask = <0x400>; + /* LDOVBBMM_VSET_OUT */ + ti,ldovbb-vset-mask = <0x1F>; + clocks = <&sysclk>; + ti,settling-time = <50>; + ti,clock-cycles = <16>; + ti,abb_info = < + /* uV ABB efuse rbb_m fbb_m vset_m */ + 975000 0 0 0 0 0 /* Bypass */ + 1200000 0 0x4 0 0x40000 0x1f00 /* FBB optional, vset */ + >; +};
drivers/regulator/Kconfig +10 -0
@@ -472,6 +472,16 @@ config REGULATOR_TWL4030 This driver supports the voltage regulators provided by this family of companion chips. +config REGULATOR_TI_ABB + bool "TI Adaptive Body Bias on-chip LDO" + depends on ARCH_OMAP + help + Select this option to support Texas Instruments' on-chip Adaptive Body + Bias (ABB) LDO regulators. It is recommended that this option be + enabled on required TI SoC. Certain Operating Performance Points + on TI SoCs may be unstable without enabling this as it provides + device specific optimized bias to allow/optimize functionality. + config REGULATOR_VEXPRESS tristate "Versatile Express regulators" depends on VEXPRESS_CONFIG
drivers/regulator/Makefile +1 -0
@@ -63,6 +63,7 @@ obj-$(CONFIG_REGULATOR_TPS65910) += tps65910-regulator.o obj-$(CONFIG_REGULATOR_TPS65912) += tps65912-regulator.o obj-$(CONFIG_REGULATOR_TPS80031) += tps80031-regulator.o obj-$(CONFIG_REGULATOR_TWL4030) += twl-regulator.o +obj-$(CONFIG_REGULATOR_TI_ABB) += ti-abb-regulator.o obj-$(CONFIG_REGULATOR_VEXPRESS) += vexpress.o obj-$(CONFIG_REGULATOR_WM831X) += wm831x-dcdc.o obj-$(CONFIG_REGULATOR_WM831X) += wm831x-isink.o
drivers/regulator/ti-abb-regulator.c new file +912 -0
912 lines not on this page · raw message
Signature · 1 line
1.7.9.5
Mark Brown
maintainerRe: [PATCH v3 1/5] regulator: Introduce TI Adaptive Body Bias(ABB) on-chip LDO driver
Quoted 4 lines · Nishanth Menon
From: "Andrii.Tseglytskyi" <[email protected]>
Adaptive Body Biasing (ABB) modulates transistor bias voltages dynamically in order to optimize switching speed versus leakage.
I've applied this but please note that I still have deep concerns about
some of the discussion about controlling this from other regulators.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130503/b2363123/attachment-0001.sig>
Re: [PATCH v3 1/5] regulator: Introduce TI Adaptive Body Bias(ABB) on-chip LDO driver
Hi Mark,
Quoted 8 lines · Mark Brown
Quoted 4 lines · Nishanth Menon
From: "Andrii.Tseglytskyi" <[email protected]>
Adaptive Body Biasing (ABB) modulates transistor bias voltages dynamically in order to optimize switching speed versus leakage.
I've applied this but please note that I still have deep concerns about some of the discussion about controlling this from other regulators.
Thanks for the merge.
We don't have any further plans of pursuing the concept of regulator chaining for upstream. After an off-line chat with Mike T, we are planning on introducing OMAP specific notifier hooks to clock framework. This should allow us to do the appropriate sequencing necessary to control AVS, regulators for ABB and PMIC in the right sequence.
Signature · 2 lines
Regards, Nishanth Menon
PATCH v3 2/5 ARM: dts: OMAP36xx: Add device node for ABB
In reply to Nishanth MenonFrom: "Andrii.Tseglytskyi" <[email protected]>
Add ABB device node for OMAP36xx family of devices. Data is based on OMAP36XX Technical Reference Manual revision AB (Dec 2012).
--- arch/arm/boot/dts/omap3.dtsi | 5 +++++ arch/arm/boot/dts/omap36xx.dtsi | 20 ++++++++++++++++++++ 2 files changed, 25 insertions(+)
arch/arm/boot/dts/omap3.dtsi +5 -0
@@ -75,6 +75,11 @@ ti,hwmods = "counter_32k"; }; + sysclk: sys { + #clock-cells = <0>; + compatible = "ti,omap-clock"; + }; + dpll1: dpll1 { #clock-cells = <0>; compatible = "ti,omap-clock";
arch/arm/boot/dts/omap36xx.dtsi +20 -0
@@ -34,5 +34,25 @@ ti,hwmods = "uart4"; clock-frequency = <48000000>; }; + + abb_mpu_iva: regulator-abb-mpu { + compatible = "ti,abb-v1"; + regulator-name = "abb_mpu_iva"; + #address-cell = <0>; + #size-cells = <0>; + reg = <0x483072f0 0x8>, <0x48306818 0x4>; + reg-names = "base-address", "int-address"; + ti,tranxdone-status-mask = <0x4000000>; + clocks = <&sysclk>; + ti,settling-time = <30>; + ti,clock-cycles = <8>; + ti,abb_info = < + /*uV ABB efuse rbb_m fbb_m vset_m*/ + 1012500 0 0 0 0 0 + 1200000 0 0 0 0 0 + 1325000 0 0 0 0 0 + 1375000 1 0 0 0 0 + >; + }; }; };
Signature · 1 line
1.7.9.5
PATCH v3 3/5 ARM: dts: OMAP443x: Add device nodes for ABB
In reply to Nishanth MenonFrom: "Andrii.Tseglytskyi" <[email protected]>
Add ABB device nodes for OMAP443x family of devices. abb_iva is populated, but disabled as it is not used on current OMAP443x family, but the node is used on OMAP446x family. Data is based on OMAP443x Technical Reference Manual revision AN (April 2013).
--- arch/arm/boot/dts/omap4.dtsi | 32 ++++++++++++++++++++++++++++++++ arch/arm/boot/dts/omap443x.dtsi | 26 ++++++++++++++++++++++++++ 2 files changed, 58 insertions(+)
arch/arm/boot/dts/omap4.dtsi +32 -0
@@ -108,6 +108,11 @@ ti,hwmods = "counter_32k"; }; + sysclk_in: sys_clkin { + #clock-cells = <0>; + compatible = "ti,omap-clock"; + }; + dpll_mpu: dpll_mpu { #clock-cells = <0>; compatible = "ti,omap-clock";
@@ -667,5 +672,32 @@ ram-bits = <12>; ti,has-mailbox; }; + + abb_mpu: regulator-abb-mpu { + compatible = "ti,abb-v2"; + regulator-name = "abb_mpu"; + #address-cells = <0>; + #size-cells = <0>; + ti,tranxdone-status-mask = <0x80>; + clocks = <&sysclk_in>; + ti,settling-time = <50>; + ti,clock-cycles = <16>; + + status = "disabled"; + }; + + abb_iva: regulator-abb-iva { + compatible = "ti,abb-v2"; + regulator-name = "abb_iva"; + #address-cells = <0>; + #size-cells = <0>; + ti,tranxdone-status-mask = <0x80000000>; + clocks = <&sysclk_in>; + ti,settling-time = <50>; + ti,clock-cycles = <16>; + + status = "disabled"; + }; + }; };
arch/arm/boot/dts/omap443x.dtsi +26 -0
@@ -24,4 +24,30 @@ clock-latency = <300000>; /* From legacy driver */ }; }; + + ocp { + abb_mpu: regulator-abb-mpu { + status = "okay"; + + reg = <0x4a307bd0 0x8>, <0x4a306014 0x4>; + reg-names = "base-address", "int-address"; + + ti,abb_info = < + /*uV ABB efuse rbb_m fbb_m vset_m*/ + 1025000 0 0 0 0 0 + 1200000 0 0 0 0 0 + 1313000 0 0 0 0 0 + 1375000 1 0 0 0 0 + 1389000 1 0 0 0 0 + >; + }; + + /* Default unused, just provide register info for record */ + abb_iva: regulator-abb-iva { + reg = <0x4a307bd8 0x8>, <0x4a306010 0x4>; + reg-names = "base-address", "int-address"; + }; + + }; + };
Signature · 1 line
1.7.9.5
PATCH v3 4/5 ARM: dts: OMAP4460: Add device nodes for ABB
In reply to Nishanth MenonFrom: "Andrii.Tseglytskyi" <[email protected]>
Add ABB device nodes for OMAP4460 device Data is based on OMAP4460 Technical Reference Manual revision Z (April 2013)
--- arch/arm/boot/dts/omap4460.dtsi | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+)
arch/arm/boot/dts/omap4460.dtsi +38 -0
@@ -29,4 +29,42 @@ <0 55 0x4>; ti,hwmods = "debugss"; }; + + ocp { + abb_mpu: regulator-abb-mpu { + status = "okay"; + + reg = <0x4a307bd0 0x8>, <0x4a306014 0x4>, + <0x4A002268 0x4>; + reg-names = "base-address", "int-address", + "efuse-address"; + + ti,abb_info = < + /*uV ABB efuse rbb_m fbb_m vset_m*/ + 1025000 0 0 0 0 0 + 1200000 0 0 0 0 0 + 1313000 0 0 0x100000 0x40000 0 + 1375000 1 0 0 0 0 + 1389000 1 0 0 0 0 + >; + }; + + abb_iva: regulator-abb-iva { + status = "okay"; + + reg = <0x4a307bd8 0x8>, <0x4a306010 0x4>, + <0x4A002268 0x4>; + reg-names = "base-address", "int-address", + "efuse-address"; + + ti,abb_info = < + /*uV ABB efuse rbb_m fbb_m vset_m*/ + 950000 0 0 0 0 0 + 1140000 0 0 0 0 0 + 1291000 0 0 0x200000 0 0 + 1375000 1 0 0 0 0 + 1376000 1 0 0 0 0 + >; + }; + }; };
Signature · 1 line
1.7.9.5
PATCH v3 5/5 ARM: dts: OMAP5: Add device nodes for ABB
In reply to Nishanth MenonFrom: "Andrii.Tseglytskyi" <[email protected]>
Add ABB device nodes for OMAP5 family of devices. Data is based on OMAP543x Technical Reference Manual revision U (April 2013).
NOTE: clock node has been disabled in this patch due to the lack of OMAP5 clock data.
--- arch/arm/boot/dts/omap5.dtsi | 67 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 67 insertions(+)
arch/arm/boot/dts/omap5.dtsi +67 -0
@@ -667,5 +667,72 @@ ctrl-module = <&omap_control_usb>; }; }; + + abb_mpu: regulator-abb-mpu { + compatible = "ti,abb-v2"; + regulator-name = "abb_mpu"; + #address-cells = <0>; + #size-cells = <0>; + /* clocks = <&sysclk_in>; - once we have clock data */ + ti,settling-time = <50>; + ti,clock-cycles = <16>; + + reg = <0x4ae07cdc 0x8>, <0x4ae06014 0x4>, + <0x4a0021ac 0x18>, <0x4ae0C318 0x4>; + reg-names = "base-address", "int-address", + "efuse-address", "ldo-address"; + ti,tranxdone-status-mask = <0x80>; + /* LDOVBBMPU_MUX_CTRL */ + ti,ldovbb-override-mask = <0x400>; + /* LDOVBBMPU_VSET_OUT */ + ti,ldovbb-vset-mask = <0x1F>; + + /* + * NOTE: only FBB mode used but actual vset will + * determine final biasing + */ + ti,abb_info = < + /*uV ABB efuse rbb_m fbb_m vset_m*/ + 880000 0 0x4 0 0x20000000 0x1F000000 + 1060000 0 0x8 0 0x20000000 0x1F000000 + 1250000 0 0x10 0 0x20000000 0x1F000000 + 1260000 1 0x14 0 0x20000000 0x1F000000 + >; + + status = "disabled"; + }; + + abb_mm: regulator-abb-mm { + compatible = "ti,abb-v2"; + regulator-name = "abb_iva"; + #address-cells = <0>; + #size-cells = <0>; + /* clocks = <&sysclk_in>; - once we have clock data */ + ti,settling-time = <50>; + ti,clock-cycles = <16>; + + reg = <0x4ae07ce4 0x8>, <0x4ae06010 0x4>, + <0x4a002194 0x14>, <0x4ae0C314 0x4>; + reg-names = "base-address", "int-address", + "efuse-address", "ldo-address"; + ti,tranxdone-status-mask = <0x80000000>; + /* LDOVBBMM_MUX_CTRL */ + ti,ldovbb-override-mask = <0x400>; + /* LDOVBBMM_VSET_OUT */ + ti,ldovbb-vset-mask = <0x1F>; + + /* + * NOTE: only FBB mode used but actual vset will + * determine final biasing + */ + ti,abb_info = < + /*uV ABB efuse rbb_m fbb_m vset_m*/ + 880000 0 0x4 0 0x20000000 0x1F000000 + 1025000 0 0x8 0 0x20000000 0x1F000000 + 1120000 1 0x10 0 0x20000000 0x1F000000 + >; + + status = "disabled"; + }; }; };
Signature · 1 line
1.7.9.5