On Mon, Jun 22, 2009 at 04:14:15PM -0400, Ryan Talbot wrote:
Since the VIDIOC_DQBUF ioctl gives me an error whren I try to
pass buffers to he driver, I just would like to know if
USERPTR is supported for video capture by MVL5.0 kernel or not.
Which error is DQBUF giving you? Did you
zuowenping,
You need to modify the arch/arm/mach-davinci/davinci_spi_platform.c
struct spi_board_info dm6467_spi_board_info[], .modalias =
DAVINCI_SPI_EEPROM_NAME, to .modalias = spidev. Also you must enable
CONFIG_SPI_SPIDEV. After that the kernel will detect the device as
spidev0 and
On Mon, Jun 22, 2009 at 13:16:55, Young, Joseph wrote:
I am porting the Davinci Linux kernel to a new and similar TI device,
called Jacinto2. I am at the point where the init program passed to
the kernel by the bootloader is initialized. The problem that I am
experiencing is that,
thanks Philby very much!
I have done according to your words,I cann't see the device node in /dev
yet,and i mknod and create node /dev/spidev0, and now i can run my
spidev_test.c,
# insmod spidev.ko
# mknod /dev/spi0 c 153 0
# ./spi_test
# spi mode: 3
bits peBUG: scheduling while atomic:
hi, all
my davsdk based on linux-2.6.10, in order to make my EVM to
support sdhc card, I down load SDIO stack patches from sf which is open
source project. I apply them into kernel successfully. but it can't
works . when I try to insmod sdio_davinci_hcd.ko, it occurs errors as below:
I have add some code for spi_board_info just as:
spi_board_info dm355_spi_board_info[] ={
//add by duke 2009.6.18
{
.modalias = spidev,
.platform_data = NULL,//davinci_8k_spi_eeprom_info,
.mode = SPI_MODE_0,
.irq = 0,
.max_speed_hz = 2
This patch adds support for MMC/SD controller driver for DaVinci family SoC.
This patch will work for SoC like DM6446 and DM355. SoC like DM365 and
DA830 also has same controller with small variations and could supported/added
easily by using this version of patch. It means that this version of
On Tue, 2009-06-23 at 16:14 +0800, zuowenping wrote:
thanks Philby very much!
I have done according to your words,I cann't see the device node
in /dev yet,and i mknod and create node /dev/spidev0, and now i can
run my spidev_test.c,
# insmod spidev.ko
# mknod /dev/spi0 c 153 0
#
The description of this patch needs to be updated. I'll repost the patch
soon.
Thanks and regards,
~Vipin
-Original Message-
From: Vipin Bhandari [mailto:vipin.bhand...@ti.com]
Sent: Tuesday, June 23, 2009 2:25 PM
To: linux-ker...@vger.kernel.org
Cc:
This patch adds support for MMC/SD controller driver for all DaVinci family
SoC. This patch supports davinci family SoC's DM6446, DM355, DM365 and
DA830/OMAPL137.
The patch has been tested on DM355 EVM.
The MMCSD controller specifications for DM355 can be found at
HI
I am now porting a small application from LSP1.30 to LSP 2.10. It seems that
VPFE driver have changed. I need to initialize sensore board from
leopardimaging with MT9P031 on boar. It seems that there is no connection to
MT9P031 driver.
Do you have some hints, or may be have you tried it..
. It seems that there is no connection to MT9P031 driver.
What you mean by this?
Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Germantown, MD 20874
Phone : 301-515-3736
email: m-kariche...@ti.com
From:
That onl feeling, because there are IOCTLs for setting MT9T001 params but
none with MT9P031.
Second I am not able open video0. It ends with something like this
i2c_adapter i2c-0: tvp514x_setinput:lost lock]
i2c_adapter i2c-0: tvp514x_setinput:lost lock]
i2c_adapter i2c-0: tvp514x: no input
Vipin Bhandari vipin.bhand...@ti.com writes:
This patch adds support for MMC/SD controller driver for all DaVinci family
SoC. This patch supports davinci family SoC's DM6446, DM355, DM365 and
DA830/OMAPL137.
The patch has been tested on DM355 EVM.
The MMCSD controller specifications for
[CC list trimmed]
Vipin Bhandari vipin.bhand...@ti.com writes:
This patch adds support for MMC/SD controller driver for all DaVinci family
SoC. This patch supports davinci family SoC's DM6446, DM355, DM365 and
DA830/OMAPL137.
The patch has been tested on DM355 EVM.
The MMCSD controller
Brian Rhodes wrote:
MV Pro 5.0 toolchain
Codec Engine 2.23.01
DSP/BIOS 5.33.05
XDCTOOLS 3.15.00.50
Framework Components 2.23.01
XDAIS 6.23
DSPLINK 1.61.03
CMEM (linuxutils) 2.23.01
The error message @0,123,595us: [+7 T:0x44643490 S:0x44642d74] OP -
Processor_create_d Loading and starting DSP
Hello,
Now that davinci git is close to upstream, most of the patches coming
through davinci git will go directly upstream when ready.
Until now, I've been manually editing subjects to have some
consistency, but I'd like some help here.
From now on, I'd like to see any patches touching
s-paul...@ti.com writes:
From: Sandeep Paulraj s-paul...@ti.com
Patch updates the Kconfig for ARM DaVinci.
The ARCH_DAVINCI_DMx flasg is selected for DM365
Signed-off-by: Sandeep Paulraj s-paul...@ti.com
Thanks, pushing today.
Kevin
---
arch/arm/mach-davinci/Kconfig |1 +
1 files
s-paul...@ti.com writes:
From: Sandeep Paulraj s-paul...@ti.com
Patch adds interrupt mux entries for EDMA, RTC
and EMAC. Also we add a pin mux entry for keypad
Signed-off-by: Sandeep Paulraj s-paul...@ti.com
Thanks, pushing today.
Kevin
---
arch/arm/mach-davinci/dm365.c|
s-paul...@ti.com writes:
From: Sandeep Paulraj s-paul...@ti.com
The patch adds Support for EMAC in the DM365 SOC
Signed-off-by: Sandeep Paulraj s-paul...@ti.com
Thanks, pushing today.
Kevin
---
arch/arm/mach-davinci/dm365.c | 58
+
1 files
s-paul...@ti.com writes:
From: Sandeep Paulraj s-paul...@ti.com
Patch adds support for the DM365 EVM.
It also configures the PINMUX and INTMUX for EMAC.
Signed-off-by: Sandeep Paulraj s-paul...@ti.com
Thanks, pushing today after folding this nto the SoC support.
Kevin
---
s-paul...@ti.com writes:
From: Sandeep Paulraj s-paul...@ti.com
Patch adds MMC/SD Support for DM365
Signed-off-by: Sandeep Paulraj s-paul...@ti.com
Thanks, pushing today.
Kevin
---
arch/arm/mach-davinci/devices.c | 45 ++
1 files changed, 31
s-paul...@ti.com writes:
From: Sandeep Paulraj s-paul...@ti.com
Patch adds support for MMC/SD in the DM365 EVM.
Pinmux for MMC/SD slot 1 on the DM365 EVM is also
configured.
Signed-off-by: Sandeep Paulraj s-paul...@ti.com
Pushing today, even though it sounds like there may still be some
s-paul...@ti.com writes:
From: Sandeep Paulraj s-paul...@ti.com
The Patch adds support for the NAND driver
in the DM365 EVM
Signed-off-by: Sandeep Paulraj s-paul...@ti.com
Thanks, pushing today.
Kevin
---
arch/arm/mach-davinci/board-dm365-evm.c | 84
+++
David Brownell davi...@pacbell.net writes:
From: David Brownell dbrown...@users.sourceforge.net
Add basic support for the CPLD on the DM365 EVM board:
- Read SW5 to set up NAND and keypad vs (someday) OneNAND
- Export MMC/SD card detect and writeprotect signals
- LED support (same
Rajashekhara, Sudhakar sudhakar@ti.com writes:
This series prepares the DaVinci git tree for TI da850/omapl138
support. This series is dependent on the following patch which I
have submitted earlier.
[PATCH] ARM: DaVinci: Pass proper EDMA platform data information
Thanks. Will push
Dave, Kevin,
Regarding support for EDMA on DM365, looks like I need to add a single line of
code in dm365.c
davinci_cfg_reg(DM365_INT_EDMA_CC);
I'll add it just before the EDMA device is registered. Let me now if this is OK.
I'll send the patch tomorrow because dm365 files will change.
Hey folks,
I'm having some mysterious behavior occur when shutting down my
application. It seems to be tied with shutting down CodecEngine 2.21,
and we did not have this problem when using CodecEngine 1.10.
We have a modular, multi-platform application that collects video, among
other
If possible, I'd recommend removing the osalGlobal.armDspLinkConfig assignment
in your app.cfg script. You should be able to use the default memory map
initialized by Engine.createFromServer():
http://tiexpressdsp.com/index.php/Configuring_Codec_Engine_in_Arm_apps_with_createFromServer
Chris
Hello EveryBody!
Now I encountered a very strange problem on DM355 EVM.I use DM355 to
capture 2592x1944 resolution picture from the MT9P031 Sensor,but sometimes I
can only get a disrupt image,and In the capture thread,I find the DQBUF time
only need 1ms in the most time(If I do not use
Chris,
I found that my map is proper, and the issue is elsewhere. It looks
like the LINKCFG_Dsp structure. The av5T ipc_dsplink library which is
being linked with the application seems to have some duplicate symbols.
I modified the LINKCFG_Dsp in dsplink to change the name and found that
This patch takes out IO mapping macros from mach/io.h and puts them in
mach/hardware.h avoiding need to include mach/io.h in various files such as
serial.h, vmalloc.h etc.
The main reason to avoid inclusion of mach/io.h is, when default in/out macros
are overridden by machine specific functions
32 matches
Mail list logo
