Re: [PATCH v3] davinci: Add MityDSP-L138/MityARM-1808 SOM support
On 7/26/2010 5:29 AM, Nori, Sekhar wrote:
+
+static struct davinci_i2c_platform_data mityomap_i2c_0_pdata = {
+.bus_freq= 100,/* kHz */
+.bus_delay= 0,/* usec */
+};
This is exactly the pdata that davinci I2C driver uses by default,
so you can save a few bytes and a few lines of code by passing NULL
pdata.
[...]
So I tried your suggestion and passed NULL as the pdata argument, e.g.,
...
ret = da8xx_register_i2c(0, NULL);
...
and the kernel locks up during initialization. Did I not understand
what you were suggesting? I will back this suggestion out until I get a chance
to hunt down the problem. I see no other boards initialize the i2c this
way (they explicitly provide a structure).
Thanks.
-Mike
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Boot time
Hi guys, I'm trying to make by board boot as quick as possible. I did some optimisation with the All This For 1 Second Boot wiki and other website. I would like to reduce a little bit more the boot time and I wonder if you guys could give me some clues. I copied my boot log below. For sure I'll remove the uboot autoboot delay and probably build a new kernel with modules. I putted in bold part that I think it is possible to do more optimisation. 1- See bullet #3. 2- The verifying Checksum is about 400 msec is it possible to skip it? 3- It takes ~1 sec to start booting the kernel and there is a other ~1 sec delay between the starting kernel and the beginning of the uncompressing. Why it's so long? Ok maybe there is the copy from NOR to RAM but it should not take more than few msec. 4- It takes ~1 sec to the kernel to free 120K memory... I got enought RAM is it possible to remove it? I got custom hardware based on OMAP-L138 with FS (jffs2) and compressed kernel in NOR Flash. Thanks a lot Nicolas - 0.000 0.000: OMAP-L138 initialization passed! 0.000 0.000: Booting TI User Boot Loader 0.004 0.004:UBL Version: 1.65 0.004 0.000:UBL Flashtype: NOR 0.008 0.004: Starting NOR Copy... 0.008 0.000: CFI Query...passed. 0.012 0.004: NOR Initialization: 0.012 0.000:Command Set: Intel 0.012 0.000:Manufacturer: INTEL 0.016 0.004:Size: 0x0020 MB 0.020 0.004: Valid magicnum, 0x55424CBB, found.. 0.184 0.164:DONE 0.188 0.004: Jumping to entry point at 0xC108. 0.504 0.316: 1.548 1.044: Hit any key to stop autoboot: 0 *2.372 0.824: ## Booting kernel from Legacy Image at c0007fc0 ...* 2.372 0.000:Image Name: Linux-2.6.34 2.380 0.008:Image Type: ARM Linux Kernel Image (uncompressed) 2.380 0.000:Data Size:1505956 Bytes = 1.4 MB 2.384 0.004:Load Address: c0008000 2.388 0.004:Entry Point: c0008000 *2.808 0.420:Verifying Checksum ... OK* 2.808 0.000:Loading Kernel Image ... OK 2.808 0.000: OK 2.808 0.000: *2.812 0.004: Starting kernel ...* *2.812 0.000:* *3.860 1.048: Uncompressing Linux... done, booting the kernel.* 4.264 0.404: Linux version 2.6.34 (i...@idt-ubuntu-linux) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #89 PREEMPT Thu Jul 22 15:24:03 EDT 2010 4.268 0.004: CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177 4.272 0.004: CPU: VIVT data cache, VIVT instruction cache 4.276 0.004: Machine: DaVinci DA850/OMAP-L138 EVM 4.280 0.004: Memory policy: ECC disabled, Data cache writeback 4.284 0.004: DaVinci da850/omap-l138 variant 0x0 4.288 0.004: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 4.300 0.012: Kernel command line: lpj=747520 mem=128M console=ttyS2,115200n8 root=/dev/mtdblock2 rootfstype=jffs2 rw ip=off 4.304 0.004: PID hash table entries: 512 (order: -1, 2048 bytes) 4.308 0.004: Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) 4.316 0.008: Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) 4.316 0.000: Memory: 128MB = 128MB total 4.324 0.008: Memory: 126752k/126752k available, 4320k reserved, 0K highmem 4.324 0.000: Virtual kernel memory layout: 4.332 0.008: vector : 0x - 0x1000 ( 4 kB) 4.336 0.004: fixmap : 0xfff0 - 0xfffe ( 896 kB) 4.340 0.004: DMA : 0xff00 - 0xffe0 ( 14 MB) 4.344 0.004: vmalloc : 0xc880 - 0xfea0 ( 866 MB) 4.348 0.004: lowmem : 0xc000 - 0xc800 ( 128 MB) 4.352 0.004: modules : 0xbf00 - 0xc000 ( 16 MB) 4.356 0.004: .init : 0xc0008000 - 0xc0026000 ( 120 kB) 4.360 0.004: .text : 0xc0026000 - 0xc02e8000 (2824 kB) 4.364 0.004: .data : 0xc02e8000 - 0xc0307a60 ( 127 kB) 4.372 0.008: SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 4.376 0.004: Hierarchical RCU implementation. 4.376 0.000: NR_IRQS:245 4.380 0.004: Console: colour dummy device 80x30 4.384 0.004: Calibrating delay loop (skipped) preset value.. 149.50 BogoMIPS (lpj=747520) 4.388 0.004: Mount-cache hash table entries: 512 4.392 0.004: CPU: Testing write buffer coherency: ok 4.396 0.004: DaVinci: 144 gpio irqs 4.396 0.000: NET: Registered protocol family 16 4.400 0.004: bio: create slab bio-0 at 0 4.404 0.004: SCSI subsystem initialized 4.408 0.004: usbcore: registered new interface driver usbfs 4.412 0.004: usbcore: registered new interface driver hub 4.416 0.004: usbcore: registered new device driver usb 4.416 0.000: Switching to clocksource timer0_1 4.420 0.004: musb_hdrc: version 6.0, pio, host, debug=0 4.424 0.004: Waiting for USB PHY clock good... 4.428 0.004: musb_hdrc musb_hdrc: MUSB HDRC host driver 4.432 0.004: musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1 4.436 0.004: hub 1-0:1.0: USB hub found 4.440 0.004: hub 1-0:1.0: 1 port detected 4.444 0.004: musb_hdrc musb_hdrc: USB Host mode controller at fee0 using PIO, IRQ 58 4.448 0.004: NET:
Re: Touchscreen - MFD driver for TPS6507x family
Todd, What do I need to change if I want to use the bitbang i2c driver and stop to get those error messages. I added support for GPIO-based bitbaging I2C into the kernel, anything else to change in the TPS driver source code? Thanks Regards, Nicolas On Wed, Jun 9, 2010 at 4:17 PM, Todd Fischer todd.fisc...@ridgerun.comwrote: HI Bastian and Nicolas, I recall getting this error when I wasn't using the bitbang i2c driver on the OMAP-L138. Todd On Wed, 2010-06-09 at 10:59 +0200, Bastian Ruppert wrote: Hello Nicolas, thanks for the .conf file. this will help you to check if your hardware is ok. It helped. I applied your file on the khilman commit you are using but i had to patch the kernel in order to compile drivers/mfd/tps6507x.c . I think if you don`t have the same problems, that is anomalous. After that the touchscreen driver is running on that kernel. It`s a little bit unstable, there are sometimes errors like tps6507x 1-0048: TSC mode read failed i2c_davinci i2c_davinci.1: controller timed out i2c_davinci i2c_davinci.1: initiating i2c bus recovery i2c_davinci i2c_davinci.1: controller timed out i2c_davinci i2c_davinci.1: initiating i2c bus recovery but the hardware can in principle do it. Regards, Bastian. ___ Davinci-linux-open-source mailing list davinci-linux-open-sou...@linux.davincidsp.comhttp://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: Touchscreen - MFD driver for TPS6507x family
On Wed, 2010-07-28 at 16:46 -0400, Nicolas Luna wrote: Todd, What do I need to change if I want to use the bitbang i2c driver and stop to get those error messages. I added support for GPIO-based bitbaging I2C into the kernel, anything else to change in the TPS driver source code? You need to modify the arm/arch/mach-davinci board file to configure the pinmux as GPIOs, not I2C signaling. Which hardware board are you using? Thanks Regards, Nicolas On Wed, Jun 9, 2010 at 4:17 PM, Todd Fischer todd.fisc...@ridgerun.com wrote: HI Bastian and Nicolas, I recall getting this error when I wasn't using the bitbang i2c driver on the OMAP-L138. Todd On Wed, 2010-06-09 at 10:59 +0200, Bastian Ruppert wrote: Hello Nicolas, thanks for the .conf file. this will help you to check if your hardware is ok. It helped. I applied your file on the khilman commit you are using but i had to patch the kernel in order to compile drivers/mfd/tps6507x.c . I think if you don`t have the same problems, that is anomalous. After that the touchscreen driver is running on that kernel. It`s a little bit unstable, there are sometimes errors like tps6507x 1-0048: TSC mode read failed i2c_davinci i2c_davinci.1: controller timed out i2c_davinci i2c_davinci.1: initiating i2c bus recovery i2c_davinci i2c_davinci.1: controller timed out i2c_davinci i2c_davinci.1: initiating i2c bus recovery but the hardware can in principle do it. Regards, Bastian. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: Touchscreen - MFD driver for TPS6507x family
board-da850-evm.c Nicolas On Wed, Jul 28, 2010 at 4:51 PM, Todd Fischer todd.fisc...@ridgerun.comwrote: On Wed, 2010-07-28 at 16:46 -0400, Nicolas Luna wrote: Todd, What do I need to change if I want to use the bitbang i2c driver and stop to get those error messages. I added support for GPIO-based bitbaging I2C into the kernel, anything else to change in the TPS driver source code? You need to modify the arm/arch/mach-davinci board file to configure the pinmux as GPIOs, not I2C signaling. Which hardware board are you using? Thanks Regards, Nicolas On Wed, Jun 9, 2010 at 4:17 PM, Todd Fischer todd.fisc...@ridgerun.com wrote: HI Bastian and Nicolas, I recall getting this error when I wasn't using the bitbang i2c driver on the OMAP-L138. Todd On Wed, 2010-06-09 at 10:59 +0200, Bastian Ruppert wrote: Hello Nicolas, thanks for the .conf file. this will help you to check if your hardware is ok. It helped. I applied your file on the khilman commit you are using but i had to patch the kernel in order to compile drivers/mfd/tps6507x.c . I think if you don`t have the same problems, that is anomalous. After that the touchscreen driver is running on that kernel. It`s a little bit unstable, there are sometimes errors like tps6507x 1-0048: TSC mode read failed i2c_davinci i2c_davinci.1: controller timed out i2c_davinci i2c_davinci.1: initiating i2c bus recovery i2c_davinci i2c_davinci.1: controller timed out i2c_davinci i2c_davinci.1: initiating i2c bus recovery but the hardware can in principle do it. Regards, Bastian. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: Touchscreen - MFD driver for TPS6507x family
I changed MUX_CFG(DA850, I2C0_SDA, 4, 12, 15, 2, false) MUX_CFG(DA850, I2C0_SCL, 4, 8, 15, 2, false) to MUX_CFG(DA850, I2C0_SDA, 4, 12, 15, 8, false) MUX_CFG(DA850, I2C0_SCL, 4, 8, 15, 8, false) seems to have the same behaviour.. Nicolas On Wed, Jul 28, 2010 at 5:08 PM, Nicolas Luna luna...@gmail.com wrote: board-da850-evm.c Nicolas On Wed, Jul 28, 2010 at 4:51 PM, Todd Fischer todd.fisc...@ridgerun.comwrote: On Wed, 2010-07-28 at 16:46 -0400, Nicolas Luna wrote: Todd, What do I need to change if I want to use the bitbang i2c driver and stop to get those error messages. I added support for GPIO-based bitbaging I2C into the kernel, anything else to change in the TPS driver source code? You need to modify the arm/arch/mach-davinci board file to configure the pinmux as GPIOs, not I2C signaling. Which hardware board are you using? Thanks Regards, Nicolas On Wed, Jun 9, 2010 at 4:17 PM, Todd Fischer todd.fisc...@ridgerun.com wrote: HI Bastian and Nicolas, I recall getting this error when I wasn't using the bitbang i2c driver on the OMAP-L138. Todd On Wed, 2010-06-09 at 10:59 +0200, Bastian Ruppert wrote: Hello Nicolas, thanks for the .conf file. this will help you to check if your hardware is ok. It helped. I applied your file on the khilman commit you are using but i had to patch the kernel in order to compile drivers/mfd/tps6507x.c . I think if you don`t have the same problems, that is anomalous. After that the touchscreen driver is running on that kernel. It`s a little bit unstable, there are sometimes errors like tps6507x 1-0048: TSC mode read failed i2c_davinci i2c_davinci.1: controller timed out i2c_davinci i2c_davinci.1: initiating i2c bus recovery i2c_davinci i2c_davinci.1: controller timed out i2c_davinci i2c_davinci.1: initiating i2c bus recovery but the hardware can in principle do it. Regards, Bastian. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: Touchscreen - MFD driver for TPS6507x family
Oh I did'nt loaded the right kernel, my fault... Well now it's not working at all, I got this error *QWSTslibMouseHandlerPrivate: ts_open() failed with error: 'No such file or directory' *and no more /dev/input/touchscreen0 detected by udev. Any clues? Regards, Nicolas On Wed, Jul 28, 2010 at 5:18 PM, Nicolas Luna luna...@gmail.com wrote: I changed MUX_CFG(DA850, I2C0_SDA, 4, 12, 15, 2, false) MUX_CFG(DA850, I2C0_SCL, 4, 8, 15, 2, false) to MUX_CFG(DA850, I2C0_SDA, 4, 12, 15, 8, false) MUX_CFG(DA850, I2C0_SCL, 4, 8, 15, 8, false) seems to have the same behaviour.. Nicolas On Wed, Jul 28, 2010 at 5:08 PM, Nicolas Luna luna...@gmail.com wrote: board-da850-evm.c Nicolas On Wed, Jul 28, 2010 at 4:51 PM, Todd Fischer todd.fisc...@ridgerun.comwrote: On Wed, 2010-07-28 at 16:46 -0400, Nicolas Luna wrote: Todd, What do I need to change if I want to use the bitbang i2c driver and stop to get those error messages. I added support for GPIO-based bitbaging I2C into the kernel, anything else to change in the TPS driver source code? You need to modify the arm/arch/mach-davinci board file to configure the pinmux as GPIOs, not I2C signaling. Which hardware board are you using? Thanks Regards, Nicolas On Wed, Jun 9, 2010 at 4:17 PM, Todd Fischer todd.fisc...@ridgerun.com wrote: HI Bastian and Nicolas, I recall getting this error when I wasn't using the bitbang i2c driver on the OMAP-L138. Todd On Wed, 2010-06-09 at 10:59 +0200, Bastian Ruppert wrote: Hello Nicolas, thanks for the .conf file. this will help you to check if your hardware is ok. It helped. I applied your file on the khilman commit you are using but i had to patch the kernel in order to compile drivers/mfd/tps6507x.c . I think if you don`t have the same problems, that is anomalous. After that the touchscreen driver is running on that kernel. It`s a little bit unstable, there are sometimes errors like tps6507x 1-0048: TSC mode read failed i2c_davinci i2c_davinci.1: controller timed out i2c_davinci i2c_davinci.1: initiating i2c bus recovery i2c_davinci i2c_davinci.1: controller timed out i2c_davinci i2c_davinci.1: initiating i2c bus recovery but the hardware can in principle do it. Regards, Bastian. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
[PATCH v5 0/1] davinci: spi: replace existing driver
Fixed in this version: - Addressed all comments from the previous version ** NOTE ** This patch requires the EDMA patch at: http://linux.davincidsp.com/pipermail/davinci-linux-open-source/2010-March/018022.html which is queued waiting on another driver fix, for DMA mode to work correctly. Brian Niebuhr (1): davinci: spi: replace existing driver arch/arm/mach-davinci/board-dm355-evm.c | 10 + arch/arm/mach-davinci/board-dm355-leopard.c | 10 + arch/arm/mach-davinci/board-dm365-evm.c | 10 + arch/arm/mach-davinci/dm355.c |8 +- arch/arm/mach-davinci/dm365.c |6 - arch/arm/mach-davinci/include/mach/spi.h| 35 +- drivers/spi/davinci_spi.c | 1098 --- 7 files changed, 521 insertions(+), 656 deletions(-) ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
[PATCH v5 1/1] davinci: spi: replace existing driver
INTRODUCTION
I have been working on a custom OMAP-L138 board that has multiple spi
devices (seven) on one controller. These devices have a wide range of
transfer parameters (speed, phase, polarity, internal and gpio chip
selects). During my testing I found multiple errors in the davinci spi
driver as a result of this complex setup. The primary issues were:
1. There is a race condition due to the SPIBUF read busy-waits for slow
devices
2. I found some DMA transfer length errors under some conditions
3. The chip select code caused extra byte transfers (with no chip
select active) due to writes to SPIDAT1
4. Several issues prevented using multiple SPI devices, especially
the DMA code, as disucussed previously on the davinci list.
The fixes to these problems were not simple. I ended up making fairly
large changes to the driver, and those changes are contained in these
patches. The full list of changes follows.
CHANGE LIST
1. davinci_spi_chipelect() now performs both activation and deactivation
of chip selects. This lets spi_bitbang fully control chip
select activation, as intended by the SPI API.
2. Chip select activation does not cause extra writes to the SPI bus
3. Chip select activation does not use SPIDEF for control. This change
will also allow for implementation of inverted (active high)
chip selects in the future.
4. Added back gpio chip select capability from the old driver
5. Fixed prescale calculation for non-integer fractions of spi clock
6. Allow specification of SPI transfer parameters on a per-device
(instead of per-controller) basis
7. Allow specification of polled, interrupt-based, or DMA operation on
a per-device basis
8. Allow DMA with when more than one device is connected
9. Combined pio and dma txrx_bufs functions into one since they share
large parts of their functionality, and to simplify item (8).
10. Use only SPIFMT0 to allow more than 4 devices
TESTING
I have tested the driver using a custom SPI stress test on my
OMAP-L138-based board with three devices connected. I have tested
configurations with all three devices polled, all three interrupt-based,
all three DMA, and a mixture.
I have compiled with the davinci_all_defconfig, but I don't have EVMs
for the other davinci platforms to test with.
Signed-off-by: Brian Niebuhr bnieb...@efjohnson.com
---
arch/arm/mach-davinci/board-dm355-evm.c | 10 +
arch/arm/mach-davinci/board-dm355-leopard.c | 10 +
arch/arm/mach-davinci/board-dm365-evm.c | 10 +
arch/arm/mach-davinci/dm355.c |8 +-
arch/arm/mach-davinci/dm365.c |6 -
arch/arm/mach-davinci/include/mach/spi.h| 35 +-
drivers/spi/davinci_spi.c | 1098 ---
7 files changed, 521 insertions(+), 656 deletions(-)
diff --git a/arch/arm/mach-davinci/board-dm355-evm.c
b/arch/arm/mach-davinci/board-dm355-evm.c
index a319101..ad8779b 100644
--- a/arch/arm/mach-davinci/board-dm355-evm.c
+++ b/arch/arm/mach-davinci/board-dm355-evm.c
@@ -32,6 +32,7 @@
#include mach/nand.h
#include mach/mmc.h
#include mach/usb.h
+#include mach/spi.h
/* NOTE: this is geared for the standard config, with a socketed
* 2 GByte Micron NAND (MT29F16G08FAA) using 128KB sectors. If you
@@ -300,10 +301,19 @@ static struct spi_eeprom at25640a = {
.flags = EE_ADDR2,
};
+static struct davinci_spi_config at25640a_spi_cfg = {
+ .parity_enable = false,
+ .intr_level = 0,
+ .io_type= SPI_IO_TYPE_DMA,
+ .wdelay = 0,
+ .timer_disable = true,
+};
+
static struct spi_board_info dm355_evm_spi_info[] __initconst = {
{
.modalias = at25,
.platform_data = at25640a,
+ .controller_data = at25640a_spi_cfg,
.max_speed_hz = 10 * 1000 * 1000, /* at 3v3 */
.bus_num= 0,
.chip_select= 0,
diff --git a/arch/arm/mach-davinci/board-dm355-leopard.c
b/arch/arm/mach-davinci/board-dm355-leopard.c
index f1d8132..b2d8d48 100644
--- a/arch/arm/mach-davinci/board-dm355-leopard.c
+++ b/arch/arm/mach-davinci/board-dm355-leopard.c
@@ -29,6 +29,7 @@
#include mach/nand.h
#include mach/mmc.h
#include mach/usb.h
+#include mach/spi.h
/* NOTE: this is geared for the standard config, with a socketed
* 2 GByte Micron NAND (MT29F16G08FAA) using 128KB sectors. If you
@@ -222,10 +223,19 @@ static struct spi_eeprom at25640a = {
.flags = EE_ADDR2,
};
+static struct davinci_spi_config at25640a_spi_cfg = {
+ .parity_enable = false,
+ .intr_level = 0,
+ .io_type= SPI_IO_TYPE_DMA,
+ .wdelay = 0,
+ .timer_disable = true,
+};
+
static struct spi_board_info dm355_leopard_spi_info[] __initconst = {
{
.modalias = at25,
.platform_data = at25640a,
+
Re: Touchscreen - MFD driver for TPS6507x family
Try i2c-tools i2cdetect and see if any chips are showing up on the bus. On Wed, 2010-07-28 at 17:44 -0400, Nicolas Luna wrote: Oh I did'nt loaded the right kernel, my fault... Well now it's not working at all, I got this error QWSTslibMouseHandlerPrivate: ts_open() failed with error: 'No such file or directory' and no more /dev/input/touchscreen0 detected by udev. Any clues? Regards, Nicolas On Wed, Jul 28, 2010 at 5:18 PM, Nicolas Luna luna...@gmail.com wrote: I changed MUX_CFG(DA850, I2C0_SDA, 4, 12, 15, 2, false) MUX_CFG(DA850, I2C0_SCL, 4, 8, 15, 2, false) to MUX_CFG(DA850, I2C0_SDA, 4, 12, 15, 8, false) MUX_CFG(DA850, I2C0_SCL, 4, 8, 15, 8, false) seems to have the same behaviour.. Nicolas On Wed, Jul 28, 2010 at 5:08 PM, Nicolas Luna luna...@gmail.com wrote: board-da850-evm.c Nicolas On Wed, Jul 28, 2010 at 4:51 PM, Todd Fischer todd.fisc...@ridgerun.com wrote: On Wed, 2010-07-28 at 16:46 -0400, Nicolas Luna wrote: Todd, What do I need to change if I want to use the bitbang i2c driver and stop to get those error messages. I added support for GPIO-based bitbaging I2C into the kernel, anything else to change in the TPS driver source code? You need to modify the arm/arch/mach-davinci board file to configure the pinmux as GPIOs, not I2C signaling. Which hardware board are you using? Thanks Regards, Nicolas On Wed, Jun 9, 2010 at 4:17 PM, Todd Fischer todd.fisc...@ridgerun.com wrote: HI Bastian and Nicolas, I recall getting this error when I wasn't using the bitbang i2c driver on the OMAP-L138. Todd On Wed, 2010-06-09 at 10:59 +0200, Bastian Ruppert wrote: Hello Nicolas, thanks for the .conf file. this will help you to check if your hardware is ok. It helped. I applied your file on the khilman commit you are using but i had to patch the kernel in order to compile drivers/mfd/tps6507x.c . I think if you don`t have the same problems, that is anomalous. After that the touchscreen driver is running on that kernel. It`s a little bit unstable, there are sometimes errors like
RE: Touchscreen - MFD driver for TPS6507x family
Hi Nicolas, On Thu, Jul 29, 2010 at 02:16:16, Nicolas Luna wrote: Todd, What do I need to change if I want to use the bitbang i2c driver and stop to get those error messages. You can try the patch here: http://arago-project.org/git/projects/?p=linux-omapl1.git;a=commit;h=7d8accda275fdbe6e727e7ac02ae5a92f5695326 This issue should be fixed in future revisions of Logic EVMs so this patch wont be needed afterward. Thanks, Sekhar ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
