Support for TeeJet Mt.Ventoux
Subsystems (4)
cover Support for TeeJet Mt.Ventoux
Split into two parts:
1. Device tree only to be used with board-generic (only serial works)
2. Full board support via custom machine file for board-testing
Ilya Yanok (2):
mt_ventoux: very basic support for TeeJet Mt.Ventoux board
mt_ventoux: support for TeeJet Mt.Ventoux board
arch/arm/boot/dts/am3517_mt_ventoux.dts | 27 + arch/arm/mach-omap2/Kconfig | 6 + arch/arm/mach-omap2/Makefile | 1 + arch/arm/mach-omap2/board-am3517_mt_ventoux.c | 708 +++++++++++++++++++++++++ arch/arm/plat-omap/include/plat/uncompress.h | 1 + 5 files changed, 743 insertions(+), 0 deletions(-) create mode 100644 arch/arm/boot/dts/am3517_mt_ventoux.dts create mode 100644 arch/arm/mach-omap2/board-am3517_mt_ventoux.c
Signature · 1 line
1.7.6.4
PATCH 1/2 mt_ventoux: very basic support for TeeJet Mt.Ventoux board
Very basic support for TeeJet Mt.Ventoux board. Able to boot via board-generic and ramdisk/initramfs, however most of peripherals are not supported. Produces tons of twl4030 related errors as this board doesn't have twl4030 installed.
--- arch/arm/boot/dts/am3517_mt_ventoux.dts | 27 +++++++++++++++++++++++++++ 1 files changed, 27 insertions(+), 0 deletions(-) create mode 100644 arch/arm/boot/dts/am3517_mt_ventoux.dts
arch/arm/boot/dts/am3517_mt_ventoux.dts new file +27 -0
@@ -0,0 +1,27 @@ +/* + * Copyright (C) 2011 Ilya Yanok, EmCraft Systems + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + */ +/dts-v1/; + +/include/ "omap3.dtsi" + +/ { + model = "TeeJet Mt.Ventoux"; + compatible = "teejet,mt_ventoux", "ti,omap3"; + + memory { + device_type = "memory"; + reg = <0x80000000 0x10000000>; /* 256 MB */ + }; + + /* AM35xx doesn't have IVA */ + soc { + iva { + status = "disabled"; + }; + }; +};
Signature · 1 line
1.7.6.4
PATCH 1/2 mt_ventoux: very basic support for TeeJet Mt.Ventoux board
Quoted 6 lines · Ilya Yanok
Very basic support for TeeJet Mt.Ventoux board. Able to boot via board-generic and ramdisk/initramfs, however most of peripherals are not supported. Produces tons of twl4030 related errors as this board doesn't have twl4030 installed.
Signed-off-by Ilya Yanok <[email protected]>
Comment below, but otherwise:
Quoted 22 lines
--- arch/arm/boot/dts/am3517_mt_ventoux.dts | 27 +++++++++++++++++++++++++++ 1 files changed, 27 insertions(+), 0 deletions(-) create mode 100644 arch/arm/boot/dts/am3517_mt_ventoux.dtsarch/arm/boot/dts/am3517_mt_ventoux.dts new file +11
-0@@ -0,0 +1,27 @@ +/* + * Copyright (C) 2011 Ilya Yanok, EmCraft Systems + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + */ +/dts-v1/; + +/include/ "omap3.dtsi" +
arch/arm/boot/dts/am3517_mt_ventoux.dts line 21
Quoted 10 lines
arch/arm/boot/dts/am3517_mt_ventoux.dts new file +10
-0+/ { + model = "TeeJet Mt.Ventoux"; + compatible = "teejet,mt_ventoux", "ti,omap3"; + + memory { + device_type = "memory"; + reg = <0x80000000 0x10000000>; /* 256 MB */ + }; + + /* AM35xx doesn't have IVA */
Perhaps the AM35xx should have a separate .dtsi file?
Quoted 14 lines
arch/arm/boot/dts/am3517_mt_ventoux.dts new file +6
-0+ soc { + iva { + status = "disabled"; + }; + }; +};Signature · 7 lines
1.7.6.4 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel at lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
PATCH 1/2 mt_ventoux: very basic support for TeeJet Mt.Ventoux board
Hi Grant,
Quoted 11 lines · Grant Likely
Quoted 6 lines · Ilya Yanok
Very basic support for TeeJet Mt.Ventoux board. Able to boot via board-generic and ramdisk/initramfs, however most of peripherals are not supported. Produces tons of twl4030 related errors as this board doesn't have twl4030 installed.
Signed-off-by Ilya Yanok <[email protected]>Comment below, but otherwise:
Acked-by Grant Likely <[email protected]>
Though nothing fundamentally different in regard to DT, but there is a v3 of this patch set available at [1]
Quoted 27 lines
Quoted 27 lines
--- arch/arm/boot/dts/am3517_mt_ventoux.dts | 27 +++++++++++++++++++++++++++ 1 files changed, 27 insertions(+), 0 deletions(-) create mode 100644 arch/arm/boot/dts/am3517_mt_ventoux.dtsarch/arm/boot/dts/am3517_mt_ventoux.dts new file +15
-0@@ -0,0 +1,27 @@ +/* + * Copyright (C) 2011 Ilya Yanok, EmCraft Systems + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + */ +/dts-v1/; + +/include/ "omap3.dtsi" + +/ { + model = "TeeJet Mt.Ventoux"; + compatible = "teejet,mt_ventoux", "ti,omap3"; +
Quoted 8 lines
arch/arm/boot/dts/am3517_mt_ventoux.dts line 21
Quoted 6 lines
arch/arm/boot/dts/am3517_mt_ventoux.dts new file +6
-0+ memory { + device_type = "memory"; + reg = <0x80000000 0x10000000>; /* 256 MB */ + }; + + /* AM35xx doesn't have IVA */Perhaps the AM35xx should have a separate .dtsi file?
In that case there is a possibility you will get multiple <SoC>.dtsi files with the same copy/pasted "disable" stuff. Of course this is better than having multiple board files doing this.
What do you think on splitting the whole thing into <IP>.dtsi files, Like I have explained here [2]?
Quoted 7 lines
arch/arm/boot/dts/am3517_mt_ventoux.dts line 27
Quoted 7 lines
arch/arm/boot/dts/am3517_mt_ventoux.dts new file +6
-0+ soc { + iva { + status = "disabled"; + }; + }; +};
[1] http://www.spinics.net/lists/linux-omap/msg62185.html
[2] http://www.spinics.net/lists/linux-omap/msg61975.html
Signature · 2 lines
Regards, Igor.
PATCH 2/2 mt_ventoux: support for TeeJet Mt.Ventoux board
In reply to Ilya YanokThis patch adds support for TeeJet Mt.Ventoux board based on TAM3517 SOM. Supported devices:
- Serial
- Ethernet
- NAND
- USB host
- LCD
- Touchscreen
- CAN controller
- ADC128S converter
---
Requires updated machine-type file, recently posted AM35xx-EMAC patch and "Disable PM init on AM35{05,17} patch.
arch/arm/mach-omap2/Kconfig | 6 + arch/arm/mach-omap2/Makefile | 1 + arch/arm/mach-omap2/board-am3517_mt_ventoux.c | 708 +++++++++++++++++++++++++ arch/arm/plat-omap/include/plat/uncompress.h | 1 + 4 files changed, 716 insertions(+), 0 deletions(-) create mode 100644 arch/arm/mach-omap2/board-am3517_mt_ventoux.c
arch/arm/mach-omap2/Kconfig +6 -0
@@ -237,6 +237,12 @@ config MACH_MCX select OMAP_PACKAGE_CBB select REGULATOR_FIXED_VOLTAGE +config MACH_AM3517_MT_VENTOUX + bool "TeeJet MT_VENTOUX (TAM3517 based) board" + depends on ARCH_OMAP3 + select OMAP_PACKAGE_CBB + select REGULATOR_FIXED_VOLTAGE + config MACH_NOKIA_N800 bool
arch/arm/mach-omap2/Makefile +1 -0
@@ -239,6 +239,7 @@ obj-$(CONFIG_MACH_SBC3530) += board-omap3stalker.o obj-$(CONFIG_MACH_TI8168EVM) += board-ti8168evm.o obj-$(CONFIG_MACH_TI8148EVM) += board-ti8168evm.o obj-$(CONFIG_MACH_MCX) += board-mcx.o +obj-$(CONFIG_MACH_AM3517_MT_VENTOUX) += board-am3517_mt_ventoux.o # Platform specific device init code
arch/arm/mach-omap2/board-am3517_mt_ventoux.c new file +708 -0
708 lines not on this page · raw message
arch/arm/plat-omap/include/plat/uncompress.h +1 -0
@@ -145,6 +145,7 @@ static inline void __arch_decomp_setup(unsigned long arch_id)DEBUG_LL_OMAP2 (3 , nokia_n810_wimax);/* omap3 based boards using UART1 */ +DEBUG_LL_OMAP3 (1 , am3517_mt_ventoux);DEBUG_LL_OMAP2 (1 , omap3evm);DEBUG_LL_OMAP3 (1 , omap_3430sdp);DEBUG_LL_OMAP3 (1 , omap_3630sdp);
Signature · 1 line
1.7.6.4
PATCH 2/2 mt_ventoux: support for TeeJet Mt.Ventoux board
Hi Ilya,
Quoted 22 lines · Ilya Yanok
This patch adds support for TeeJet Mt.Ventoux board based on TAM3517 SOM. Supported devices:
- Serial
- Ethernet
- NAND
- USB host
- LCD
- Touchscreen
- CAN controller
- ADC128S converterSigned-off-by Ilya Yanok <[email protected]>---
Requires updated machine-type file, recently posted AM35xx-EMAC patch and "Disable PM init on AM35{05,17} patch.arch/arm/mach-omap2/Kconfig | 6 + arch/arm/mach-omap2/Makefile | 1 + arch/arm/mach-omap2/board-am3517_mt_ventoux.c | 708 +++++++++++++++++++++++++ arch/arm/plat-omap/include/plat/uncompress.h | 1 + 4 files changed, 716 insertions(+), 0 deletions(-) create mode 100644 arch/arm/mach-omap2/board-am3517_mt_ventoux.c
[...]
Quoted 5 lines
arch/arm/mach-omap2/board-am3517_mt_ventoux.c new file +0
-0
[...]
arch/arm/mach-omap2/board-am3517_mt_ventoux.c line 211
Quoted 8 lines
arch/arm/mach-omap2/board-am3517_mt_ventoux.c new file +8
-0+/* +* use fake regulator for vdds_dsi as we can't find this pin inside +* AM3517 datasheet. +*/ +static struct regulator_consumer_supply mt_ventoux_vdds_dsi_supply[] = { +REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss" ), +REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss_dsi.0" ), +};
Although the TRM states that there is a vdds_dsi signal, it looks, from the datasheet, that VDDSHV is used to power the DSS. Either way, it can't be switched off, I think... Therefore, depending on your board wiring, you can leave it as fixed regulator or bind to a supply on TPS65023.
[...]
arch/arm/mach-omap2/board-am3517_mt_ventoux.c line 394
Quoted 10 lines
arch/arm/mach-omap2/board-am3517_mt_ventoux.c new file +10
-0+static struct i2c_board_info __initdata mt_ventoux_i2c1_devices[] = { + { +I2C_BOARD_INFO ("tps65023" ,0x48 ), + .flags =I2C_CLIENT_WAKE , + .platform_data = &mt_ventoux_regulator_data[0 ], + }, + { +I2C_BOARD_INFO ("24c02" ,0x50 ), + }, +};
Here (and may be in some other places) you have spaces for indentation. Can it be tabs instead for uniformity (and file size)?
arch/arm/mach-omap2/board-am3517_mt_ventoux.c line 400
Quoted 6 lines
arch/arm/mach-omap2/board-am3517_mt_ventoux.c new file +6
-0+ +static struct i2c_board_info __initdata mt_ventoux_i2c2_devices[] = { + { +I2C_BOARD_INFO ("24c02" ,0x50 ), + }, +};
also here...
[...]
Quoted 1 line
+#if
defined(CONFIG_TOUCHSCREEN_ADS7846)
Can't the ADS7846 be module?
Quoted 12 lines
arch/arm/mach-omap2/board-am3517_mt_ventoux.c new file +12
-0+static struct ads7846_platform_data tsc2046_config__initdata = { + .x_max =0x0fff , + .y_max =0x0fff , + .x_plate_ohms =180 , + .pressure_max =255 , + .debounce_max =30 , + .debounce_tol =10 , + .debounce_rep =1 , + .keep_vref_on =1 , + .settle_delay_usecs =100 , +}; +#endif
[...]
Quoted 11 lines
arch/arm/mach-omap2/board-am3517_mt_ventoux.c new file +11
-0+static void __init mt_ventoux_init (void ) +{ +omap3_mux_init (board_mux,OMAP_PACKAGE_CBB ); +mt_ventoux_i2c_init (); +platform_add_devices (mt_ventoux_devices,ARRAY_SIZE (mt_ventoux_devices)); +mt_ventoux_serial_init (); +omap_sdrc_init (NULL ,NULL ); + +mt_ventoux_display_init (); + +/* Configure EHCI ports */
arch/arm/mach-omap2/board-am3517_mt_ventoux.c line 679
Quoted 10 lines
arch/arm/mach-omap2/board-am3517_mt_ventoux.c new file +10
-0+omap_mux_init_gpio (USB_PHY1_RESET ,OMAP_PIN_OUTPUT ); +usbhs_init (&usbhs_bdata); + +/* NAND */ +omap_nand_flash_init (NAND_BUSWIDTH_16 , mt_ventoux_nand_partitions, +ARRAY_SIZE (mt_ventoux_nand_partitions)); + +/* touchscreen */ +omap_mux_init_gpio (TS_IRQ_PIN ,OMAP_PIN_INPUT ); +omap_ads7846_init (1 ,TS_IRQ_PIN ,310 , &tsc2046_config);
Here you call omap_ads7846_init() irregardless to CONFIG_TOUCHSCREEN_ADS7846, but the tsc2046_config is defined only if it is enabled...
I think, either remove the #ifdef CONFIG_TOUCHSCREEN_ADS7846 or move the above to a separate function like mt_ventoux_touch_init() and provide a static inline version of it in case the CONFIG_TOUCHSCREEN_ADS7846 is not enabled (just like you did for adc128s_init()).
Otherwise, various rand_configs will fail...
arch/arm/mach-omap2/board-am3517_mt_ventoux.c line 689
Quoted 10 lines
arch/arm/mach-omap2/board-am3517_mt_ventoux.c new file +10
-0+ +/* Ethernet */ +am35xx_ethernet_init (MCX_MDIO_FREQUENCY ,1 ); + +/* MMC init */ +omap_mux_init_gpio (SD_CARD_CD ,OMAP_PIN_INPUT ); +omap2_hsmmc_init (mmc); + +/* ADC128S022 init */ +adc128s_init ();
I think you are missing the __init annotation in the adc128s_init() function definition (just noticed after snipping).
Quoted 1 line
+}
[...]
Signature · 2 lines
Regards, Igor.
PATCH 2/2 mt_ventoux: support for TeeJet Mt.Ventoux board
Hi Igor,
thanks for your comments.
Quoted 6 lines · Igor Grinberg
Quoted 6 lines
arch/arm/mach-omap2/board-am3517_mt_ventoux.c new file +6
-0+/* +* use fake regulator for vdds_dsi as we can't find this pin inside +* AM3517 datasheet. +*/ +static struct regulator_consumer_supply mt_ventoux_vdds_dsi_supply[] = { +REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss" ),
Quoted 8 lines
Review
Quoted 2 lines
(quoted diff) +2
-0+ REGULATOR_SUPPLY("vdds_dsi", "omapdss_dsi.0"), +};Although the TRM states that there is a
vdds_dsisignal, it looks, from the datasheet, that VDDSHV is used to power the DSS. Either way, it can't be switched off, I think... Therefore, depending on your board wiring, you can leave it as fixed regulator or bind to a supply on TPS65023.
I will forward this info to hardware guys and ask about wiring. For now I will leave it as is. Thanks for this information it turned to be some kind of mystery. It would be great if you could give some pointer to the datasheet regarding VDDSHV and DSS.
Quoted 5 lines
Quoted 5 lines
arch/arm/mach-omap2/board-am3517_mt_ventoux.c new file +5
-0+static struct i2c_board_info __initdata mt_ventoux_i2c1_devices[] = { + { +I2C_BOARD_INFO ("tps65023" ,0x48 ), + .flags =I2C_CLIENT_WAKE , + .platform_data = &mt_ventoux_regulator_data[0 ],
Quoted 8 lines
arch/arm/mach-omap2/board-am3517_mt_ventoux.c line 394
Quoted 5 lines
arch/arm/mach-omap2/board-am3517_mt_ventoux.c new file +5
-0+ }, + { + I2C_BOARD_INFO("24c02", 0x50), + }, +};Here (and may be in some other places) you have spaces for indentation. Can it be tabs instead for uniformity (and file size)?
Argh.. Surely. I should have noticed this myself.
Quoted 3 lines
Quoted 1 line
+#if
defined(CONFIG_TOUCHSCREEN_ADS7846)Can't the ADS7846 be module?
Surely. Fixed.
Quoted 38 lines
Quoted 12 lines
arch/arm/mach-omap2/board-am3517_mt_ventoux.c new file +12
-0+static struct ads7846_platform_data tsc2046_config__initdata = { + .x_max =0x0fff , + .y_max =0x0fff , + .x_plate_ohms =180 , + .pressure_max =255 , + .debounce_max =30 , + .debounce_tol =10 , + .debounce_rep =1 , + .keep_vref_on =1 , + .settle_delay_usecs =100 , +}; +#endif [...]
Quoted 11 lines
arch/arm/mach-omap2/board-am3517_mt_ventoux.c new file +11
-0+static void __init mt_ventoux_init (void ) +{ +omap3_mux_init (board_mux,OMAP_PACKAGE_CBB ); +mt_ventoux_i2c_init (); +platform_add_devices (mt_ventoux_devices,ARRAY_SIZE (mt_ventoux_devices)); +mt_ventoux_serial_init (); +omap_sdrc_init (NULL ,NULL ); + +mt_ventoux_display_init (); + +/* Configure EHCI ports */ arch/arm/mach-omap2/board-am3517_mt_ventoux.c line 679
Quoted 10 lines
arch/arm/mach-omap2/board-am3517_mt_ventoux.c new file +10
-0+omap_mux_init_gpio (USB_PHY1_RESET ,OMAP_PIN_OUTPUT ); +usbhs_init (&usbhs_bdata); + +/* NAND */ +omap_nand_flash_init (NAND_BUSWIDTH_16 , mt_ventoux_nand_partitions, +ARRAY_SIZE (mt_ventoux_nand_partitions)); + +/* touchscreen */ +omap_mux_init_gpio (TS_IRQ_PIN ,OMAP_PIN_INPUT ); +omap_ads7846_init (1 ,TS_IRQ_PIN ,310 , &tsc2046_config);Here you call
omap_ads7846_init()irregardless to
Quoted 8 lines
CONFIG_TOUCHSCREEN_ADS7846, but thetsc2046_configis defined only if it is enabled...
I think, either remove the #ifdefCONFIG_TOUCHSCREEN_ADS7846or move the above to a separate function likemt_ventoux_touch_init()and provide a static inline version of it in case theCONFIG_TOUCHSCREEN_ADS7846is not enabled (just like you did foradc128s_init()).
Otherwise, variousrand_configswill fail...
Agreed. Fixed.
Quoted 4 lines
Quoted 4 lines
arch/arm/mach-omap2/board-am3517_mt_ventoux.c new file +4
-0+/* Ethernet */ +am35xx_ethernet_init (MCX_MDIO_FREQUENCY ,1 ); + +/* MMC init */
Quoted 8 lines
arch/arm/mach-omap2/board-am3517_mt_ventoux.c line 689
Quoted 5 lines
arch/arm/mach-omap2/board-am3517_mt_ventoux.c new file +5
-0+omap_mux_init_gpio (SD_CARD_CD ,OMAP_PIN_INPUT ); +omap2_hsmmc_init (mmc); + +/* ADC128S022 init */ +adc128s_init ();I think you are missing the
__initannotation in theadc128s_init()function definition (just noticed after snipping).
Well, it's declared as inline so I think there is no much use for the __init annotation...
Regards, Ilya.
PATCH 2/2 mt_ventoux: support for TeeJet Mt.Ventoux board
Hi Ilya,
Quoted 16 lines · Ilya Yanok
Quoted 6 lines · Igor Grinberg
Quoted 6 lines
arch/arm/mach-omap2/board-am3517_mt_ventoux.c new file +6
-0+/* +* use fake regulator for vdds_dsi as we can't find this pin inside +* AM3517 datasheet. +*/ +static struct regulator_consumer_supply mt_ventoux_vdds_dsi_supply[] = { +REGULATOR_SUPPLY ("vdds_dsi" ,"omapdss" ),Quoted 8 lines
Review
Quoted 2 lines
(quoted diff) +2
-0+ REGULATOR_SUPPLY("vdds_dsi", "omapdss_dsi.0"), +};Although the TRM states that there is a
vdds_dsisignal, it looks, from the datasheet, that VDDSHV is used to power the DSS. Either way, it can't be switched off, I think... Therefore, depending on your board wiring, you can leave it as fixed regulator or bind to a supply on TPS65023.
Quoted 4 lines
I will forward this info to hardware guys and ask about wiring. For now I will leave it as is. Thanks for this information it turned to be some kind of mystery. It would be great if you could give some pointer to the datasheet regarding VDDSHV and DSS.
Well, there is no direct pointer to that information, but
I've found these facts:
1) the "Ball Characteristics" tables state that the DSS related pins (and also many others) are powered by the VDDSHV.
2) the estimated power consumption of VDDSHV is the largest after the VDD_CORE, which is typical for DSS, but it is also one of the largest power domains, so I guess this cannot be a valid argument ;-)
3) On the "Voltage domains" diagram, only the VDD_CORE is exposed and DSS is not listed in it, but there are other domains which are not exposed... (this only can exclude the DSS from VDD_CORE, but not absolutely, as datasheets can have mistakes or just not give that piece of information).
Still, it is a guess and not verified information.
[...]
Signature · 2 lines
Regards, Igor.
PATCH 2/2 mt_ventoux: support for TeeJet Mt.Ventoux board
Hi Igor,
Quoted 18 lines · Igor Grinberg
Quoted 4 lines
I will forward this info to hardware guys and ask about wiring. For now I will leave it as is. Thanks for this information it turned to be some kind of mystery. It would be great if you could give some pointer to the datasheet regarding VDDSHV and DSS.
Well, there is no direct pointer to that information, but
I've found these facts:
1) the "Ball Characteristics" tables state that the DSS related pins (and also many others) are powered by the VDDSHV.
2) the estimated power consumption of VDDSHV is the largest after theVDD_CORE, which is typical for DSS, but it is also one of the largest power domains, so I guess this cannot be a valid argument ;-)
3) On the "Voltage domains" diagram, only theVDD_COREis exposed and DSS is not listed in it, but there are other domains which are not exposed... (this only can exclude the DSS fromVDD_CORE, but not absolutely, as datasheets can have mistakes or just not give that piece of information).
Quoted 1 line
Still, it is a guess and not verified information.
Yes, I understand. Thanks for sharing you thoughts!
Regards, Ilya.
PATCH v2 1/1 mt_ventoux: support for TeeJet Mt.Ventoux board
In reply to Ilya YanokThis patch adds support for TeeJet Mt.Ventoux board based on TAM3517 SOM. Supported devices:
- Serial
- Ethernet
- NAND
- USB host
- LCD
- Touchscreen
- CAN controller
- ADC128S converter
---
Changes from V1:
- Fixed indentation (use tabs not spaces)
- Fixed over 80 characters lines
- Added #if defined(CONFIG_SENSORS_ADCXX_MODULE) to allow adcxx to be a module.
- Fixes for compilation with CONFIG_TOUCHSCREEN_ADS7846!=y
- Added defined(CONFIG_TOUCHSCREEN_ADS7846_MODULE)
- Moved call to omap_ads7846_init to separate small function
- Register fixed regulator used for touchscreen only if the driver is enabled
- Changed board name (MT_VENTOUX -> Mt.Ventoux)
arch/arm/mach-omap2/Kconfig | 6 + arch/arm/mach-omap2/Makefile | 1 + arch/arm/mach-omap2/board-am3517_mt_ventoux.c | 724 +++++++++++++++++++++++++ arch/arm/plat-omap/include/plat/uncompress.h | 1 + 4 files changed, 732 insertions(+), 0 deletions(-) create mode 100644 arch/arm/mach-omap2/board-am3517_mt_ventoux.c
arch/arm/mach-omap2/Kconfig +6 -0
@@ -237,6 +237,12 @@ config MACH_MCX select OMAP_PACKAGE_CBB select REGULATOR_FIXED_VOLTAGE +config MACH_AM3517_MT_VENTOUX + bool "TeeJet MT_VENTOUX (TAM3517 based) board" + depends on ARCH_OMAP3 + select OMAP_PACKAGE_CBB + select REGULATOR_FIXED_VOLTAGE + config MACH_NOKIA_N800 bool
arch/arm/mach-omap2/Makefile +1 -0
@@ -239,6 +239,7 @@ obj-$(CONFIG_MACH_SBC3530) += board-omap3stalker.o obj-$(CONFIG_MACH_TI8168EVM) += board-ti8168evm.o obj-$(CONFIG_MACH_TI8148EVM) += board-ti8168evm.o obj-$(CONFIG_MACH_MCX) += board-mcx.o +obj-$(CONFIG_MACH_AM3517_MT_VENTOUX) += board-am3517_mt_ventoux.o # Platform specific device init code
arch/arm/mach-omap2/board-am3517_mt_ventoux.c new file +724 -0
724 lines not on this page · raw message
arch/arm/plat-omap/include/plat/uncompress.h +1 -0
@@ -145,6 +145,7 @@ static inline void __arch_decomp_setup(unsigned long arch_id)DEBUG_LL_OMAP2 (3 , nokia_n810_wimax);/* omap3 based boards using UART1 */ +DEBUG_LL_OMAP3 (1 , am3517_mt_ventoux);DEBUG_LL_OMAP2 (1 , omap3evm);DEBUG_LL_OMAP3 (1 , omap_3430sdp);DEBUG_LL_OMAP3 (1 , omap_3630sdp);
Signature · 1 line
1.7.6.4
PATCH v2 1/1 mt_ventoux: support for TeeJet Mt.Ventoux board
Quoted 16 lines · Ilya Yanok
This patch adds support for TeeJet Mt.Ventoux board based on TAM3517 SOM. Supported devices:
- Serial
- Ethernet
- NAND
- USB host
- LCD
- Touchscreen
- CAN controller
- ADC128S converterSigned-off-by Ilya Yanok <[email protected]>---
Changes from V1:
Quoted 10 lines
- Fixed indentation (use tabs not spaces)
- Fixed over 80 characters lines
- Added #ifdefined(CONFIG_SENSORS_ADCXX_MODULE)to allow adcxx to be a module.
- Fixes for compilation with CONFIG_TOUCHSCREEN_ADS7846!=y
- Addeddefined(CONFIG_TOUCHSCREEN_ADS7846_MODULE)
- Moved call toomap_ads7846_initto separate small function
- Register fixed regulator used for touchscreen only if the driver is enabled
- Changed board name (MT_VENTOUX-> Mt.Ventoux)
Hi Tony,
can I ask you about the status of these patches ? I have not seen open comments, do you think they can be merged in your tree ?
Thanks,
Stefano Babic
Signature · 5 lines
===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de =====================================================================
Tony Lindgren
maintainerPATCH v2 1/1 mt_ventoux: support for TeeJet Mt.Ventoux board
Quoted 28 lines · Stefano Babic
Quoted 16 lines · Ilya Yanok
This patch adds support for TeeJet Mt.Ventoux board based on TAM3517 SOM. Supported devices:
- Serial
- Ethernet
- NAND
- USB host
- LCD
- Touchscreen
- CAN controller
- ADC128S converterSigned-off-by Ilya Yanok <[email protected]>---
Changes from V1:
Quoted 10 lines
- Fixed indentation (use tabs not spaces)
- Fixed over 80 characters lines
- Added #ifdefined(CONFIG_SENSORS_ADCXX_MODULE)to allow adcxx to be a module.
- Fixes for compilation with CONFIG_TOUCHSCREEN_ADS7846!=y
- Addeddefined(CONFIG_TOUCHSCREEN_ADS7846_MODULE)
- Moved call toomap_ads7846_initto separate small function
- Register fixed regulator used for touchscreen only if the driver is enabled
- Changed board name (MT_VENTOUX-> Mt.Ventoux)
Quoted 4 lines
Hi Tony,
can I ask you about the status of these patches ? I have not seen open comments, do you think they can be merged in your tree ?
Yes I can carry some board-*.c files until device tree is usable for basic features. There's still some hsmmc changes pending that I'd like to get out of the way before adding new ones as then it means I have to keep updating those board files separately.
Regards,
Tony