* Removed duplicate return statement
* General code clean-up
My 1st patch.
---
diff --git a/drivers/video/omap2/dss/display.c
b/drivers/video/omap2/dss/display.c
index 6a74ea1..a5a6859 100644
--- a/drivers/video/omap2/dss/display.c
+++ b/drivers/video/omap2/dss/display.c
@@ -340,10 +340,11 @@ int
> -Original Message-
> From: Kanigeri, Hari
> Sent: Friday, April 16, 2010 9:47 PM
> To: linux-omap@vger.kernel.org
> Cc: Doyu Hiroshi (Nokia-D/Helsinki); Shilimkar, Santosh; t...@atomide.com
> Subject: [PATCH] ARM:iommu support for OMAP4
>
> From 708914e1a82a608d423b050cb31b4deb46eb8411 M
>From 1046e5fabff98074f706ed257c040ca3dd0decdb Mon Sep 17 00:00:00 2001
From: Ernesto Ramos
Date: Fri, 16 Apr 2010 21:46:50 -0500
Subject: [PATCH 5/5] DSPBRIDGE: Remove Reg module
Remove Reg module from services.
Signed-off-by: Ernesto Ramos
---
arch/arm/plat-omap/include/dspbridge/dbdcddef.h
>From 874bc262b47319b311d14ca32a7c1afb9eb388e8 Mon Sep 17 00:00:00 2001
From: Ernesto Ramos
Date: Thu, 1 Apr 2010 00:17:24 -0600
Subject: [PATCH 4/5] DSPBRIDGE: Remove handles from registry
Remove handles from registry.
Signed-off-by: Ernesto Ramos
---
arch/arm/plat-omap/include/dspbridge/drv.
>From 10010c14048a946190356cc682089d35b1bf7f48 Mon Sep 17 00:00:00 2001
From: Ernesto Ramos
Date: Fri, 16 Apr 2010 21:40:57 -0500
Subject: [PATCH 3/5] DSPBRIDGE: Remove DSP resources from registry
Remove DSP resources from registry.
Signed-off-by: Ernesto Ramos
---
arch/arm/plat-omap/include/d
>From 9ac5e14af1471b79a64076aec6b866abe87b3365 Mon Sep 17 00:00:00 2001
From: Ernesto Ramos
Date: Wed, 31 Mar 2010 21:10:16 -0600
Subject: [PATCH 1/5] DSPBRIDGE: Remove DSP resources from registry
Remove DSP resources from registry.
Signed-off-by: Ernesto Ramos
---
arch/arm/plat-omap/include/d
>From 4aee61479659b42127d107da6054e1c22be56d66 Mon Sep 17 00:00:00 2001
From: Cris Jansson
Date: Wed, 24 Mar 2010 11:12:05 -0600
Subject: [PATCH] DSPBRIDGE: MMU-Fault debugging enhancements
These changes allow for DSP task information to be printed
by the MPU dspbridge when DSP MMU fault ocurrs.
>From e8b0597f602aa501cdda039c609a5f4fe31b3281 Mon Sep 17 00:00:00 2001
From: Ernesto Ramos
Date: Fri, 16 Apr 2010 18:40:53 -0500
Subject: [PATCH 5/5] DSPBRIDGE: Avoid errors if stream id is zero
As 'zero' can be a perfectly good id, it can be picked up as
a NULL from userspace, avoid issues in A
>From 49cfb8a2ef77480ea5f622da9b80694387be Mon Sep 17 00:00:00 2001
From: Ernesto Ramos
Date: Fri, 16 Apr 2010 18:39:28 -0500
Subject: [PATCH 4/5] DSPBRIDGE: Use stream id instead of kernel address
Send stream ids to the user instead of handles, then when
the id is coming from user dspbridge
>From 615114515a5298d4510250507aa99544e923ba46 Mon Sep 17 00:00:00 2001
From: Ernesto Ramos
Date: Fri, 19 Mar 2010 11:38:27 -0600
Subject: [PATCH 3/5] DSPBRIDGE: Use processor handle from context instead of
user's
Make sure dspbridge driver uses a valid processor handle by
using the handle store
>From 827cbf0b4ade7ec7839b503922ecb278df1ff233 Mon Sep 17 00:00:00 2001
From: Ernesto Ramos
Date: Fri, 16 Apr 2010 18:22:36 -0500
Subject: [PATCH 2/5] DSPBRIDGE: Avoid errors if node handle is zero
As 'zero' can be a perfectly good id, it can be picked up as
a NULL from userspace, avoid issues in
>From 4e2c98b47ef85348674ad983334ac238be39beed Mon Sep 17 00:00:00 2001
From: Ernesto Ramos
Date: Fri, 16 Apr 2010 18:15:21 -0500
Subject: [PATCH 1/5] DSPBRIDGE: Use node id instead of kernel address
Use idr kernel library to send/receive node ids to the
user instead of kernel address.
This id wi
>From 9b263cc8cf0dea7e440aabb77fc88d06e01d62a4 Mon Sep 17 00:00:00 2001
From: Ernesto Ramos
Date: Thu, 18 Mar 2010 23:48:56 -0600
Subject: [PATCH] DSPBRIDGE: Always delete nodes during resource cleanup
Right now, during resource clean up, nodes are not being
deleted if they are in state NODE_DONE
>From 451e9733672b7fd3879ec109f3c6b2ac55c21cf5 Mon Sep 17 00:00:00 2001
From: Armando Uribe De Leon
Date: Thu, 8 Apr 2010 17:14:38 -0500
Subject: [PATCH 1/5] DSPBRIDGE: Remove checkpatch errors regarding braces
This patch removes checkpatch errors due to misleading braces
Signed-off-by: Armando
Hi,
On a board I'm working on, it has the OMAP 3530's camera port connected to
the Davinci DM6467's VPIF port. The Davince is supposed to send BT656 stream
over this link to OMAP. How to get the OMAP camera driver to work in this
situation?
In kernel config, I set the CONFIG_VIDEO_OMAP3_CAM=yes o
This hack should not be applied to any git trees.
Enables 800MHz and 1GHz OPPs on VDD1 for 36XX silicon and bypasses an
error condition in vp_forceupdate_scale_voltage to allow for voltage
scaling to happen in the absence of complete SmartReflex support.
These changes are needed to allow DVFS tra
Introduces voltscale_adaptive_body_bias function to voltage.c.
voltscale_adaptive_body_bias is called by omap_voltage_scale after a
voltage transition has occured. Currently voltscale_adaptive_body_bias
only implements Forward Body-Bias (FBB) for OMAP3630 when MPU runs at
1GHz or higher. In the f
PRCM on OMAP devices using the 45nm process support Adaptive Body Bias
ldo as well as some new MPU interrupts related to voltage control.
These devices currently include OMAP 3630 and 4430. This patch adds
these bitfields to the appropriate headers.
Also adds register offset for OMAP36XX_CONTROL_
This patch series introduces Forward Body-Bias (FBB), which is one
technique possible using the Adaptive Body-Bias (ABB) LDO. FBB boosts
voltage on VDD1 PMOS back gates which helps cold devices with weak
silicon characteristics sustain voltage at high OPPs.
All OMAP devices built on the 45nm proc
On Fri, Apr 16, 2010 at 2:07 PM, Nahamo wrote:
> Tomi Valkeinen nokia.com> writes:
>
>>
>> Hi,
>>
>> I haven't been able to boot my OMAP 3430SDP board with mainstream kernel
>> for a while, with the omap_3430sdp_defconfig. Anyone else having
>> problems? I don't get anything on the console after
I'm trying to run the DVSDK 3.01.00.03 on an OMAP/3530 board which is
not the OMAP3EVM (close, but from a different manufacturer).
I've ported my board specifics to the kernel that comes with
the DVSDK and everything seems to work.
Except for the video demos :-( When I try to run 'decode',
it at
>From bcdd232666a163d2661d704f9c21d055bacfd178 Mon Sep 17 00:00:00 2001
From: Hari Kanigeri
Date: Mon, 8 Mar 2010 18:00:36 -0600
Subject: [PATCH] ARM: OMAP add TLB preservation support to IOMMU
This patch adds TLB preservation support to IOMMU module
Signed-off-by: Hari Kanigeri
---
arch/arm/m
>From 708914e1a82a608d423b050cb31b4deb46eb8411 Mon Sep 17 00:00:00 2001
From: Hari Kanigeri
Date: Mon, 8 Mar 2010 17:55:21 -0600
Subject: [PATCH] ARM:iommu support for OMAP4
This patch provides the iommu support for OMAP4 co-processors.
Signed-off-by: Hari Kanigeri
---
arch/arm/mach-omap2/Make
Tomi Valkeinen nokia.com> writes:
>
> Hi,
>
> I haven't been able to boot my OMAP 3430SDP board with mainstream kernel
> for a while, with the omap_3430sdp_defconfig. Anyone else having
> problems? I don't get anything on the console after "Uncompressing
> Linux... done, booting the kernel.", a
Hi Ghorai,
On Fri, Apr 16, 2010 at 5:05 PM, Sukumar Ghorai wrote:
[...]
> - ret = gpmc_prefetch_enable(info->gpmc_cs, 0x0, len, 0x0);
> + ret = gpmc_prefetch_enable(info->gpmc_cs, 0x40, 0x0, len, 0x0);
Use macros here too then.
>if (ret) {
>/* PFPW engine is
I am trying to load the kernel (Linux
2.6.34-rc3-07875-geba0147-dirty) in the DevKit8K board. My default
output device is TV. Initially, none of the DSS devices got detected.
After merging the "Koen Kooi" patch, DSS devices are getting
detected and still getting below error:
[ 97.250915] OMAPFB:
Ivan,
> In the commit 702b94bff3c50542a6e4ab9a4f4cef093262fe65 (2.6.34) the
> functions
> dmac_inv_range and dmac_clean_range were removed.
>
> I'm wondering how to fix this in order to rebase to 2.6.34.
>
> Thanks
2 options:
1. Replace dmac_inv_range and dmac_clean_range functions with the ne
This patch overrides nand ecc layout and bad block descriptor (for 8-bit
device) to support hw ecc in romcode layout. So as to have in sync with ecc
layout throughout; i.e. x-laod, u-boot and kernel.
This patch also enables to use romcode ecc for spd and zoom, by default.
This
This patch makes it possible to select sw or hw (different layout options)
ecc scheme supported by omap nand driver. And hw ecc layout selected for
sdp and zoom boards, by default.
Signed-off-by: Sukumar Ghorai
Signed-off-by: Vimal Singh
---
arch/arm/mach-omap2/board-sdp-flash.c |
Update config file to enable NAND in prefetch IRQ mode for ZOOM3 and 3630SDP .
Signed-off-by: Sukumar Ghorai
---
arch/arm/configs/omap_3630sdp_defconfig |1 +
arch/arm/configs/omap_zoom3_defconfig |1 +
2 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/arm/configs/oma
Configure the FIFO THREASHOLD value to 50% (32 bytes) to keep busy both
filling and to drain out of FIFO at reading and writing.
Signed-off-by: Sukumar Ghorai
Signed-off-by: Vimal Singh
---
arch/arm/mach-omap2/gpmc.c |9 ++---
arch/arm/plat-omap/include/plat/gpmc.h |
This patch enable prefetch-irq mode for NAND.
Signed-off-by: Vimal Singh
Signed-off-by: Sukumar Ghorai
---
arch/arm/mach-omap2/board-sdp-flash.c |1 +
arch/arm/mach-omap2/board-zoom-flash.c |1 +
arch/arm/plat-omap/include/plat/nand.h |1 +
drivers/mtd/nand/Kconfig |
GPMC register definition move to common place in gpmc.h.
Signed-off-by: Sukumar Ghorai
Signed-off-by: Vimal Singh
---
arch/arm/mach-omap2/gpmc.c | 38 +--
arch/arm/plat-omap/include/plat/gpmc.h | 36 +++--
drivers/mtd/nand/omap
The main motivations behind this patch series are -
1. support NAND I/O in irq mode.
2. support of different ECC schema.
3. also to make ecc layout as like in romcode ecc layout
The following set of patches applies on top of the master branch. And
is dependent on
> -Original Message-
> From: Tomi Valkeinen [mailto:tomi.valkei...@nokia.com]
> Sent: Friday, April 16, 2010 3:08 PM
> To: Hiremath, Vaibhav
> Cc: linux-omap@vger.kernel.org
> Subject: Re: [PATCH] OMAP: DSS2: GFX FIFO UNDERFLOW issue fixed
>
> On Mon, 2010-03-22 at 14:09 +0100, ext hvaib.
> -Original Message-
> From: Hiremath, Vaibhav
> Sent: Friday, April 16, 2010 4:06 PM
> To: tomi.valkei...@nokia.com
> Cc: linux-omap@vger.kernel.org; Hiremath, Vaibhav
> Subject: [PATCH] OMAP: LCD LS037V7DW01: By default select backlight driver
> in Kconfig
>
> From: Vaibhav Hiremath
>
On Thu, Apr 08, 2010 at 06:47:13PM -0500, Gomez Castellanos, Ivan wrote:
> +/*
> + * mem_flush_cache
> + * Purpose:
> + * Flush cache
> + */
> +void mem_flush_cache(void *pMemBuf, u32 byte_size, s32 FlushType)
> +{
> + if (!pMemBuf)
> + return;
> +
> +
From: Vaibhav Hiremath
Signed-off-by: Vaibhav Hiremath
---
drivers/video/omap2/displays/Kconfig |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/drivers/video/omap2/displays/Kconfig
b/drivers/video/omap2/displays/Kconfig
index dfb57ee..44a6d63 100644
--- a/drivers/vid
This patch adapts smartreflex driver to support OMAP3630 also.
Changes involve:
1. Separate hwmod structures for OMAP3630 distinguished from
3430 structures using omap_chip attribute.
2. Introducing new test nvalues for OMAP3630.
3. OMAP3630 specific changes for srconfig err_minlimit field,
v
OMAP3430 uses the 65nm version of the smartreflex IP where as
OMAP3630 and OMAP4430 uses the 45nm updated IP.
This patch adds support for the updated smartreflex IP used
in OMAP3630 and OMAP4 in the smartreflex driver.
Major changes between the two versions of IP involve:
1. Change in offset posi
This patch series adds support for the updated 45nm smrtrelfex IP
supported in OMAP3630 and OMAP4 in the smartreflex driver and
adds support to enable smartreflex autocompensation for OMAP3630
using test nvalues.
This patch series is based on the V3 version of Smartreflex and
voltage revamp patch
> -Original Message-
> From: Tomi Valkeinen [mailto:tomi.valkei...@nokia.com]
> Sent: Friday, April 16, 2010 3:12 PM
> To: Hiremath, Vaibhav
> Cc: linux-omap@vger.kernel.org; t...@atomide.com
> Subject: Re: [PATCH-V2 1/2] OMAP: LCD LS037V7DW01: Add Backlight driver
> support
>
> Oops, my
On Wed, Mar 31, 2010 at 3:27 PM, Jarkko Nikula wrote:
> On Wed, 31 Mar 2010 04:27:41 -0600 (MDT)
> Paul Walmsley wrote:
>
>> > This patch moves register shift setting before any register accesses are
>> > done.
>> >
>> > Signed-off-by: Mika Westerberg
>> > Cc: Cory Maccarrone
>>
>> Tested-by:
Oops, my emailer decided to send the email a bit too soon =).
On Fri, 2010-04-16 at 11:39 +0200, Tomi Valkeinen wrote:
> On Mon, 2010-04-12 at 13:50 +0200, ext hvaib...@ti.com wrote:
> > From: Vaibhav Hiremath
> >
> > Tested on OMAP3EVM for OMAP3530 and AM/DM 3730.
> >
> > Signed-off-by: Vaibha
On Mon, 2010-04-12 at 13:50 +0200, ext hvaib...@ti.com wrote:
> From: Vaibhav Hiremath
>
> Tested on OMAP3EVM for OMAP3530 and AM/DM 3730.
>
> Signed-off-by: Vaibhav Hiremath
This patch causes omap_3430sdp_defconfig not to compile:
> ---
> .../video/omap2/displays/panel-sharp-ls037v7dw01.c
On Mon, 2010-03-22 at 14:09 +0100, ext hvaib...@ti.com wrote:
> From: Vaibhav Hiremath
>
> In case of 720P with 90/270 degree rotation, the system reports
> GFX_FIFO_UNDERFLOW error which usually happens if DSS DMA is not able to fill
> the FIFO as per requirement.
>
> In TRM (section 11.2.6.1.3
Op 16 apr 2010, om 13:05 heeft Thomas Weber het volgende geschreven:
> Hello Koen,
> On 04/16/10 08:38, Koen Kooi wrote:
>> No more comments on this one? Can it go into Tony's tree now?
>>
>> Op 15 apr 2010, om 10:52 heeft Koen Kooi het volgende geschreven:
>>
>>> This patch adds DSS2 support t
Hello Koen,
On 04/16/10 08:38, Koen Kooi wrote:
> No more comments on this one? Can it go into Tony's tree now?
>
> Op 15 apr 2010, om 10:52 heeft Koen Kooi het volgende geschreven:
>
>> This patch adds DSS2 support to the beagleboard boardfile. DVI and TV-out
>> are supported.
>>
>> Signed-off-
This patch corrects typo in some of the API names in smartreflex driver. It
also renames enable_smartreflex, disable_smartreflex APIs to
omap_smartreflex_enable and omap_smartreflex_disable to be
more consistent with rest of the API's in the driver code.
Signed-off-by: Thara Gopinath
---
arch/ar
This patch converts the exisitng smartreflex library into a
platform driver with device , driver registrations using hardware mods.
As part of this Ntarget values are passed as platform data.
Signed-off-by: Thara Gopinath
---
arch/arm/mach-omap2/Makefile |2 +-
arch/arm/mach-omap2/smart
This patch moves the hooks to enable disable smartreflex
autocompensation to pm debugfs from the /sys/power/.
To enable autocompensation for smartreflex SR do
echo 1 > /pm_debug/sr_autocomp
To disable autocompensation for smartreflex SR do
echo 0 > /pm_debug/sr_autocomp
Signed-off
This patch disables smartreflex across both frequency and voltage
scaling instead of just across voltage scaling as before.
This is the hardware recommended practice.
This bug was first reported and solved on Nokia N900
code base by Nishanth Menon and Paul Walmsley.
This patch also does some chang
There are two separate modules in SmartReflex-AVS :
MinMaxAvg module and Error module. Class3 uses the Error module only.
In Class2 you can choose between either module since it is software based.
The registers are mapped to the modules as followed:
MinMaxAvg module: AccumData, MinMaxAvgEnable, Mi
This patch cleans up smartreflex.h removing all unnecessary and
duplicate definitions.
Signed-off-by: Thara Gopinath
---
arch/arm/mach-omap2/smartreflex.h | 96 +
1 files changed, 55 insertions(+), 41 deletions(-)
diff --git a/arch/arm/mach-omap2/smartrefle
This patch introduces the framework to create voltage table per
VDD basis in voltage driver. Each VDD will have one voltage table,
which in turn will contain one entry per voltage supported and
other data associated with the voltage like smartreflex N-target
values. This patch also generates voltag
This patch removes VP1, VP2, SR1 and SR2 macros and replaces them with
VDD1 and VDD2 macros.
Signed-off-by: Thara Gopinath
---
arch/arm/mach-omap2/pm34xx.c |8 +++---
arch/arm/mach-omap2/smartreflex-class3.c |4 +-
arch/arm/mach-omap2/smartreflex.c| 26 +++--
This patch renames is_sr_reset to is_sr_enable and sets and unsets
this flag in appropriate places so that trying to enable smart reflex in a
non-supported OMAP chip does not lead to unnecessary crash.
Basically today if sr_enable fails, sr_disable will crash due to accessing
sr registers when sr
This patch enables smartreflex class 3 driver in omap3_pm_defconfig.
Signed-off-by: Thara Gopinath
---
arch/arm/configs/omap3_pm_defconfig |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/arm/configs/omap3_pm_defconfig
b/arch/arm/configs/omap3_pm_defconfig
index 6e8
This patch introduces OMAP3 specific values for Smartreflex and
Voltage processor registers as per the latest TI recommendations.
This patch adds smartreflex errminlimit and voltage processor
errorgain into the voltage tables as they vary with different
voltages. This patch also improves the smartr
This patch creates voltage.c and voltage.h files and
moves all voltage processor and voltage controller specific code
from smartreflex.c and other places in the OMAP3 codebase into
these two files.
This along with smartreflex class driver addition will make
smartreflex.c a generic driver to support
This patch introduces VP force update method of voltage scaling
and enables it by default. The older method of vc bypass is now
configuratble through a menu config option. VP force update is the
hardware recommended method of voltage scaling.
Signed-off-by: Thara Gopinath
---
arch/arm/mach-omap2
Smartreflex error config register is special as it contains
certain status bits which if written a 1 into means a clear
of those bits. This patch takes special care during modify of
this register that no status bits in this register are accidently
set to 1.
This issue was first reported by Nishant
Currently whenever smartreflex is disabled the voltage for the
particular VDD is reset to the non-smartreflex compensated level.
This step is unnecessary during dvfs because anyways in the next couple
of steps before re-enabling smartreflex , the voltage level is changed.
This patch adds the flexi
This patch removes get_vdd1_opp and get_vdd2_opp API's and replaces
them with get_curr_vdd1_voltage and get_curr_vdd2_voltage API's.
N-target values are now linked to voltages and the link bewtween
voltage and n-target values is managed internally in smartreflex
driver and sr_devices.c.
get_curr_v
This patch ensures that sr id is passed as a parameter only to
public APIs in smartreflex.c and other APIs in smartreflex.c
uses the omap_sr strucutres.
Signed-off-by: Thara Gopinath
---
arch/arm/mach-omap2/smartreflex.c | 36 +---
1 files changed, 13 insertions
This patch adds support to pdata enable smartreflex autocompenstion
during init based on enable_on_init flag passed as pdata.
This patch also adds enabling of autocompensation by
default (setting enable_on_init flag to true) in case of ES3.1
OMAP3430 chip. In the current implementation
this step
This patch adds smartreflex class 3 driver. This driver hooks
up with the generic smartreflex driver smartreflex.c to abstract
out class specific implementations out of the generic driver.
Signed-off-by: Thara Gopinath
---
arch/arm/mach-omap2/Makefile |1 +
arch/arm/mach-omap2/bo
This patch adds the hwmod strucutres and other hwmod data for
OMAP3 Smartreflex IP's.
Signed-off-by: Thara Gopinath
---
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 135
arch/arm/mach-omap2/smartreflex.h | 33 +++
2 files changed, 168 insertions(+), 0
This patch removes the pointer sr1, sr2 in smartreflex.c and
instead creatse a list for keeping track of multiple smartreflex
instances.. This makes it scalable for next gen OMAPs where there
are more than two smartreflex modules.
Signed-off-by: Thara Gopinath
---
arch/arm/mach-omap2/smartreflex
OMAP3 smartreflex modules are capable of two different classes
of implementaion -
Class-2: Continuous Software Calibration
Class-3: Continuous Hardware Calibration.
OMAP3 along with T2/Gaia supports the Class 3 implementaion.
With a different PMIC it can support Class 2 implementaio
The main motivations behind this patch series are the following
1. Making smartreflex a platform driver with omap-device layer.
2. Separating voltage specific code from smartreflex.c and other
locations and consolidating them into voltage.c and voltage.h.
3. Smartreflex module can have Class 1 C
On Fri, Apr 16, 2010 at 11:21:27AM +0300, Tomi Valkeinen wrote:
> Hi,
>
> I haven't been able to boot my OMAP 3430SDP board with mainstream kernel
> for a while, with the omap_3430sdp_defconfig. Anyone else having
> problems? I don't get anything on the console after "Uncompressing
> Linux... done
No more comments on this one? Can it go into Tony's tree now?
Op 15 apr 2010, om 10:52 heeft Koen Kooi het volgende geschreven:
> This patch adds DSS2 support to the beagleboard boardfile. DVI and TV-out are
> supported.
>
> Signed-off-by: Koen Kooi
> ---
>
> Changes since v1:
>* remo
> -Original Message-
> From: Kan-Ru Chen [mailto:ka...@0xlab.org]
> Sent: Friday, April 16, 2010 1:42 PM
> To: Tomi Valkeinen
> Cc: Kan-Ru Chen; linux-omap@vger.kernel.org; Hiremath, Vaibhav; linux-
> fb...@vger.kernel.org; Thomas Weber
> Subject: [RFC] [PATCH] Devkit8000: Use generic pane
Hi,
I haven't been able to boot my OMAP 3430SDP board with mainstream kernel
for a while, with the omap_3430sdp_defconfig. Anyone else having
problems? I don't get anything on the console after "Uncompressing
Linux... done, booting the kernel.", and Trace32 shows the log below.
Tomi
___address
Instead of use special driver for every new panel, we can use the
generic driver and modedb database to specify the timing
information. Now supports 4.3, 5.6 and 7 inch panel.
Signed-off-by: Kan-Ru Chen
---
Hi!
Some time ago there was a discussion about implementing a common
driver for dummy
On Thu, 2010-04-15 at 16:59 +0200, ext Grazvydas Ignotas wrote:
> This panel depends on SPI, not I2C.
>
> Signed-off-by: Grazvydas Ignotas
> ---
Thanks, applied into my tree.
Tomi
> drivers/video/omap2/displays/Kconfig |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff -
77 matches
Mail list logo
