Hello,
I'm trying to get DeepSleep working on the DM365 with Linux Kernel
2.6.34 and I'm stuck. I'm using an Olimex JTAG debugger and I can step
through sleep.S to the point where it turns off PLL1, at which point I
seem to loose connection. It seems that maybe I don't have all the
interr
From: Lad, Prabhakar
This patch enables fbdev driver by creating fbdev device and register it.
Alongside renames 'vpfe_capture_dma_mask' to 'dm355_video_dma_mask' for better
clarity since it was reused by capture and diplay aswell.
Signed-off-by: Lad, Prabhakar
---
arch/ar
ndencies.
>
> Acked-by: Sekhar Nori
>
Thanks for the ACK, Yes I have tested the patch. missed to add the tested info.
And yes this patch will go via media tree.
Regards,
--Prabhakar
> Thanks,
> Sekhar
>
>> ---
>> Note:- This patch is on top of following pull
>
patchwork.linuxtv.org/patch/17888/
>
> arch/arm/mach-davinci/board-dm355-evm.c |4 ++--
> arch/arm/mach-davinci/board-dm365-evm.c |4 ++--
> arch/arm/mach-davinci/board-dm644x-evm.c |4 ++--
> 3 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/arch
://patchwork.linuxtv.org/patch/17888/
arch/arm/mach-davinci/board-dm355-evm.c |4 ++--
arch/arm/mach-davinci/board-dm365-evm.c |4 ++--
arch/arm/mach-davinci/board-dm644x-evm.c |4 ++--
3 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/arch/arm/mach-davinci/board-dm355-evm.c
b/arch/arm/mach
On 4/8/2013 2:56 PM, Prabhakar lad wrote:
> From: Lad, Prabhakar
>
> Create platform devices for various video modules like venc,osd,
> vpbe and v4l2 driver for dm355.
>
> Signed-off-by: Lad, Prabhakar
For patches 1/2 and 2/2:
Acked-by: Sekhar Nor
gt;>> Sekhar Nori escreveu:
>>>
>>>> On 4/8/2013 2:56 PM, Prabhakar lad wrote:
>>>>> From: Lad, Prabhakar
>>>>>
>>>>> This patch series enables VPBE display driver on DM355.
>>>>
>>>> These (this and th
Prabhakar lad wrote:
> >>> From: Lad, Prabhakar
> >>>
> >>> This patch series enables VPBE display driver on DM355.
> >>
> >> These (this and the DM365 one) patches look good to me. I need to get an
> >> immutable branch from Mauro where dep
Hi Maruo,
On 4/8/2013 4:26 PM, Mauro Carvalho Chehab wrote:
> Hi Sekhar,
>
> Em Mon, 8 Apr 2013 16:06:24 +0530
> Sekhar Nori escreveu:
>
>> On 4/8/2013 2:56 PM, Prabhakar lad wrote:
>>> From: Lad, Prabhakar
>>>
>>> This patch series enables VPB
Hi Sekhar,
Em Mon, 8 Apr 2013 16:06:24 +0530
Sekhar Nori escreveu:
> On 4/8/2013 2:56 PM, Prabhakar lad wrote:
> > From: Lad, Prabhakar
> >
> > This patch series enables VPBE display driver on DM355.
>
> These (this and the DM365 one) patches look good to me. I
On 4/8/2013 2:56 PM, Prabhakar lad wrote:
> From: Lad, Prabhakar
>
> This patch series enables VPBE display driver on DM355.
These (this and the DM365 one) patches look good to me. I need to get an
immutable branch from Mauro where dependencies are queued and then I can
generate a pul
From: Lad, Prabhakar
add support for V4L2 video display to DM355 EVM.
Support for SD modes is provided, along with Composite
output
Signed-off-by: Lad, Prabhakar
Acked-by: Sekhar Nori
---
arch/arm/mach-davinci/board-dm355-evm.c | 69 ++-
1 files changed, 68
From: Lad, Prabhakar
Create platform devices for various video modules like venc,osd,
vpbe and v4l2 driver for dm355.
Signed-off-by: Lad, Prabhakar
---
arch/arm/mach-davinci/board-dm355-evm.c |4 +-
arch/arm/mach-davinci/davinci.h |3 +-
arch/arm/mach-davinci/dm355.c
From: Lad, Prabhakar
This patch series enables VPBE display driver on DM355.
This patch series is dependent on VPSS clock cleanup patches
(http://www.mail-archive.com/davinci-linux-open-source@linux.davincidsp.com/msg25613.html)
posted.
Changes for v8:
1: Removed extra line after break'
On 4/2/2013 6:45 PM, Prabhakar lad wrote:
> From: Lad, Prabhakar
>
> add support for V4L2 video display to DM355 EVM.
> Support for SD modes is provided, along with Composite
> output
>
> Signed-off-by: Lad, Prabhakar
Looks good. Since you mentioned that you will take th
On 4/2/2013 6:45 PM, Prabhakar lad wrote:
> From: Lad, Prabhakar
>
> Create platform devices for various video modules like venc,osd,
> vpbe and v4l2 driver for dm355.
>
> Signed-off-by: Lad, Prabhakar
> ---
> arch/arm/mach-davinci/board-dm355-evm.c |4 +-
From: Lad, Prabhakar
add support for V4L2 video display to DM355 EVM.
Support for SD modes is provided, along with Composite
output
Signed-off-by: Lad, Prabhakar
---
arch/arm/mach-davinci/board-dm355-evm.c | 69 ++-
1 files changed, 68 insertions(+), 1 deletions
From: Lad, Prabhakar
Create platform devices for various video modules like venc,osd,
vpbe and v4l2 driver for dm355.
Signed-off-by: Lad, Prabhakar
---
arch/arm/mach-davinci/board-dm355-evm.c |4 +-
arch/arm/mach-davinci/davinci.h |3 +-
arch/arm/mach-davinci/dm355.c
From: Lad, Prabhakar
This patch series enables VPBE display driver on DM355.
This patch series is dependent on VPSS clock cleanup patches
(http://www.mail-archive.com/davinci-linux-open-source@linux.davincidsp.com/msg25613.html)
posted.
Changes for v7:
1: Fixed nits pointed by Sekhar for DM365
From: Lad, Prabhakar
Create platform devices for various video modules like venc,osd,
vpbe and v4l2 driver for dm355.
Signed-off-by: Lad, Prabhakar
---
arch/arm/mach-davinci/board-dm355-evm.c |4 +-
arch/arm/mach-davinci/davinci.h |2 +-
arch/arm/mach-davinci/dm355.c
From: Lad, Prabhakar
This patch series enables VPBE display driver on DM355.
This patch series is dependent on VPSS clock cleanup patches
(http://www.mail-archive.com/davinci-linux-open-source@linux.davincidsp.com/msg25499.html)
posted.
Chnages for v6:
1: Fixed nits pointed by Sekhar.
Changes
From: Lad, Prabhakar
add support for V4L2 video display to DM355 EVM.
Support for SD modes is provided, along with Composite
output
Signed-off-by: Lad, Prabhakar
---
arch/arm/mach-davinci/board-dm355-evm.c | 69 ++-
1 files changed, 68 insertions(+), 1 deletions
Sekhar,
On Mon, Mar 18, 2013 at 2:11 PM, Sekhar Nori wrote:
> On 3/16/2013 3:47 PM, Prabhakar lad wrote:
>> From: Lad, Prabhakar
>>
>> Create platform devices for various video modules like venc,osd,
>> vpbe and v4l2 driver for dm355.
>>
>> Signed-off-
On 3/16/2013 3:47 PM, Prabhakar lad wrote:
> From: Lad, Prabhakar
>
> Create platform devices for various video modules like venc,osd,
> vpbe and v4l2 driver for dm355.
>
> Signed-off-by: Lad, Prabhakar
Comments on the DM365 series apply to this one too. In additi
From: Lad, Prabhakar
add support for V4L2 video display to DM355 EVM.
Support for SD modes is provided, along with Composite
output
Signed-off-by: Lad, Prabhakar
---
arch/arm/mach-davinci/board-dm355-evm.c | 69 ++-
1 files changed, 68 insertions(+), 1 deletions
From: Lad, Prabhakar
This patch series enables VPBE display driver on DM355.
Changes for v5:
1: Rebased on 3.9, fix review comments pointed by Sekhar for DM365 series.
Changes for v4:
1: pass different platform names to handle different ip's.
Changes for v3:
1: Replaced obsolete preset A
From: Lad, Prabhakar
Create platform devices for various video modules like venc,osd,
vpbe and v4l2 driver for dm355.
Signed-off-by: Lad, Prabhakar
---
arch/arm/mach-davinci/board-dm355-evm.c |4 +-
arch/arm/mach-davinci/davinci.h |2 +-
arch/arm/mach-davinci/dm355.c
drivers/media/platform/davinci/dm355_ccdc.c:593:9: warning: ‘val1’ may be
used uninitialized in this function [-Wuninitialized]
drivers/media/platform/davinci/dm355_ccdc.c:560:6: note: ‘val1’ was declared
here
This is a false positive but the compiler has no way to know about it,
so initialize th
From: Manjunath Hadli
add support for V4L2 video display to DM355 EVM.
Support for SD modes is provided, along with Composite
output
Signed-off-by: Manjunath Hadli
Signed-off-by: Lad, Prabhakar
---
arch/arm/mach-davinci/board-dm355-evm.c | 71 ++-
1 files
From: Manjunath Hadli
Create platform devices for various video modules like venc,osd,
vpbe and v4l2 driver for dm355.
Signed-off-by: Manjunath Hadli
Signed-off-by: Lad, Prabhakar
---
arch/arm/mach-davinci/board-dm355-evm.c |4 +-
arch/arm/mach-davinci/davinci.h |2 +-
arch
From: Manjunath Hadli
This patch series enables VPBE display driver on DM355.
Changes for v4:
1: pass different platform names to handle different ip's.
Changes for v3:
1: Replaced obsolete preset API by timings API.
Changes for v2:
1: Removed VPSS clock alias for master and slave whic
From: Lad, Prabhakar
This patch allows enabling building of VPBE display driver for DM365
and DM355. This also removes unnecessary entry VIDEO_DM644X_VPBE
in Kconfig, which could have been done with single entry, and
appropriate changes in Makefile for building.
Signed-off-by: Lad, Prabhakar
On 10/15/2012 02:42 PM, cristiane.san...@ivision.ind.br wrote:
Hi!
I need to make a pulse counter with davinci DM355.
I'm tryng to use timer3 (External event capture via timer input pins),
but I didn't get.
Anyone knows how to do this?
Thanks
You can use a GPIO in interrupt mode
Hi!
I need to make a pulse counter with davinci DM355.
I'm tryng to use timer3 (External event capture via timer input pins),
but I didn't get.
Anyone knows how to do this?
Thanks
___
Davinci-linux-open-source mailing list
Davinci-linux-o
The clock tree for dm355 is defined using the new structure davinci_clk.
The SoC specific code re-uses clk-fixed-rate, clk-divider,
clk-fixed-factor and clk-mux drivers in addition to the davinci
specific clk drivers, clk-davinci-pll and clk-davinci-psc.
Macros are used to define the various
The clock tree for dm355 is defined using the new structure davinci_clk.
The SoC specific code re-uses clk-fixed-rate, clk-divider,
clk-fixed-factor and clk-mux drivers in addition to the davinci
specific clk drivers, clk-davinci-pll and clk-davinci-psc.
Macros are used to define the various
The clock tree for dm355 is defined using the new structure davinci_clk.
The SoC specific code re-uses clk-fixed-rate, clk-divider,
clk-fixed-factor and clk-mux drivers in addition to the davinci
specific clk drivers, clk-davinci-pll and clk-davinci-psc.
Macros are used to define the various
i put it in the sun the image is
> completely washed out?.
>
>
> On 18 August 2012 12:06, venkatasubramanian P wrote:
>
>> Dear sir,
>> Thank for your help it is very helpful for our project
>> development.So by using dm355 how much resolution picture
elpful for our project
> development.So by using dm355 how much resolution picture i can able to
> capture.It is possible to capture 1080p raw then split into two then given
> to the ipipe and then it is possible to merge.I have a code with is
> capturing a 1280x720 and saved in yuv422
Dear sir,
Thank for your help it is very helpful for our project
development.So by using dm355 how much resolution picture i can able to
capture.It is possible to capture 1080p raw then split into two then given
to the ipipe and then it is possible to merge.I have a code with is
lly to convert the RAW bayer
image to viewable format) . So if the ipipe is bypassed it will be just
RAW data.
Thx,
--Prabhakar
> On 17 August 2012 13:10, Prabhakar Lad <mailto:prabhakar@ti.com>> wrote:
>
>
> In DM355 the ipipe can work with upto 1344 pixels in eac
:
>
> In DM355 the ipipe can work with upto 1344 pixels in each horizontal
> line, so due to this restriction you cannot capture 1920*1080 raw image.
>
> Thanks and regards,
> --Prabhakar
>
> On Friday 17 August 2012 11:53 AM, venkatasubramanian P wrote:
> > Dear sir,
>
Hi,
In DM355 the ipipe can work with upto 1344 pixels in each horizontal
line, so due to this restriction you cannot capture 1920*1080 raw image.
Thanks and regards,
--Prabhakar
On Friday 17 August 2012 11:53 AM, venkatasubramanian P wrote:
> Dear sir,
> Now dm355 is supp
Dear sir,
Now dm355 is supporting 720p video it will support for
1080p.Then image how much resolution we can take.Now i am using mt9p031 5mp
camera i am able to capture a picture up to 1280x720 it is possible to
increase the picture size to 1920x1080.
On 16 August 2012 10:24
he location and
> > i could able to find the idle thread there.Thanks for your valuable
> > support.I am facing one more problem in dm355.I am using dvtb to take a
> > picture and i could able to take a picture.But i am trying to take a
> > video by using dvtb it is hitting a
Hi venkatasubramanian,
On 8/14/2012 10:22 PM, venkatasubramanian P wrote:
> Hi sir,
>You are absolutely correct i checked in the location and
> i could able to find the idle thread there.Thanks for your valuable
> support.I am facing one more problem in dm355.I am u
Hi sir,
You are absolutely correct i checked in the location and i
could able to find the idle thread there.Thanks for your valuable support.I
am facing one more problem in dm355.I am using dvtb to take a picture and i
could able to take a picture.But i am trying to take a video by
On 8/13/2012 4:19 PM, venkatasubramanian P wrote:
> Hi sir,
> Thanks for your replay how can i put dm355 into wait for
> interrupt mode.My kernel is 2.6.10.
This should hit automatically if ARM is idle. Have a look at ARM's idle
thread implementation in arch/arm/kerne
Hi sir,
Thanks for your replay how can i put dm355 into wait for
interrupt mode.My kernel is 2.6.10.
On 13 August 2012 16:05, Sekhar Nori wrote:
> Hi venkatasubramanian,
>
> On 8/13/2012 3:51 PM, venkatasubramanian P wrote:
> > Hi,
> > Can i put my dm35
Hi venkatasubramanian,
On 8/13/2012 3:51 PM, venkatasubramanian P wrote:
> Hi,
> Can i put my dm355 into low power mode or deep sleep mode or
> wait for interrupt Mode.I read some forum non of the davinci kernel
> having power management only omap kernel having the low powe
Hi,
Can i put my dm355 into low power mode or deep sleep mode or wait
for interrupt Mode.I read some forum non of the davinci kernel having power
management only omap kernel having the low power mode.
--
Regards,
Venkatasubramanian.p
avench systems
#105 80/1 1st Main 3rd Cross
From: Manjunath Hadli
add support for V4L2 video display to DM355 EVM.
Support for SD modes is provided, along with Composite
output
Signed-off-by: Manjunath Hadli
Signed-off-by: Lad, Prabhakar
---
arch/arm/mach-davinci/board-dm355-evm.c | 71 ++-
1 files
This patch series enables VPBE display driver on DM355.
This patch series is dependent on this patches posted
http://www.spinics.net/lists/arm-kernel/msg188234.html
Changes for v3:
1: Replaced obsolete preset API by timings API.
Changes for v2:
1: Removed VPSS clock alias for master and
From: Manjunath Hadli
Create platform devices for various video modules like venc,osd,
vpbe and v4l2 driver for dm355.
Signed-off-by: Manjunath Hadli
Signed-off-by: Lad, Prabhakar
---
arch/arm/mach-davinci/board-dm355-evm.c |4 +-
arch/arm/mach-davinci/davinci.h |2 +-
arch
From: Manjunath Hadli
Create platform devices for various video modules like venc,osd,
vpbe and v4l2 driver for dm355.
Signed-off-by: Manjunath Hadli
Signed-off-by: Lad, Prabhakar
---
Changes for v2:
1: Removed vpss master and slave clock aliases.
arch/arm/mach-davinci/board-dm355-evm.c
From: Manjunath Hadli
add support for V4L2 video display to DM355 EVM.
Support for SD modes is provided, along with Composite
output.
Signed-off-by: Manjunath Hadli
Signed-off-by: Lad, Prabhakar
---
Changes for v2: None
arch/arm/mach-davinci/board-dm355-evm.c | 71
This patch series enables VPBE display driver on DM355.
Changes for v2:
1: Removed VPSS clock alias for master and slave which was
sent for VPSS driver. since this patch was dependent on
patch[1]. I will revist this patch once MC(captrure driver)
goes into mainline.
[1] http
From: Manjunath Hadli
Create platform devices for various video modules like venc,osd,
vpbe and v4l2 driver for dm355.
Signed-off-by: Manjunath Hadli
Signed-off-by: Lad, Prabhakar
---
arch/arm/mach-davinci/board-dm355-evm.c |4 +-
arch/arm/mach-davinci/davinci.h |2 +-
arch
From: Manjunath Hadli
add support for V4L2 video display to DM355 EVM.
Support for SD modes is provided, along with Composite
output.
Signed-off-by: Manjunath Hadli
Signed-off-by: Lad, Prabhakar
---
arch/arm/mach-davinci/board-dm355-evm.c | 71 ++-
1 files
This patch series enables VPBE display driver on DM355.
Manjunath Hadli (2):
ARM: davinci: dm355: add support for v4l2 video display
ARM: davinci: dm355 EVM: add support for VPBE display
arch/arm/mach-davinci/board-dm355-evm.c | 73 ++-
arch/arm/mach-davinci/davinci.h
From: Manjunath Hadli
add Kconfig and Makefile changes to build VPBE display
driver on dm365 and dm355 along with dm644x.
Signed-off-by: Manjunath Hadli
Signed-off-by: Lad, Prabhakar
---
drivers/media/video/davinci/Kconfig | 12 ++--
drivers/media/video/davinci/Makefile |2
he DM36X suspend support in Linux at
> >> the moment? From what I can see detailed at
> >> http://processors.wiki.ti.com/index.php/DaVinci_GIT_Linux_Kernel#Power_Management
> >> and from the Linux kernel code, it would appear that there is currently
> >> only sup
/processors.wiki.ti.com/index.php/DaVinci_GIT_Linux_Kernel#Power_Management
>> and from the Linux kernel code, it would appear that there is currently
>> only support for the DA850 and OMAP-L138.
>
> That's right, DM355/DM365 hardware has suspend capability, but that's not
from the Linux kernel code, it would appear that there is currently
> only support for the DA850 and OMAP-L138.
That's right, DM355/DM365 hardware has suspend capability, but that's not
available in kernel yet.
>
> Is anyone working on this, or any out-of-tree patches availabl
Hello,
Can anyone tell me the status of the DM36X suspend support in Linux at
the moment? From what I can see detailed at
http://processors.wiki.ti.com/index.php/DaVinci_GIT_Linux_Kernel#Power_Management
and from the Linux kernel code, it would appear that there is currently
only support for the DA
comes along.
At least on DA830 power domains appear to be programmable. So I'd still
like the patch to be applied (I could drop DM355 check though).
The problem would be that power domain state transition procedure isn't
documented for any SoC other than DM644x. So, we can never be su
t this time, it would be better to leave the code as-is and
> > revisit it if/when a new SoC with programmable power domain
> > support comes along.
>
> At least on DA830 power domains appear to be programmable. So I'd still
> like the patch to be applied (I could drop DM3
we support (don't have the specifications
But we support more than 6 SoCs... :-)
for tnetv107x; and code does not have evidence of a separate
DSP power domain).
It looks like none of the SoCs except DM6446 actually support
powering down the DSP power domain.
DM6467, DM355, DM365 al
r domain support for each of the 6
DaVinci SoCs we support (don't have the specifications
for tnetv107x; and code does not have evidence of a separate
DSP power domain).
It looks like none of the SoCs except DM6446 actually support
powering down the DSP power domain.
DM6467, DM355, DM365 all
Hi,
1, maybe there is something wrong with your env, pls send your bootcmd and
bootargs.
2, connect both your computer and the board to ethernet via separate cables
or just interconnect them is both ok.
3, use printenv to see what the ip of hardware is.
2011-09-20
benxuelan0402
_
I never tested soc_camera interface for dm355. But, you can directly call
vpfe_capture driver through v4l2 API for capturing camera buffers. vpfe_capture
driver will call sensor driver directly whenever necessary.
Also post this question in Ti e2e forum, your query will reach bigger community
Add OSD block changes to enable dm365 and dm355 for vpbe driver.
Changes are based on version number of OSD, which have incremental
changes over 644x OSD hardware interms of few registers.
VPBE_VERSION_2 = dm365 specific
VPBE_VERSION_3 = dm355 specific
Signed-off-by: Manjunath Hadli
This patch implements necessary changes for enabling dm365 and
dm355 hardware for vpbe. The patch contains additional HD mode
support for dm365 (720p60, 1080i30) and appropriate register
modifications based on version numbers.
VPBE_VERSION_2 = dm365 specific
VPBE_VERSION_3 = dm355 specific
m] On Behalf
>> Of Sergei Shtylyov
>> Sent: Thursday, September 15, 2011 10:30 AM
>> To: Hilman, Kevin; davinci-linux-open-source@linux.davincidsp.com; Nori,
>> Sekhar
>> Cc: linux-arm-ker...@lists.infradead.org
>> Subject: [PATCH] DaVinci: only poll EPCPR on DM
ng it?
Before getting into the details of the problem, a general overview would
help a bunch.
1.) Does this kernel version have support for the soc-camera framework
on the DM355?
2.) Is there a document (other than soc-camera.txt) that describes the
soc-camera framework at a high level? What file
EPCPR register and PDCTL.EPCGOOD bit exist only on DaVinci DM644x and DM35x,
so do not try to poll EPCPR and set PDCTL.EPCGOOD on the other SoCs -- it would
lead to lock up if some power domain hasn't been powered up by this time (which
hasn't happened yet on any board, it seems).
Signed-off-by: S
On Thu, Sep 8, 2011 at 11:40 PM, Samarth wrote:
> I am new to TI EVMs. I was trying to run a simple piece of code on the EVM
> but I
> couldn't boot the board.
>
> here's the error I get in U-boot -
>
> Looking up port of RPC 13/2 on 127.0.0.1
> RPC: sendmsg returned error 22
> portmap: RPC
I am new to TI EVMs. I was trying to run a simple piece of code on the EVM but I
couldn't boot the board.
here's the error I get in U-boot -
Looking up port of RPC 13/2 on 127.0.0.1
RPC: sendmsg returned error 22
portmap: RPC call returned error 22
Root-NFS: Unable to get nfsd port number fro
Add OSD block changes to enable dm365 and dm355 for vpbe driver.
Changes are based on version number of OSD, which have incremental
changes over 644x OSD hardware interms of few registers.
VPBE_VERSION_2 = dm365 specific
VPBE_VERSION_3 = dm355 specific
Signed-off-by: Manjunath Hadli
This patch implements necessary changes for enabling dm365 and
dm355 hardware for vpbe. The patch contains additional HD mode
support for dm365 (720p60, 1080i30) and appropriate register
modifications based on version numbers.
VPBE_VERSION_2 = dm365 specific
VPBE_VERSION_3 = dm355 specific
Hello,
We are using a dm355 evm board and we want to write large files to a SDHC
memory card. The demo board running Linux 2.6.32-rc2-davinci (argo-project)
and the SD card is used as a block device (/dev/mmcblk0p1) and the host
controller use DMA and 4bit mode ( davinci_mmc davinci_mmc.0
The sram region defined for dm355 in the iotable entry removed is also
defined in its davinci_soc_info, davinci_soc_info_dm355 in dm355.c.
Remove this duplicate information which is now uneccessary since sram
init will ioremap the region defined by davinci_soc_info_dm355.
Signed-off-by: Ben
Jon Povey wrote:
>>>>> Jon Povey wrote:
>>>>>> I am seeing rare SD card write corruption on DM355
>
> I think I have a fix for this now - just CC'd you on the patch RFC
>
> [RFC] mmc: davinci: fix corruption after surprise card eject
>
&g
Gilles Chanteperdrix wrote:
> Jon Povey wrote:
>> I think I have a fix for this now - just CC'd you on the patch RFC
>>
>> [RFC] mmc: davinci: fix corruption after surprise card eject
>>
>> (Which fixes it, but may not be the best way of going about it).
>
> If I read you correctly, it seems that t
Move the eventq assignment for spi0 out of resources and into platform data.
Signed-off-by: Michael Williamson
---
arch/arm/mach-davinci/dm355.c |5 +
1 files changed, 1 insertions(+), 4 deletions(-)
diff --git a/arch/arm/mach-davinci/dm355.c b/arch/arm/mach-davinci/dm355.c
index
Jon Povey wrote:
>>>>> Jon Povey wrote:
>>>>>> I am seeing rare SD card write corruption on DM355
>
> I think I have a fix for this now - just CC'd you on the patch RFC
>
> [RFC] mmc: davinci: fix corruption after surprise card eject
>
&g
>>>> Jon Povey wrote:
>>>>> I am seeing rare SD card write corruption on DM355
I think I have a fix for this now - just CC'd you on the patch RFC
[RFC] mmc: davinci: fix corruption after surprise card eject
(Which fixes it, but may not be the best way of going
Gilles Chanteperdrix wrote:
>>> Jon Povey wrote:
>>>> I am seeing rare SD card write corruption on DM355
> We did not investigate this issue any further (and notably, we did not
> hexdump the SD card contents when corrupted), but it certainly looks
> like something l
Jon Povey wrote:
> Gilles Chanteperdrix wrote:
>> Jon Povey wrote:
>>> I am seeing rare SD card write corruption on DM355 running
>>> 2.6.36. The system will get itself into a state where it appears
>>> all SD writes are offset by two bytes. This is using
Hi Jon,
On Mon, Jan 31, 2011 at 10:15:10, Jon Povey wrote:
> Gilles Chanteperdrix wrote:
> > Jon Povey wrote:
> >> I am seeing rare SD card write corruption on DM355 running 2.6.36.
> >> The system will get itself into a state where it appears all SD
> >> wri
Gilles Chanteperdrix wrote:
> Jon Povey wrote:
>> I am seeing rare SD card write corruption on DM355 running 2.6.36.
>> The system will get itself into a state where it appears all SD
>> writes are offset by two bytes. This is using a vfat filesystem on
>> the
Jon Povey wrote:
> I am seeing rare SD card write corruption on DM355 running 2.6.36.
> The system will get itself into a state where it appears all SD writes are
> offset by two bytes. This is using a vfat filesystem on the SD, and
> affects the FAT and directories at least.
Hi,
I am seeing rare SD card write corruption on DM355 running 2.6.36.
The system will get itself into a state where it appears all SD writes are
offset by two bytes. This is using a vfat filesystem on the SD, and
affects the FAT and directories at least.
When I look at the contents of the SD card
existing driver,
DM355 DMAproblem
Hi,
I have tested the new driver using DMA mode on our custom DM355 board.
I
replaced the linux 2.6.32 spi driver by this driver and it seemed to
work except for on point. The dm355 spi polling mode was correctly
working but the DMA mode was causing some
; Subject: Re: [PATCH 00/49] spi: davinci: re-write existing driver,
> DM355 DMAproblem
>
> Hi,
>
> I have tested the new driver using DMA mode on our custom DM355 board.
> I
> replaced the linux 2.6.32 spi driver by this driver and it seemed to
> work except for on po
ur at each transfer.
The details of what i noticed is:
-Chipselect to the client is a GPIO, chip_sel array is a 1 byte array
containing the gpio pin.
-The DM355 application uses spidev char driver to read and write data to
spidev0.0
-When dm355 was reading a 16 bytes buffer, the client sen
Hi Pierre,
On Tue, Nov 23, 2010 at 16:43:27, Pierre wrote:
> Hi,
>
> I have tested the new driver using DMA mode on our custom DM355 board. I
> replaced the linux 2.6.32 spi driver by this driver and it seemed to
> work except for on point. The dm355 spi polling mode was correctl
Hi,
I have tested the new driver using DMA mode on our custom DM355 board. I
replaced the linux 2.6.32 spi driver by this driver and it seemed to
work except for on point. The dm355 spi polling mode was correctly
working but the DMA mode was causing some communication problems. It
appeared
hi all
I am porting open source Linux kernel into DM355, but I met a problem.
I am using Linux git kernel downloaded from Montavista open soure
git, and I modify the code in arch/arm/mach-davinci/ for DM355 EVM,
and sucessfully compiled out the uImage, but when I use u-boot's
tftp;
:00 2001
From: Yanir Lubetkin
Date: Mon, 13 Sep 2010 13:51:47 +0200
Subject: [PATCH] mt9p031 support for dm355-evm
---
arch/arm/mach-davinci/board-dm355-evm.c| 49 ++-
drivers/media/video/Kconfig| 10 +
drivers/media/video/Makefile |1 +
drivers/media
1 - 100 of 1686 matches
Mail list logo
