Hi Liu Yebo,
About LCD are you getting distorted image on LCD or total blank display.
If you are getting blank display then you are missing sync pulses timing.
Just check it out.
Regards,
Onkar Patki,
Mechatronics Test Equipment (I) Pvt.Ltd.
----- Original Message -----
From: <[email protected]>
To: <[email protected]>
Sent: Tuesday, April 21, 2009 2:00 PM
Subject: Davinci-linux-open-source Digest, Vol 40, Issue 126
Send Davinci-linux-open-source mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Davinci-linux-open-source digest..."
Today's Topics:
1. [patch 2.6.30-rc2 1/2] palm_bk3710: those registers/bitfields
don't exist (David Brownell)
2. lcd interface to dm355 (Liu Yebo)
3. RE: DaVinci GIT kernel (Venkatachala Upadhya)
4. Re: [OT] short survey - how do you value codec engine?
(Leo DaVinci)
5. Re: lcd interface to dm355 (Kieran Bingham)
----------------------------------------------------------------------
Message: 1
Date: Mon, 20 Apr 2009 18:19:56 -0700
From: David Brownell <[email protected]>
Subject: [patch 2.6.30-rc2 1/2] palm_bk3710: those registers/bitfields
don't exist
To: Bartlomiej Zolnierkiewicz <[email protected]>
Cc: [email protected], DaVinci
<[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
From: David Brownell <[email protected]>
Bugfixes noted by checking the code against the controller
documentation (TI document number SPRUE21):
- Remove declarations for eight non-existent registers (!);
and remove accesses to two of them.
- Remove access to various non-existent bitfields in some of
the registers which *do* exist (those fields must-be-zero).
- Provide comment to replace bogus reset logic (removed above,
it relied on non-existent bitfields). Resets require GPIO
help; this driver doesn't currently know about that.
With some minor cleanup: relocate a comment, avoid an extra
lookup of the PIO timings.
Signed-off-by: David Brownell <[email protected]>
---
drivers/ide/palm_bk3710.c | 67
+++++++++++---------------------------------
1 file changed, 18 insertions(+), 49 deletions(-)
--- a/drivers/ide/palm_bk3710.c
+++ b/drivers/ide/palm_bk3710.c
@@ -50,16 +50,9 @@ struct palm_bk3710_udmatiming {
#define BK3710_BMICP 0x00
#define BK3710_BMISP 0x02
#define BK3710_BMIDTP 0x04
-#define BK3710_BMICS 0x08
-#define BK3710_BMISS 0x0A
-#define BK3710_BMIDTS 0x0C
#define BK3710_IDETIMP 0x40
-#define BK3710_IDETIMS 0x42
-#define BK3710_SIDETIM 0x44
-#define BK3710_SLEWCTL 0x45
#define BK3710_IDESTATUS 0x47
#define BK3710_UDMACTL 0x48
-#define BK3710_UDMATIM 0x4A
#define BK3710_MISCCTL 0x50
#define BK3710_REGSTB 0x54
#define BK3710_REGRCVR 0x58
@@ -71,7 +64,6 @@ struct palm_bk3710_udmatiming {
#define BK3710_UDMATRP 0x70
#define BK3710_UDMAENV 0x74
#define BK3710_IORDYTMP 0x78
-#define BK3710_IORDYTMS 0x7C
static unsigned ideclk_period; /* in nanoseconds */
@@ -98,11 +90,6 @@ static void palm_bk3710_setudmamode(void
trp = DIV_ROUND_UP(palm_bk3710_udmatimings[mode].rptime,
ideclk_period) - 1;
- /* udmatim Register */
- val16 = readw(base + BK3710_UDMATIM) & (dev ? 0xFF0F : 0xFFF0);
- val16 |= (mode << (dev ? 4 : 0));
- writew(val16, base + BK3710_UDMATIM);
-
/* udmastb Ultra DMA Access Strobe Width */
val32 = readl(base + BK3710_UDMASTB) & (0xFF << (dev ? 0 : 8));
val32 |= (t0 << (dev ? 8 : 0));
@@ -163,10 +150,11 @@ static void palm_bk3710_setpiomode(void
u32 val32;
struct ide_timing *t;
+ t = ide_timing_find_mode(XFER_PIO_0 + mode);
+
/* PIO Data Setup */
t0 = DIV_ROUND_UP(cycletime, ideclk_period);
- t2 = DIV_ROUND_UP(ide_timing_find_mode(XFER_PIO_0 + mode)->active,
- ideclk_period);
+ t2 = DIV_ROUND_UP(t->active, ideclk_period);
t2i = t0 - t2 - 1;
t2 -= 1;
@@ -187,7 +175,6 @@ static void palm_bk3710_setpiomode(void
}
/* TASKFILE Setup */
- t = ide_timing_find_mode(XFER_PIO_0 + mode);
t0 = DIV_ROUND_UP(t->cyc8b, ideclk_period);
t2 = DIV_ROUND_UP(t->act8b, ideclk_period);
@@ -236,42 +223,23 @@ static void palm_bk3710_set_pio_mode(ide
static void __devinit palm_bk3710_chipinit(void __iomem *base)
{
/*
- * enable the reset_en of ATA controller so that when ata signals
- * are brought out, by writing into device config. at that
- * time por_n signal should not be 'Z' and have a stable value.
+ * REVISIT: the ATA reset signal needs to be managed through a
+ * GPIO, which means it should come from platform_data. Until
+ * we get and use such information, we have to trust that things
+ * have been reset before we get here.
*/
- writel(0x0300, base + BK3710_MISCCTL);
-
- /* wait for some time and deassert the reset of ATA Device. */
- mdelay(100);
-
- /* Deassert the Reset */
- writel(0x0200, base + BK3710_MISCCTL);
/*
* Program the IDETIMP Register Value based on the following assumptions
*
* (ATA_IDETIMP_IDEEN , ENABLE ) |
- * (ATA_IDETIMP_SLVTIMEN , DISABLE) |
- * (ATA_IDETIMP_RDYSMPL , 70NS) |
- * (ATA_IDETIMP_RDYRCVRY , 50NS) |
- * (ATA_IDETIMP_DMAFTIM1 , PIOCOMP) |
* (ATA_IDETIMP_PREPOST1 , DISABLE) |
- * (ATA_IDETIMP_RDYSEN1 , DISABLE) |
- * (ATA_IDETIMP_PIOFTIM1 , DISABLE) |
- * (ATA_IDETIMP_DMAFTIM0 , PIOCOMP) |
* (ATA_IDETIMP_PREPOST0 , DISABLE) |
- * (ATA_IDETIMP_RDYSEN0 , DISABLE) |
- * (ATA_IDETIMP_PIOFTIM0 , DISABLE)
- */
- writew(0xB388, base + BK3710_IDETIMP);
-
- /*
- * Configure SIDETIM Register
- * (ATA_SIDETIM_RDYSMPS1 ,120NS ) |
- * (ATA_SIDETIM_RDYRCYS1 ,120NS )
+ *
+ * DM6446 silicon rev 2.1 and earlier have no observed net benefit
+ * from enabling prefetch/postwrite.
*/
- writeb(0, base + BK3710_SIDETIM);
+ writew(BIT(15), base + BK3710_IDETIMP);
/*
* UDMACTL Ultra-ATA DMA Control
@@ -283,11 +251,11 @@ static void __devinit palm_bk3710_chipin
/*
* MISCCTL Miscellaneous Conrol Register
- * (ATA_MISCCTL_RSTMODEP , 1) |
- * (ATA_MISCCTL_RESETP , 0) |
+ * (ATA_MISCCTL_HWNHLD1P , 1 cycle)
+ * (ATA_MISCCTL_HWNHLD0P , 1 cycle)
* (ATA_MISCCTL_TIMORIDE , 1)
*/
- writel(0x201, base + BK3710_MISCCTL);
+ writel(0x001, base + BK3710_MISCCTL);
/*
* IORDYTMP IORDY Timer for Primary Register
@@ -357,10 +325,9 @@ static int __init palm_bk3710_probe(stru
clk_enable(clk);
rate = clk_get_rate(clk);
- ideclk_period = 1000000000UL / rate;
- /* Register the IDE interface with Linux ATA Interface */
- memset(&hw, 0, sizeof(hw));
+ /* NOTE: round *down* to meet minimum timings; we count in clocks */
+ ideclk_period = 1000000000UL / rate;
mem = platform_get_resource(pdev, IORESOURCE_MEM, 0);
if (mem == NULL) {
@@ -390,6 +357,7 @@ static int __init palm_bk3710_probe(stru
/* Configure the Palm Chip controller */
palm_bk3710_chipinit(base);
+ memset(&hw, 0, sizeof(hw));
for (i = 0; i < IDE_NR_PORTS - 2; i++)
hw.io_ports_array[i] = (unsigned long)
(base + IDE_PALM_ATA_PRI_REG_OFFSET + i);
@@ -402,6 +370,7 @@ static int __init palm_bk3710_probe(stru
palm_bk3710_port_info.udma_mask = rate < 100000000 ? ATA_UDMA4 :
ATA_UDMA5;
+ /* Register the IDE interface with Linux */
rc = ide_host_add(&palm_bk3710_port_info, hws, NULL);
if (rc)
goto out;
------------------------------
Message: 2
Date: Tue, 21 Apr 2009 11:01:32 +0800
From: "Liu Yebo" <[email protected]>
Subject: lcd interface to dm355
To: <[email protected]>
Message-ID: <002a01c9c22d$7ff46610$1e01a...@04ab9ea5116c4d4>
Content-Type: text/plain; charset="gb2312"
Hi ALL,
I am using a LCD on our custom board based on DM355. Below is my
parameter settings for driver.
insmod davinci_enc_mngr.ko ch0_output=LCD ch0_mode=640x480
insmod davincifb.ko
options=vid0=640x480x4,1200K:vid1=640x480x4,1200K:osd0=640x480x4,1200K
There was a problem that the I can not get any images on LCD.
Can anybody please let me know, what I am missing here with the LCD
interface?
Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/20090421/a556458d/attachment-0001.htm
------------------------------
Message: 3
Date: Tue, 21 Apr 2009 09:46:47 +0530
From: Venkatachala Upadhya <[email protected]>
Subject: RE: DaVinci GIT kernel
To: "'Narnakaje, Snehaprabha'" <[email protected]>
Cc: "[email protected]"
<[email protected]>
Message-ID:
<a217382701a68b47a67f352c91940f8d01093ed...@mtw02msg01.mindtree.com>
Content-Type: text/plain; charset="us-ascii"
Hello Sneha,
Thanks Sneha for this first hand useful information.
It is useful to provide colour mapping to the status. That helps us to
understand the colour code the same way as you all understand. If it is only
RED, GREEN and YELLOW, I would have understood the meaning same as in
traffic signal light, but this page also has GREY colour.
Thanks,
With best regards,
Venkatachala Upadhya| Extn: 65395|
--
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
Narnakaje, Snehaprabha
Sent: 20 April, 2009 8:04 PM
To: Christophe Aeschlimann; Andrea Gasparini
Cc: [email protected]
Subject: RE: DaVinci GIT kernel
Christophe,
The page will soon be updated to include DA830/OMAP-L137 status.
Andrea, I have added MMC/SD driver status to the page.
Thanks
Sneha
-----Original Message-----
From: Christophe Aeschlimann [mailto:[email protected]]
Sent: Monday, April 20, 2009 8:13 AM
To: Narnakaje, Snehaprabha
Cc: [email protected]
Subject: Re: DaVinci GIT kernel
Narnakaje, Snehaprabha wrote:
> Hi all,
>
> We now have a wiki page on DaVinci wiki for the DaVinci GIT kernel.
>
> http://wiki.davincidsp.com/index.php?title=DaVinci_GIT_Linux_Kernel
>
> The page tries to cover status of different drivers on DaVinci series of
devices, including their status on the kernel.org mainline (or each
subsystem).
>
> We will try to update it on a weekly basis.
>
> Feel free to update it, if you have useful information to share.
>
> Thanks
> Sneha
>
Thank you for that nice work.
I'm interested to know if someone could give me the same information but
for the
DA830 / OMAP-L137 ?
Regards,
Christophe
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
http://www.mindtree.com/email/disclaimer.html
------------------------------
Message: 4
Date: Tue, 21 Apr 2009 09:53:58 +0200
From: Leo DaVinci <[email protected]>
Subject: Re: [OT] short survey - how do you value codec engine?
To: Koen Kooi <[email protected]>
Cc: [email protected]
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
Koen,
the Linux used / recommended for DaVinci products is a commercial
offering from MontaVista (MV pro 4.x or 5.x).
You can find some details about it on the MV website
http://www.mvista.com/product_detail_pro.php
or from the product folder of the DVSPB (
http://focus.ti.com/docs/toolsw/folders/print/tmdsdvspba9.html )
There are lots of resources on the web, including FAQs from MV, which
explain the commercial offering value proposition, for example see
http://www.mvista.com/why.php
Also, as for my knowledge of GPL and open source licensing issues
there is no problem in redistributing a Linux distribution but
charging for other things like medium of distribution, support,
testing etc. When you get the MV Pro you get it of course in source
format.
This is something lots of companies do, not only in the embedded world
Stuff like patch integration, system testing, kernel maintenance,
professional development tools (DevRocket), development utilities, etc
are things that are typically very costly to do in-house and require a
technical expertise that not every company doing embedded products
has, or is willing to invest in, especially if it is not not their
core business.
So at the end there is a recognized commercial value in this business
model which is the value proposition of the MV Linux offering, and
having said that, in short I don't believe there is a violation of
anything.
Also, I do not want to start a flame on this since this mailing list
is focused to discuss on technical issues related to DaVinci Linux.
Still, I hope it helps reassuring you a bit, and I thank you in
advance for taking the survey ;-)
On Mon, Apr 20, 2009 at 4:49 PM, Koen Kooi <[email protected]>
wrote:
On 20-04-09 16:28, Leo DaVinci wrote:
In order to address the users expectations, please take part in a short
survey:
http://www.ti.com/asia-codec-survey0902-en
any feedback is precious and will be highly appreciated....
Your survey implies that there is a non opensource linux, where did you
get
that from and why hasn't anyone sued its vendor yet for violating the GPL?
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
------------------------------
Message: 5
Date: Tue, 21 Apr 2009 09:29:55 +0100
From: Kieran Bingham <[email protected]>
Subject: Re: lcd interface to dm355
To: Liu Yebo <[email protected]>
Cc: [email protected]
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=UTF-8
You probably need to add code to support the initialisation of the
LCD, and ensure other parts are set up correctly.
What LCD are you using, How is it attached ....
Its likely that the LCD panel will need configuring through an SPI link
perhaps.
Setting ch0_output=LCD is only going to switch the Framebuffer output.
---
Kieran
2009/4/21 Liu Yebo <[email protected]>:
Hi ALL,
      I am using a LCD
on our custom board based on DM355. Below is my parameter settings for
driver.
insmod davinci_enc_mngr.ko ch0_output=LCD ch0_mode=640x480
insmod davincifb.ko
options=vid0=640x480x4,1200K:vid1=640x480x4,1200K:osd0=640x480x4,1200K
There was a problem that the I can not get any images on LCD.
Can anybody please let me know, what I am missing here with the LCD
interface?
Thanks!
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
--
Jonathan Swift - "May you live every day of your life." -
http://www.brainyquote.com/quotes/authors/j/jonathan_swift.html
------------------------------
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
End of Davinci-linux-open-source Digest, Vol 40, Issue 126
**********************************************************
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
