Support NVIDIA Tegra-based Acer A500 and Nexus 7 devices
Subsystems (4)
v8 cover Support NVIDIA Tegra-based Acer A500 and Nexus 7 devices
Hello,
This series introduces upstream kernel support for Acer Iconia Tab A500 and ASUS Google Nexus 7 tablet devices. Please review and apply, thanks in advance.
Changelog:
v8: - The eMMC voltage regulator is now marked as always-ON in all
device-trees because turned out that some bootloader versions have assumption about the enabled regulator at a boot time. This fixes machine hanging on a warm reboot, it's also matching the downstream kernel regulator configuration.
- The core regulator of the Ti PMIC Nexus 7 variant is now limited to a 1.35V, which is a more realistic limit than 1.5V that was borrowed from the Cardhu device-tree. Now both Maxim and Ti variants have the common limits.
- Added acks from Rob Herring.
v7: - This version brings support for a Nexus 7 variant that uses Ti PMIC
instead of the Maxim PMIC. Previously we assumed that variant with the Ti PMIC doesn't exist in a wild, but turned out that it was a wrong assumption. In a result the device-trees are separated into more DTSI pieces, which combined together form the final device-tree. Thanks to Zack Pearsall for testing the Ti version!
- The camera voltage regulator is now preset to a correct 1.8v in the Nexus 7 device-tree.
v6: - Corrected PMIC's RTC alias in the DTs. Sometime ago I renamed the
PMIC's node to match the modern upstream styling, but forgot to change the RTC alias. Now PMIC RTC alias uses node's handle instead of string.
- Removed "panel: " handle from device trees, which became unused after v5 and I just missed to remove it.
v5: - After spending some more time on adding LVDS encoder bridge support
to the Tegra DRM driver, I'm now having a second thought and agree with Thierry Reding that in a longer run it should be better not to mix old nvidia,panel with new output graph in device-tree. So the nvidia,panel phandle is removed now in both A500 and Nexus 7 DTs.
v4: - Corrected CPU's thermal zone on both A500 and Nexus 7, which
should use the remote thermal sensor (Tegra chip) instead of the local ("skin" temperature).
- Added default PMIC pinmux state on Nexus 7, for completeness.
- Added PMIC cpu_pwr_req GPIO hog on Nexus 7, for completeness.
- Renamed thermal sensor node label to NCT72 on Nexus 7 to match the actual hardware (NCT72 is compatible with NCT1008). For completeness.
- Added always-on USB AVDD regulator on Nexus 7, which is controlled by the PMIC GPIO. For completeness.
- Added PMIC GPIO enable-control to the 3v3_sys regulator on Nexus 7, for completeness.
- Added CONFIG_NAMESPACES, CONFIG_USER_NS, CONFIG_SECCOMP and CONFIG_PINCTRL_MAX77620 to the tegra_defconfig. The first three options are must-have for the modern userspace, the last is somewhat actual now since the default PMIC pinmux state is added to the N7 DT.
v3: - Improved device-tree node-names in accordance to review comments that
were made by Thierry Reding to v2.
- Corrected LVDS encoder powerdown-GPIO polarity on both A500 and Nexus 7 because I implemented the DRM bridges support in the Tegra DRM driver and found that there was a mistake in the device-trees. The updated polarity also matches the boards schematics. Now DRM bridges support becomes mandatory since LVDS is getting disabled during of the encoder driver probing. I'll send the DRM patch separately from this series.
- Replaced recently deprecated CONFIG_DRM_LVDS_ENCODER with the new CONFIG_DRM_LVDS_CODEC in tegra_defconfig.
- Added more config options to tegra_defconfig, like pstore and thermal.
- Added atmel,cfg_name to the A500 DT, which is a new upcoming property in 5.8+ that allows to specify the per-board hardware config file name.
v2: - Corrected "volume down" key-label in the grouper's device-tree and
improved some other names in device-trees.
- Added optional (upcoming in 5.8+) VDD/AVDD regulators to the touchscreen node in A500 device-tree.
Dmitry Osipenko (6):
ARM: tegra: Add device-tree for Acer Iconia Tab A500
ARM: tegra: Add device-tree for ASUS Google Nexus 7
dt-bindings: Add vendor prefix for Acer Inc.
dt-bindings: ARM: tegra: Add Acer Iconia Tab A500
dt-bindings: ARM: tegra: Add ASUS Google Nexus 7
ARM: tegra_defconfig: Enable options useful for Nexus 7 and Acer A500
.../devicetree/bindings/arm/tegra.yaml | 10 + .../devicetree/bindings/vendor-prefixes.yaml | 2 + arch/arm/boot/dts/Makefile | 4 + .../boot/dts/tegra20-acer-a500-picasso.dts | 1458 ++++++++++ .../dts/tegra30-asus-nexus7-grouper-E1565.dts | 9 + .../dts/tegra30-asus-nexus7-grouper-PM269.dts | 9 + .../tegra30-asus-nexus7-grouper-common.dtsi | 2503 +++++++++++++++++ ...egra30-asus-nexus7-grouper-maxim-pmic.dtsi | 188 ++ .../tegra30-asus-nexus7-grouper-ti-pmic.dtsi | 151 + .../boot/dts/tegra30-asus-nexus7-grouper.dtsi | 462 +++ .../dts/tegra30-asus-nexus7-tilapia-E1565.dts | 9 + .../boot/dts/tegra30-asus-nexus7-tilapia.dtsi | 548 ++++ arch/arm/configs/tegra_defconfig | 42 + 13 files changed, 5395 insertions(+) create mode 100644 arch/arm/boot/dts/tegra20-acer-a500-picasso.dts create mode 100644 arch/arm/boot/dts/tegra30-asus-nexus7-grouper-E1565.dts create mode 100644 arch/arm/boot/dts/tegra30-asus-nexus7-grouper-PM269.dts create mode 100644 arch/arm/boot/dts/tegra30-asus-nexus7-grouper-common.dtsi create mode 100644 arch/arm/boot/dts/tegra30-asus-nexus7-grouper-maxim-pmic.dtsi create mode 100644 arch/arm/boot/dts/tegra30-asus-nexus7-grouper-ti-pmic.dtsi create mode 100644 arch/arm/boot/dts/tegra30-asus-nexus7-grouper.dtsi create mode 100644 arch/arm/boot/dts/tegra30-asus-nexus7-tilapia-E1565.dts create mode 100644 arch/arm/boot/dts/tegra30-asus-nexus7-tilapia.dtsi
Signature · 1 line
2.26.0
PATCH v8 1/6 ARM: tegra: Add device-tree for Acer Iconia Tab A500
Add device-tree for Acer Iconia Tab A500, which is NVIDIA Tegra20-based tablet device.
--- arch/arm/boot/dts/Makefile | 1 + .../boot/dts/tegra20-acer-a500-picasso.dts | 1458 +++++++++++++++++ 2 files changed, 1459 insertions(+) create mode 100644 arch/arm/boot/dts/tegra20-acer-a500-picasso.dts
arch/arm/boot/dts/Makefile +1 -0
@@ -1190,6 +1190,7 @@ dtb-$(CONFIG_MACH_SUNIV) += \ dtb-$(CONFIG_ARCH_TANGO) += \ tango4-vantage-1172.dtb dtb-$(CONFIG_ARCH_TEGRA_2x_SOC) += \ + tegra20-acer-a500-picasso.dtb \ tegra20-harmony.dtb \ tegra20-colibri-eval-v3.dtb \ tegra20-colibri-iris.dtb \
arch/arm/boot/dts/tegra20-acer-a500-picasso.dts new file +1458 -0
1,458 lines not on this page · raw message
Signature · 1 line
2.26.0
PATCH v8 2/6 ARM: tegra: Add device-tree for ASUS Google Nexus 7
In reply to Dmitry OsipenkoThere are few hardware variants of NVIDIA Tegra30-based Nexus 7 device:
1. WiFi-only (named Grouper)
2. GSM (named Tilapia)
3. Using Maxim PMIC (E1565 board ID)
4. Using Ti PMIC (PM269 board ID)
This patch adds device-trees for known and tested variants.
--- arch/arm/boot/dts/Makefile | 3 + .../dts/tegra30-asus-nexus7-grouper-E1565.dts | 9 + .../dts/tegra30-asus-nexus7-grouper-PM269.dts | 9 + .../tegra30-asus-nexus7-grouper-common.dtsi | 2503 +++++++++++++++++ ...egra30-asus-nexus7-grouper-maxim-pmic.dtsi | 188 ++ .../tegra30-asus-nexus7-grouper-ti-pmic.dtsi | 151 + .../boot/dts/tegra30-asus-nexus7-grouper.dtsi | 462 +++ .../dts/tegra30-asus-nexus7-tilapia-E1565.dts | 9 + .../boot/dts/tegra30-asus-nexus7-tilapia.dtsi | 548 ++++ 9 files changed, 3882 insertions(+) create mode 100644 arch/arm/boot/dts/tegra30-asus-nexus7-grouper-E1565.dts create mode 100644 arch/arm/boot/dts/tegra30-asus-nexus7-grouper-PM269.dts create mode 100644 arch/arm/boot/dts/tegra30-asus-nexus7-grouper-common.dtsi create mode 100644 arch/arm/boot/dts/tegra30-asus-nexus7-grouper-maxim-pmic.dtsi create mode 100644 arch/arm/boot/dts/tegra30-asus-nexus7-grouper-ti-pmic.dtsi create mode 100644 arch/arm/boot/dts/tegra30-asus-nexus7-grouper.dtsi create mode 100644 arch/arm/boot/dts/tegra30-asus-nexus7-tilapia-E1565.dts create mode 100644 arch/arm/boot/dts/tegra30-asus-nexus7-tilapia.dtsi
arch/arm/boot/dts/Makefile +3 -0
@@ -1204,6 +1204,9 @@ dtb-$(CONFIG_ARCH_TEGRA_2x_SOC) += \ dtb-$(CONFIG_ARCH_TEGRA_3x_SOC) += \ tegra30-apalis-eval.dtb \ tegra30-apalis-v1.1-eval.dtb \ + tegra30-asus-nexus7-grouper-PM269.dtb \ + tegra30-asus-nexus7-grouper-E1565.dtb \ + tegra30-asus-nexus7-tilapia-E1565.dtb \ tegra30-beaver.dtb \ tegra30-cardhu-a02.dtb \ tegra30-cardhu-a04.dtb \
arch/arm/boot/dts/tegra30-asus-nexus7-grouper-E1565.dts new file +9 -0
@@ -0,0 +1,9 @@ +// SPDX-License-Identifier: GPL-2.0 +/dts-v1/; + +#include "tegra30-asus-nexus7-grouper-maxim-pmic.dtsi" +#include "tegra30-asus-nexus7-grouper.dtsi" + +/ { + model = "ASUS Google Nexus 7 (Project Nakasi / ME370T) E1565"; +};
arch/arm/boot/dts/tegra30-asus-nexus7-grouper-PM269.dts new file +9 -0
@@ -0,0 +1,9 @@ +// SPDX-License-Identifier: GPL-2.0 +/dts-v1/; + +#include "tegra30-asus-nexus7-grouper-ti-pmic.dtsi" +#include "tegra30-asus-nexus7-grouper.dtsi" + +/ { + model = "ASUS Google Nexus 7 (Project Nakasi / ME370T) PM269"; +};
arch/arm/boot/dts/tegra30-asus-nexus7-grouper-common.dtsi new file +2503 -0
2,503 lines not on this page · raw message
arch/arm/boot/dts/tegra30-asus-nexus7-grouper-maxim-pmic.dtsi new file +188 -0
188 lines not on this page · raw message
arch/arm/boot/dts/tegra30-asus-nexus7-grouper-ti-pmic.dtsi new file +151 -0
151 lines not on this page · raw message
arch/arm/boot/dts/tegra30-asus-nexus7-grouper.dtsi new file +462 -0
131 lines not on this page · raw message
arch/arm/boot/dts/tegra30-asus-nexus7-tilapia-E1565.dts new file +9 -0
Lines of this file are not shown. View the raw message.
arch/arm/boot/dts/tegra30-asus-nexus7-tilapia.dtsi new file +548 -0
548 lines not on this page · raw message
The rest of this diff is not shown. View the raw message.
Signature · 1 line
2.26.0
Part of the diff is not shown here. View the raw message.
Re: [PATCH v8 2/6] ARM: tegra: Add device-tree for ASUS Google Nexus 7
Quoted 6 lines · Dmitry Osipenko
There are few hardware variants of NVIDIA Tegra30-based Nexus 7 device:
1. WiFi-only (named Grouper)
2. GSM (named Tilapia)
3. Using Maxim PMIC (E1565 board ID)
4. Using Ti PMIC (PM269 board ID)
Hi,
I've briefly looked at the PM269 devicetree (PMIC part) and it looks very similar, if not the same, to what I deduced from the TF300T kernel. Those devices don't look to differ much from original Cardhu tablet devkit, so maybe the trees can base off of that?
I would also guess that because of this 'ram-code', memory timings would be duplicated between devices. I can see small differences between ram-code=1 timings of Grouper and TF300T, though they look like arbiter tuning differences. I'll have to test if my TF300T works with Grouper's settings. In case they work, could you split the memory timings to another dtsi file?
BTW, shouldn't EMC timing set match MC? I see more frequencies listed in MC than EMC nodes.
Best Regards,
Michał Mirosław
Re: [PATCH v8 2/6] ARM: tegra: Add device-tree for ASUS Google Nexus 7
15.05.2020 21:18, Michał Mirosław пишет:
Quoted 8 lines · Dmitry Osipenko
Quoted 6 lines
There are few hardware variants of NVIDIA Tegra30-based Nexus 7 device:
1. WiFi-only (named Grouper)
2. GSM (named Tilapia)
3. Using Maxim PMIC (E1565 board ID)
4. Using Ti PMIC (PM269 board ID)
Quoted 4 lines
Hi,
I've briefly looked at the PM269 devicetree (PMIC part) and it looks very similar, if not the same, to what I deduced from the TF300T kernel.
Hello Michał,
Definitely there are board parts that are reused by different devices. This is not surprising since most of the boards are designed by the same company.
Quoted 2 lines
Those devices don't look to differ much from original Cardhu tablet devkit, so maybe the trees can base off of that?
I don't think it's really possible in a case of Nexus 7 because in overall the used hardware components differ a bit too much. It shouldn't worth the effort, IMO.
Quoted 6 lines
I would also guess that because of this 'ram-code', memory timings would be duplicated between devices. I can see small differences between ram-code=1 timings of Grouper and TF300T, though they look like arbiter tuning differences. I'll have to test if my TF300T works with Grouper's settings. In case they work, could you split the memory timings to another dtsi file?
Yes, perhaps this could be done. The memory timings on Grouper and Tilapia are pretty much the same as well. As you noticed, there are some tuning differences of TF300T in comparison to the Nexus 7, the same applies to the Grouper and Tilapia variants.
Quoted 2 lines
BTW, shouldn't EMC timing set match MC? I see more frequencies listed in MC than EMC nodes.
The MC timings are exactly the same on Grouper and Tilapia, but EMC timings have a very minor differences, and thus, the common.dtsi misses these differentiating EMC timings, they are defined in grouper.dtsi and tilapia.dts.
I guess we indeed could try to select the lowest common denominator timing and re-use it. I'll consider this change for v9, thank you very much for the suggestion.
Re: [PATCH v8 2/6] ARM: tegra: Add device-tree for ASUS Google Nexus 7
16.05.2020 15:01, Dmitry Osipenko пишет:
Quoted 42 lines
15.05.2020 21:18, Michał Mirosław пишет:
Quoted 8 lines · Dmitry Osipenko
Quoted 6 lines
There are few hardware variants of NVIDIA Tegra30-based Nexus 7 device:
1. WiFi-only (named Grouper)
2. GSM (named Tilapia)
3. Using Maxim PMIC (E1565 board ID)
4. Using Ti PMIC (PM269 board ID)Quoted 4 lines
Hi,
I've briefly looked at the PM269 devicetree (PMIC part) and it looks very similar, if not the same, to what I deduced from the TF300T kernel.
Hello Michał,
Definitely there are board parts that are reused by different devices. This is not surprising since most of the boards are designed by the same company.
Quoted 2 lines
Those devices don't look to differ much from original Cardhu tablet devkit, so maybe the trees can base off of that?
I don't think it's really possible in a case of Nexus 7 because in overall the used hardware components differ a bit too much. It shouldn't worth the effort, IMO.
Quoted 6 lines
I would also guess that because of this 'ram-code', memory timings would be duplicated between devices. I can see small differences between ram-code=1 timings of Grouper and TF300T, though they look like arbiter tuning differences. I'll have to test if my TF300T works with Grouper's settings. In case they work, could you split the memory timings to another dtsi file?
Yes, perhaps this could be done. The memory timings on Grouper and Tilapia are pretty much the same as well. As you noticed, there are some tuning differences of TF300T in comparison to the Nexus 7, the same applies to the Grouper and Tilapia variants.
Quoted 2 lines
BTW, shouldn't EMC timing set match MC? I see more frequencies listed in MC than EMC nodes.
Quoted 8 lines
The MC timings are exactly the same on Grouper and Tilapia, but EMC timings have a very minor differences, and thus, the
common.dtsimisses these differentiating EMC timings, they are defined ingrouper.dtsiandtilapia.dts.I guess we indeed could try to select the lowest common denominator timing and re-use it. I'll consider this change for v9, thank you very much for the suggestion.
Hello Michał,
I tried to investigate whether we could unify the memory timings and it's hard to tell. The values are mostly off by one in most cases for one or two registers, in others cases a memory-chip feature is enabled or disabled for the same memory module. It certainly feels like we could safely ignore all those minor differences, but I don't have enough expertise in order to decide firmly. In my opinion it should be better to leave the memory timings as-is for the starter, we could always get back to the unification later on.
PATCH v8 3/6 dt-bindings: Add vendor prefix for Acer Inc.
In reply to Dmitry OsipenkoAcer is a hardware and electronics corporation, specializing in advanced electronics technology. Acer's products include desktop PCs, laptop PCs, tablets, servers, displays, storage devices, virtual reality devices, smartphones and peripherals. Their web site is http://www.acer.com/.
--- Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++ 1 file changed, 2 insertions(+)
Documentation/devicetree/bindings/vendor-prefixes.yaml +2 -0
@@ -27,6 +27,8 @@ patternProperties: description: Abilis Systems "^abracon,.*": description: Abracon Corporation + "^acer,.*": + description: Acer Inc. "^acme,.*": description: Acme Systems srl "^actions,.*":
Signature · 1 line
2.26.0
PATCH v8 4/6 dt-bindings: ARM: tegra: Add Acer Iconia Tab A500
In reply to Dmitry OsipenkoAdd a binding for the Tegra20-based Acer Iconia Tab A500 tablet device.
--- Documentation/devicetree/bindings/arm/tegra.yaml | 3 +++ 1 file changed, 3 insertions(+)
Documentation/devicetree/bindings/arm/tegra.yaml +3 -0
@@ -34,6 +34,9 @@ properties: - toradex,colibri_t20-iris - const: toradex,colibri_t20 - const: nvidia,tegra20 + - items: + - const: acer,picasso + - const: nvidia,tegra20 - items: - enum: - nvidia,beaver
Signature · 1 line
2.26.0
PATCH v8 5/6 dt-bindings: ARM: tegra: Add ASUS Google Nexus 7
In reply to Dmitry OsipenkoAdd a binding for the Tegra30-based ASUS Google Nexus 7 tablet device.
--- Documentation/devicetree/bindings/arm/tegra.yaml | 7 +++++++ 1 file changed, 7 insertions(+)
Documentation/devicetree/bindings/arm/tegra.yaml +7 -0
@@ -62,6 +62,13 @@ properties: - toradex,colibri_t30-eval-v3 - const: toradex,colibri_t30 - const: nvidia,tegra30 + - items: + - const: asus,grouper + - const: nvidia,tegra30 + - items: + - const: asus,tilapia + - const: asus,grouper + - const: nvidia,tegra30 - items: - enum: - nvidia,dalmore
Signature · 1 line
2.26.0
PATCH v8 6/6 ARM: tegra_defconfig: Enable options useful for Nexus 7 and Acer A500
In reply to Dmitry OsipenkoEnable several very useful options and drivers for hardware that is found on Nexus 7 and Acer A500 tablet devices. Please note that some drivers may require firmware files extracted from original Android image.
--- arch/arm/configs/tegra_defconfig | 42 ++++++++++++++++++++++++++++++++ 1 file changed, 42 insertions(+)
arch/arm/configs/tegra_defconfig +42 -0
@@ -10,6 +10,8 @@ CONFIG_RT_GROUP_SCHED=y CONFIG_CGROUP_FREEZER=y CONFIG_CGROUP_CPUACCT=y CONFIG_CGROUP_DEBUG=y +CONFIG_NAMESPACES=y +CONFIG_USER_NS=y CONFIG_BLK_DEV_INITRD=y # CONFIG_ELF_CORE is not set CONFIG_EMBEDDED=y
@@ -18,6 +20,7 @@ CONFIG_SLAB=y CONFIG_ARCH_TEGRA=y CONFIG_SMP=y CONFIG_HIGHMEM=y +CONFIG_SECCOMP=y CONFIG_ZBOOT_ROM_TEXT=0x0 CONFIG_ZBOOT_ROM_BSS=0x0 CONFIG_KEXEC=y
@@ -63,11 +66,17 @@ CONFIG_BT_RFCOMM=y CONFIG_BT_BNEP=y CONFIG_BT_HIDP=y CONFIG_BT_HCIBTUSB=m +CONFIG_BT_HCIUART=y +CONFIG_BT_HCIUART_BCM=y CONFIG_CFG80211=y CONFIG_MAC80211=y CONFIG_RFKILL=y CONFIG_RFKILL_INPUT=y CONFIG_RFKILL_GPIO=y +CONFIG_NFC=y +CONFIG_NFC_HCI=y +CONFIG_NFC_SHDLC=y +CONFIG_NFC_PN544_I2C=y CONFIG_PCI=y CONFIG_PCIEPORTBUS=y CONFIG_PCI_MSI=y
@@ -106,20 +115,24 @@ CONFIG_INPUT_JOYDEV=y CONFIG_INPUT_EVDEV=y CONFIG_KEYBOARD_GPIO=y CONFIG_KEYBOARD_TEGRA=y +CONFIG_KEYBOARD_CAP11XX=y CONFIG_KEYBOARD_CROS_EC=y CONFIG_MOUSE_PS2_ELANTECH=y CONFIG_INPUT_TOUCHSCREEN=y CONFIG_TOUCHSCREEN_ATMEL_MXT=y +CONFIG_TOUCHSCREEN_ELAN=y CONFIG_TOUCHSCREEN_WM97XX=y # CONFIG_TOUCHSCREEN_WM9705 is not set # CONFIG_TOUCHSCREEN_WM9713 is not set CONFIG_TOUCHSCREEN_STMPE=y CONFIG_INPUT_MISC=y +CONFIG_INPUT_GPIO_VIBRA=y # CONFIG_LEGACY_PTYS is not set CONFIG_SERIAL_8250=y CONFIG_SERIAL_8250_CONSOLE=y CONFIG_SERIAL_OF_PLATFORM=y CONFIG_SERIAL_TEGRA=y +CONFIG_SERIAL_DEV_BUS=y # CONFIG_HW_RANDOM is not set # CONFIG_I2C_COMPAT is not set CONFIG_I2C_CHARDEV=y
@@ -131,10 +144,12 @@ CONFIG_SPI_TEGRA114=y CONFIG_SPI_TEGRA20_SFLASH=y CONFIG_SPI_TEGRA20_SLINK=y CONFIG_PINCTRL_AS3722=y +CONFIG_PINCTRL_MAX77620=y CONFIG_PINCTRL_PALMAS=y CONFIG_GPIO_SYSFS=y CONFIG_GPIO_PCA953X=y CONFIG_GPIO_PCA953X_IRQ=y +CONFIG_GPIO_MAX77620=y CONFIG_GPIO_PALMAS=y CONFIG_GPIO_TPS6586X=y CONFIG_GPIO_TPS65910=y
@@ -142,13 +157,21 @@ CONFIG_POWER_RESET=y CONFIG_POWER_RESET_AS3722=y CONFIG_POWER_RESET_GPIO=y CONFIG_BATTERY_SBS=y +CONFIG_BATTERY_BQ27XXX=y +CONFIG_CHARGER_GPIO=y +CONFIG_CHARGER_SMB347=y CONFIG_CHARGER_TPS65090=y CONFIG_SENSORS_LM90=y CONFIG_SENSORS_LM95245=y +CONFIG_THERMAL=y +CONFIG_THERMAL_STATISTICS=y +CONFIG_CPU_THERMAL=y CONFIG_WATCHDOG=y +CONFIG_MAX77620_WATCHDOG=y CONFIG_TEGRA_WATCHDOG=y CONFIG_MFD_AS3722=y CONFIG_MFD_CROS_EC=y +CONFIG_MFD_MAX77620=y CONFIG_MFD_MAX8907=y CONFIG_MFD_STMPE=y CONFIG_MFD_PALMAS=y
@@ -159,6 +182,7 @@ CONFIG_REGULATOR=y CONFIG_REGULATOR_FIXED_VOLTAGE=y CONFIG_REGULATOR_AS3722=y CONFIG_REGULATOR_GPIO=y +CONFIG_REGULATOR_MAX77620=y CONFIG_REGULATOR_MAX8907=y CONFIG_REGULATOR_PALMAS=y CONFIG_REGULATOR_TPS51632=y
@@ -174,7 +198,10 @@ CONFIG_USB_GSPCA=y CONFIG_DRM=y CONFIG_DRM_NOUVEAU=m CONFIG_DRM_TEGRA=y +CONFIG_DRM_TEGRA_STAGING=y +CONFIG_DRM_PANEL_LVDS=y CONFIG_DRM_PANEL_SIMPLE=y +CONFIG_DRM_LVDS_CODEC=y # CONFIG_LCD_CLASS_DEVICE is not set CONFIG_BACKLIGHT_CLASS_DEVICE=y # CONFIG_BACKLIGHT_GENERIC is not set
@@ -238,6 +265,7 @@ CONFIG_RTC_CLASS=y CONFIG_RTC_DRV_AS3722=y CONFIG_RTC_DRV_DS1307=y CONFIG_RTC_DRV_MAX8907=y +CONFIG_RTC_DRV_MAX77686=y CONFIG_RTC_DRV_PALMAS=y CONFIG_RTC_DRV_TPS6586X=y CONFIG_RTC_DRV_TPS65910=y
@@ -259,11 +287,18 @@ CONFIG_ARCH_TEGRA_2x_SOC=y CONFIG_ARCH_TEGRA_3x_SOC=y CONFIG_ARCH_TEGRA_114_SOC=y CONFIG_ARCH_TEGRA_124_SOC=y +CONFIG_PM_DEVFREQ=y +CONFIG_ARM_TEGRA_DEVFREQ=y +CONFIG_ARM_TEGRA20_DEVFREQ=y CONFIG_MEMORY=y CONFIG_IIO=y +CONFIG_KXCJK1013=y CONFIG_MPU3050_I2C=y +CONFIG_INV_MPU6050_I2C=y +CONFIG_AL3010=y CONFIG_SENSORS_ISL29018=y CONFIG_SENSORS_ISL29028=y +CONFIG_AK8974=y CONFIG_AK8975=y CONFIG_PWM=y CONFIG_PWM_TEGRA=y
@@ -283,6 +318,13 @@ CONFIG_TMPFS_POSIX_ACL=y CONFIG_SQUASHFS=y CONFIG_SQUASHFS_LZO=y CONFIG_SQUASHFS_XZ=y +CONFIG_PSTORE=y +CONFIG_PSTORE_LZO_COMPRESS=y +CONFIG_PSTORE_LZ4_COMPRESS=y +CONFIG_PSTORE_LZ4HC_COMPRESS=y +CONFIG_PSTORE_842_COMPRESS=y +CONFIG_PSTORE_CONSOLE=y +CONFIG_PSTORE_RAM=y CONFIG_NFS_FS=y CONFIG_NFS_V4=y CONFIG_ROOT_NFS=y
Signature · 1 line
2.26.0