Following are two patches:
- Define and use platform_data for davinci_mmc, supporting
the usual board-specific hooks for sensing card presence,
the writeprotect switch, and saying if the slot is wired
to support SD vs just MMC (or potentially 1-wire SDIO).
- Use that in dm6446 EVM ...
From: David Brownell <[EMAIL PROTECTED]>
Inital support for new MMC init logic, where boards can say how
to initialize what, and also provide functions to sense card
detect and writeprotect switches. This also removes some
static driver configuration forcing it to always use 4-bit
parallel data c
From: David Brownell <[EMAIL PROTECTED]>
Update DM6466 EVM to support the new MMC board config data.
This provides a miniature I2C driver in the board-dm644x-evm.c
file ... unusual, but it does make it easier to pass the key
information easily to the MMC driver.
There's no attempt to use the gpi
Hi,
When you said that the flash isn't really booting u-boot what do you see. I've
tried to boot with an erased Flash and the DS22 LED was blinking slowly (DS22
is the GPIO16, see the ARM subsystem reference guide : SPRUFB3 document)
I don't remember having given an address for the UBL. For u-boo
Hi All,
I am new to the DM355 & Davinci-linux development.
We have a custom DM355 based board which is similar to DM355EVM board.
The board have DM9000 ethernet chip on EMIF .
I want to implment DMA for DM9000's transmit/receive oparation,
DM355 has EDMA provisions for various peripherals
Troy,
> -Original Message-
> From: Troy Kisky [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, December 10, 2008 3:27 AM
> To: Rajashekhara, Sudhakar
> Cc: davinci-linux-open-source@linux.davincidsp.com
> Subject: Re: [PATCH 11/14] ARM: DaVinci: dma: clear link on stop
>
> Rajashekhara, Sudha
Hi. I am a user of DM6467 EVM.
When booting the board, I make the board mount the nfs system in one Linux host
PC. Sometimes it succeeds, but sometimes it fails. The error msg is like this:
mount: server not responding, timed out
Root-NFS: Server returned error -5 while mounting /home
Generalizes dm644x pinmux.
The existing pinmux layer works only when the PINMUX register has single bit
field to enable the secondary function. DM646x can support secondary as well
as tertiary pin functions. This new pinmux layer is similar to the one being
used by OMAP architecture.
Checkpatch s
Hi,
I am having a similar problem. Do you have any example of how to modify the
driver to be mutually exclusive of each other in-flight.
Tnx,
Benjamin
--- On Wed, 12/10/08, Subbrathnam, Swaminathan <[EMAIL PROTECTED]> wrote:
From: Subbrathnam, Swaminathan <[EMAIL PROTECTED]>
Subject: RE: sav
Hi All,
I am new to the DM355 & Davinci-linux development.
We have a custom DM355 based board which is similar to DM355EVM board.
The board have DM9000 ethernet chip on EMIF .
I want to implment DMA for DM9000's transmit/receive oparation,
DM355 has EDMA provisions for various peripherals
Hi,
Has anyone experienced this situation: boot from flash and recording some data
to CF card?
I'm using DaVinci 6446 customized board. I boot the device from NOR flash. When
I avoid communication with CF card (no data streaming to CF), the application
works perfectly fine. But, when I set 17t
Valentina,
NOR flash is pin muxed with CF as far as I know on DaVinci. If you
file system is located on NOR and you need to access NOR and CF from Linux then
you need to modify the drivers to be mutually exclusive of each others
in-flight and outstanding access.
Regards
Swami
PSP d
Hi,
Check the NFS server log file (/var/log/messages) to find out what is
going on. This should have an entry each time the mount request is seen
by the server - it should say something like 'Authenticated mount
request for.'. If it fails to authenticate it should give a reason..
Failing
I've been developing a motion jpeg demo, on the DVEVM 6446, that takes
video from the composite source and converts it into mjpeg frames that
are output over the Ethernet port. After much struggling I've got this
working to my satisfaction and everything is great.
But I would like to switch fr
Hi,
I have DVEVM dm6446 davinci board.
And I try to work stand alone with the NOR Flash.
Dose anybody knows or has neither experience with NOR flash?
Please, if anybody can help me how can I load the KERNEL and the FILE SYSTEM
to the NOR flash.
I read something about JFFS2 but I didn't find
Hello All,
We are currently working in the DM355 Davinci processor based customized
board. We have five I2C slave devices in the board. Out of the five
slave devices, one device needs the pixel cloclk/VCLK output from the
Davinci processor.
In order to generate the VCLK, we have to enable
There are two pieces to this issue:
1) The transfer between memory and the DM9000. This should be no problem
as the DM9000 will show up in the EMIF address space.
2) The initiation of the transfer. You either need to manually invoke
the transfer (through the ESR) or an event can st
It looks like your problems started here:
asm/arch/param.h: No such file or directory
The "asm" directory is normally a softlink (e.g. to arm-asm) and it gets
created during the "make dm6446_defconfig" step (that might not be the exact
syntax though hopefully you get what I'm saying). If you e
On Tue, Dec 09, 2008 at 05:29:49PM -0800, David Brownell wrote:
> On Tuesday 09 December 2008, Felipe Balbi wrote:
> > +struct davinci_nand_info {
> > + /* device lock */
> > + spinlock_t lock;
> > + struct nand_chipchip;
> > + struct mtd_info mt
On Tue, Dec 09, 2008 at 11:55:51PM -0800, David Brownell wrote:
> So what I'm suggesting is to build on these two patches
> (and a third for dm355 evm) and ... rip out ALL the
> current card detect logic in davinci_mmc, and rely on
> the MMC_CAP_NEEDS_POLL support in the MMC core.
do we really nee
On Wed, Dec 10, 2008 at 03:35:28PM +0530, Sudhakar Rajashekhara wrote:
> Generalizes dm644x pinmux.
>
> The existing pinmux layer works only when the PINMUX register has single bit
> field to enable the secondary function. DM646x can support secondary as well
> as tertiary pin functions. This new
On Wednesday 10 December 2008, Felipe Balbi wrote:
> On Tue, Dec 09, 2008 at 05:29:49PM -0800, David Brownell wrote:
> > On Tuesday 09 December 2008, Felipe Balbi wrote:
> > > +struct davinci_nand_info {
> > > + /* device lock */
> > > + spinlock_t lock;
> > > + struc
On Wednesday 10 December 2008, Felipe Balbi wrote:
> On Tue, Dec 09, 2008 at 11:55:51PM -0800, David Brownell wrote:
> > So what I'm suggesting is to build on these two patches
> > (and a third for dm355 evm) and ... rip out ALL the
> > current card detect logic in davinci_mmc, and rely on
> > the
Hi,
If you don't want the hassle of version controlling loads of files you
have no interest in then may I suggest you use the 'quilt' package to
manage your patches to the kernel. The package is available for
RedHat/Fedora/CentOS and probably *buntu as well.
With this your workflow becomes
Felipe,
One comment on the NAND resources below -
Thanks
Sneha
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Felipe Balbi
> Sent: Tuesday, December 09, 2008 6:42 PM
> To: davinci-linux-open-source@linux.davincidsp.com
> Cc: Felipe Balbi
> Subje
Hi,
On Wed, Dec 10, 2008 at 12:52:14PM -0600, Narnakaje, Snehaprabha wrote:
> > +static struct resource davinci_nand_resources[] = {
> > + {
> > + .start = DAVINCI_ASYNC_EMIF_DATA_CE0_BASE,
> > + .end= DAVINCI_ASYNC_EMIF_DATA_CE0_BASE + SZ_32M - 1,
> > +
I'm running into a very strange problems with serial output on the
console affecting my LCD output. The problem can be replicated by
pushing an image to osd0 (cat myimage > /dev/fb/0) and then just holding
down the enter key to scroll the console. The display flickers and the
image shifts as
I'll disagree with a few of Felipe's points here, and offer
a few other comments.
On Wednesday 10 December 2008, Felipe Balbi wrote:
> On Wed, Dec 10, 2008 at 03:35:28PM +0530, Sudhakar Rajashekhara wrote:
> > Generalizes dm644x pinmux.
> >
> > The existing pinmux layer works only when the PINMU
David Brownell <[EMAIL PROTECTED]> writes:
> I'm curious whether someone is working on the dm355 and evm
> support for two a/v codecs in (or soon to be in) mainline:
>
> - sound/soc/codecs/tlv320aic3x.c ... this is the audio
>codec on the board, but sound/soc/davinci seems to not
>have su
On Wednesday 10 December 2008, Felipe Balbi wrote:
>
> > The NAND device that comes with the DM355 EVM requires another
> > resource here for the second NAND chip select, to be able to
> > use the 2GB space. Has this configuration been tested on the EVM?
>
> As I understood from the documentati
On Wednesday 10 December 2008, Sudhakar Rajashekhara wrote:
> Generalizes dm644x pinmux.
One more thought. DM355 has for example INTMUX, choosing which
peripheral's interrupt gets to be reported; and EVTMUX, choosing
which peripheral gets a particular DMA channel. (ASP0 vs ASP1,
for either RX or
On Wednesday 10 December 2008, David Brownell wrote:
> p.s. Preview of the third patch appended; builds, not tested.
And would you believe ... that, plus some debug hacks, got
an SD card enumerated with mmc1 on a DM355 EVM?? AFAICT,
letting the MMC core see that a card was there at startup
time s
On Wednesday 10 December 2008, Kevin Hilman wrote:
> > - drivers/media/video/tvp514x.c ... this is the video
> >input decoder, taking S-Video or composite. Very new,
> >not yet in linux-next; V5 patch posted Friday. I'm
> >guessing this needs similar DM355-specific support:
> >VP
Rajashekhara, Sudhakar wrote:
> # aplay test
> Playing WAVE 'test' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
> aplay: pcm_write:1264: write error: Input/output error
> #
>
> As you know your RFC patch is also not working. I made the change which you
> had suggested in tlvaic3x.c file b
David,
Initial version of capture drivers (VPFE, CCDC and TVP) was submitted to this
mailing list.
http://linux.omap.com/pipermail/davinci-linux-open-source/2008-November/009227.html
This version of capture driver used v3 or v4 of TVP patches from v4l2 mailing
list.
http://linux.omap.com/pipe
Hi,
You do not have a dedicated EDMA channel for DM9000-EMIF. But you can always
use an unallocated DMA channel for Transmit and Receive.
EDMA will be used to transfer the data to/from DDR from/to DM9000 FIFO.
We had tried to change the current DM9000 driver to use EDMA on the transmit
path. W
David Brownell <[EMAIL PROTECTED]> writes:
> While trying to puzzle out some of those ASoc questions, I noticed
> some cleanups that seemed needed. So here are some patches ...
>
> First, the cleanups:
>
> - Remove a remnant of an ancient/obsolete OSS-for-DaVinci patch.
>(Part of this -- a h
Felipe,
Another minor comment below, in addition to Dave's comments:
Felipe Balbi <[EMAIL PROTECTED]> writes:
> From: Felipe Balbi <[EMAIL PROTECTED]>
>
> Introduce a structure to hold device data. Already
> changes read/write functions to use __raw_read/write.
>
> Signed-off-by: Felipe Balbi <[
David Brownell <[EMAIL PROTECTED]> writes:
> On Tuesday 09 December 2008, Felipe Balbi wrote:
>> Felipe Balbi (6):
>> arch: davinci: pass emif control base via resource
>> mtd: nand: davinci: checkpatch.pl fixes
>> mtd: nand: davinci: don't cast unnecessarily
>> mtd: nand: davinci: introdu
On Wednesday 10 December 2008, Kevin Hilman wrote:
> I'm going to merge this whole series as I agree that the last two are
> definitely the right direction to take.
OK, don't forget that little one-liner I posted (updating #5 ISTR)
switching a ptr->val[pdev->id]->OOPS! into ptr->val->OK ... ;)
-
Sneha,
On Wednesday 10 December 2008, Narnakaje, Snehaprabha wrote:
> David,
>
> Initial version of capture drivers (VPFE, CCDC and TVP) was submitted to this
> mailing list.
> http://linux.omap.com/pipermail/davinci-linux-open-source/2008-November/009227.html
>
> This version of capture drive
[EMAIL PROTECTED] writes:
> From: Chaithrika U S <[EMAIL PROTECTED]>
>
> Adds LSI ET1011C PHY driver.
> This driver is used by TI DM646x EVM.
>
> Signed-off-by: Chaithrika U S <[EMAIL PROTECTED]>
Chaithrika,
I saw that David Miller applied this. Nice work!
I will also commit to linux-davinci u
On Wednesday 10 December 2008, David Brownell wrote:
> And would you believe ... that, plus some debug hacks, got
> an SD card enumerated with mmc1 on a DM355 EVM?? AFAICT,
> letting the MMC core see that a card was there at startup
> time seems to have been the kicker. Yay!
Or maybe not. One o
David Brownell <[EMAIL PROTECTED]> writes:
> On Wednesday 10 December 2008, Kevin Hilman wrote:
>> I'm going to merge this whole series as I agree that the last two are
>> definitely the right direction to take.
>
> OK, don't forget that little one-liner I posted (updating #5 ISTR)
> switching a p
David Brownell <[EMAIL PROTECTED]> writes:
> In my thus-far-futile quest to get dm355 booting out of
> the GIT tree and not running out of initramfs ... here
> are some MMC updates.
>
> - Clock framework updates, so that clk_get(dev, "mmc")
>can return the MMC clock used by that device withou
David Brownell <[EMAIL PROTECTED]> writes:
> From: David Brownell <[EMAIL PROTECTED]>
>
> Sure would be nice to have the watchdog device node created, so
> the watchdog driver (already in mainline) binds to something.
>
> Signed-off-by: David Brownell <[EMAIL PROTECTED]>
> ---
> Hmmm ... doesn't a
Hi All:
I find when write to SD card on Davinci, mmcqd eats 70% of the cpu!!,
which cause audio and other tasks don't work well.
My configuration is below
- DVEVM6446 from Spectrum Digital
- linux-2.6.10_mvl401.patch47 from Montavista
- Various SD card
- 4bit bus width, DMA enabled, default m
This is a testing patch that still needs
broken into smaller chunks. It is compile
tested for the davinci_evm_dm644x_defconfig
only. I expect that the patch will reduce
pops and eliminate underrun audio issues
on the evm. The previously sent
dma patch set needs applied before this.
Specificly, davi
>
> mmci irq arrived with BSYDNE set, but DATDNE,TRNDNE not set
>
Sorry, should be "mmci irq arrived with BSYDNE set, but RSPDNE not set".
Regards
Eddy
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://lin
On Wednesday 10 December 2008, Eddy Zhao wrote:
> So, I have several questions:
I think it's fairly evident that the current davinci_mmc.c driver
has some issues to resolve yet. :(
That seems to apply both to MontaVista's 2.6.10 code and to the
current GIT version. Do you know if these problems
On Monday 08 December 2008, David Brownell wrote:
> From: David Brownell <[EMAIL PROTECTED]>
>
> Remove remnants of an old OSS-audio-for-DaVinci patch, which
> tried to make some OMAP-specific AIC23 code do double duty as
> DaVinci AIC33 codec support.
>
> Nowadays there's sane ASoC support for b
Thanks a lot for your info !
Btw to request unallocated DMA channel is it the right thing am doing in
the following segment?
int dm9000_dma_tx_ch;
int err, tcc;
err = davinci_request_dma(DAVINCI_DMA_CHANNEL_ANY, "DM9000
Tx", dm9000_dma_tx_callback, dev, &dm9000_dma_tx_ch,
&tcc,
I have a question for the Input folk, see below ...
On Sunday 07 December 2008, David Brownell wrote:
> From: David Brownell <[EMAIL PROTECTED]>
>
> Simple input driver support for the events reported by the
> MSP430 firmware on the DM355 EVM. Verified using the remote
> included with the kit; d
I see you merged these too ... good.
On Sunday 07 December 2008, David Brownell wrote:
> Following this are several patches that IMO make a useful
> leap in functionality for the dm355 and its EVM:
>
> - GPIO bugfixes. The other chips probably didn't care,
>but for dm355 correctly written
On Wednesday 10 December 2008, Kevin Hilman wrote:
> I'm going to merge this whole series as I agree that the last two are
> definitely the right direction to take.
Great. Seems like some ASoC bits can't go to mainline until
a bunch of arch/arm/mach-davinci updates precede them ... let
me know if
From: David Brownell <[EMAIL PROTECTED]>
Minor cleanups to davinci-mmc: whitespace, spelling, sparse fixes,
duplicated include files, broken debug message, ioremap exactly
the address space we reserved, cleaner IS_ERR check, etc.
Signed-off-by: David Brownell <[EMAIL PROTECTED]>
---
drivers/mmc/
From: David Brownell <[EMAIL PROTECTED]>
Remove a header inclusion that was accidentaly
left over from debugging.
Signed-off-by: David Brownell <[EMAIL PROTECTED]>
---
drivers/input/keyboard/dm355evm_keys.c |2 --
1 file changed, 2 deletions(-)
--- a/drivers/input/keyboard/dm355evm_keys.c
From: David Brownell <[EMAIL PROTECTED]>
Support card detect and writeprotect switches on DM355 EVM.
Signed-off-by: David Brownell <[EMAIL PROTECTED]>
---
Against current DaVinci GIT. MMC0 doesn't seem to talk to
me, but MMC1 at least detects the card ... before it wedges
trying to read the part
David Brownell <[EMAIL PROTECTED]> writes:
> On Monday 08 December 2008, David Brownell wrote:
>> From: David Brownell <[EMAIL PROTECTED]>
>>
>> Remove remnants of an old OSS-audio-for-DaVinci patch, which
>> tried to make some OMAP-specific AIC23 code do double duty as
>> DaVinci AIC33 codec sup
From: David Brownell <[EMAIL PROTECTED]>
Support card detect and writeprotect switches on DM355 EVM.
Signed-off-by: David Brownell <[EMAIL PROTECTED]>
---
Grr, this is the bugfixed version ... forgot to add the right
base to the gpio range passed from dm355evm_msp.
And news on the "MMC1 partiall
60 matches
Mail list logo