Improve the error prints to give more information about the offending
address size.
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
---
drivers/video/omap2/vram.c | 12 +---
1 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/drivers/video/omap2/vram.c
The DSS documentation didn't mention the option to give the VRAM start
address.
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
---
Documentation/arm/OMAP/DSS |7 ---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/Documentation/arm/OMAP/DSS
Use memblock_free() and memblock_remove() to remove the allocated or
reserved VRAM area from normal kernel memory.
This is a slightly modified version of patches from Felipe Contreras and
Namhyung Kim.
Reported-by: Felipe Contreras felipe.contre...@gmail.com
Reported-by: Namhyung Kim
In omap4, there is no explicit configuration register to enable mailbox clocks.
Defining dummy clock for mailbox clock module to keep the mailbox driver
backward compatible with previous omaps.
Signed-off-by: Hari Kanigeri h-kanige...@ti.com
---
arch/arm/mach-omap2/clock44xx_data.c |1 +
1
disabling rx interrupt on omap4 is different than its pre-decessors.
The bit in OMAP4_MAILBOX_IRQENABLE_CLR should be set to disable the
interrupts instead of clearing the bit.
Signed-off-by: Hari Kanigeri h-kanige...@ti.com
---
arch/arm/mach-omap2/mailbox.c |5 -
1 files changed, 4
Fix the checkpatch warnings observed in mailbox module
Signed-off-by: Hari Kanigeri h-kanige...@ti.com
---
arch/arm/plat-omap/mailbox.c |9 +
1 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/arch/arm/plat-omap/mailbox.c b/arch/arm/plat-omap/mailbox.c
index
In the current mailbox driver, the mailbox internal pointer for
callback can be directly manipulated by the Users, so a second
User can easily corrupt the first user's callback pointer.
The initial effort to correct this issue can be referred here:
https://patchwork.kernel.org/patch/107520/
Along
From: Fernando Guzman Lugo x0095...@ti.com
As pointed by Ohad Ben-Cohen, the variable rq_full flag is a
global variable, so if there are multiple mailbox users
there will be conflics. Now there is a full flag per
mailbox queue.
Version 2:
- Rebase to the latest.
Version 3:
- Remove spin_lock
Schedule the Tasklet to send only when mailbox fifo is full and there are
pending messages in kifo, else send the message directly in the Process
context. This would avoid needless scheduling of Tasklet for every message
transfer
Signed-off-by: Hari Kanigeri h-kanige...@ti.com
---
Thanks to Rene Sapiens and Omar Ramirez for their inputs on initial patch
set.
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg37278.html
The patch set addresses the following review comments from Rene and Omar.
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg37626.html
On Wed, Nov 10, 2010 at 02:04:14PM +0200, Tomi Valkeinen wrote:
On Wed, 2010-11-10 at 12:51 +0100, ext Paul Mundt wrote:
On Wed, Nov 10, 2010 at 11:45:18AM +0200, Tomi Valkeinen wrote:
Improve the error prints to give more information about the offending
address size.
On Wed, 2010-11-10 at 12:51 +0100, ext Paul Mundt wrote:
On Wed, Nov 10, 2010 at 11:45:18AM +0200, Tomi Valkeinen wrote:
Improve the error prints to give more information about the offending
address size.
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
1-3 queued for .37,
When SPI wake up from OFF mode, CS is in the wrong state: force it to
the inactive state.
During the system life, I monitored the CS behavior using a
oscilloscope. I also activated debug in omap2_mcspi, so I saw when
driver disable the clocks and restore context when device is not used.
Each
On Wed, Nov 10, 2010 at 11:45:18AM +0200, Tomi Valkeinen wrote:
Improve the error prints to give more information about the offending
address size.
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
1-3 queued for .37, thanks.
--
To unsubscribe from this list: send the line unsubscribe
-Original Message-
From: Rick Bronson [mailto:r...@efn.org]
Sent: Tuesday, November 09, 2010 10:24 AM
To: linux-omap@vger.kernel.org
Cc: Premi, Sanjeev
Subject: RE: Mistral AM37x (with AM3715) devel board networking broken
Hi Sanjeev,
Thanks much for the help.
I tried
-Original Message-
From: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Gadiyar, Anand
Sent: Tuesday, November 09, 2010 10:32 AM
To: Rick Bronson
Cc: linux-omap@vger.kernel.org; Premi, Sanjeev
Subject: Re: Mistral AM37x (with AM3715) devel
On 05/10/10 09:45, Peter Ujfalusi wrote:
Implement the suggested workaround for OMAP3 regarding to sDMA draining
issue, when the channel is disabled on the fly.
This errata affects the following configuration:
sDMA transfer is source synchronized
Buffering is enabled
SmartStandby is selected.
On 05/10/10 09:45, Peter Ujfalusi wrote:
Implement the suggested workaround for OMAP3 regarding to sDMA draining
issue, when the channel is disabled on the fly.
This errata affects the following configuration:
sDMA transfer is source synchronized
Buffering is enabled
SmartStandby is selected.
-Original Message-
From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
Sent: Wednesday, November 10, 2010 3:08 AM
To: G, Manjunath Kondaiah
Cc: linux-omap@vger.kernel.org;
linux-arm-ker...@lists.infradead.org; Cousson, Benoit;
Shilimkar, Santosh
Subject: Re: [PATCH v3
-Original Message-
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Tuesday, November 09, 2010 6:11 AM
To: G, Manjunath Kondaiah
Cc: linux-omap@vger.kernel.org;
linux-arm-ker...@lists.infradead.org; Cousson, Benoit; Kevin
Hilman; Shilimkar, Santosh
Subject: Re: [PATCH v4
-Original Message-
From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
Sent: Wednesday, November 10, 2010 3:43 AM
To: G, Manjunath Kondaiah
Cc: linux-omap@vger.kernel.org;
linux-arm-ker...@lists.infradead.org; Peter Ujfalusi;
Cousson, Benoit; Shilimkar, Santosh
Subject:
-Original Message-
From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
Sent: Wednesday, November 10, 2010 3:54 AM
To: G, Manjunath Kondaiah
Cc: linux-omap@vger.kernel.org;
linux-arm-ker...@lists.infradead.org; Cousson, Benoit;
Shilimkar, Santosh
Subject: Re: [PATCH v3
-Original Message-
From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
Sent: Wednesday, November 10, 2010 3:56 AM
To: G, Manjunath Kondaiah
Cc: linux-omap@vger.kernel.org;
linux-arm-ker...@lists.infradead.org; Cousson, Benoit;
Shilimkar, Santosh
Subject: Re: [PATCH v3
-Original Message-
From: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Kevin Hilman
Sent: Wednesday, November 10, 2010 4:18 AM
To: G, Manjunath Kondaiah
Cc: linux-omap@vger.kernel.org;
linux-arm-ker...@lists.infradead.org; Cousson,
-Original Message-
From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
Sent: Wednesday, November 10, 2010 4:42 AM
To: G, Manjunath Kondaiah
Cc: linux-omap@vger.kernel.org;
linux-arm-ker...@lists.infradead.org; Cousson, Benoit;
Shilimkar, Santosh
Subject: Re: [PATCH v3
-Original Message-
From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
Sent: Wednesday, November 10, 2010 4:59 AM
To: G, Manjunath Kondaiah
Cc: linux-omap@vger.kernel.org;
linux-arm-ker...@lists.infradead.org; Cousson, Benoit;
Shilimkar, Santosh
Subject: Re: [PATCH v3
Hi,
On Tue, 2010-11-09 at 18:12 +0100, ext Bryan Wu wrote:
Generic DPI panel driver includes the driver and 4 similar panel
configurations. It
will match the panel name which is passed from platform data and setup the
right configurations.
With generic DPI panel driver, we can remove
- Original Message -
From: Murphy, Dan dmur...@ti.com
SNIP
+static ssize_t cma3000_store_attr_grange(struct device *dev,
+ struct device_attribute *attr,
+ const char *buf, size_t count)
+{
+ struct
Hello,
I've updated my tree to the last pm-core branch today (I'm at commit
42289e226ec996a13ab8a2aaef5ad9dda61ee57e), and I've built the
omap2plus_defconfig with no change (except adding an initramfs). On my
BeagleBoard, I enable the wakeup from UART
in
On Wed, Nov 10, 2010 at 11:32:59AM +0100, Gregory CLEMENT wrote:
When SPI wake up from OFF mode, CS is in the wrong state: force it
to the inactive state.
During the system life, I monitored the CS behavior using a
oscilloscope. I also activated debug in omap2_mcspi, so I saw when
driver
On Wed, Nov 10, 2010 at 11:32:54AM +0100, Gregory CLEMENT wrote:
Some spi masters need to do some actions when system is going to suspend
or when it will be resumed.
Spi driver offer possibility to handle suspend and resume only for device.
Spi master will do its suspend actions after the
G, Manjunath Kondaiah manj...@ti.com writes:
[...]
+ if (reg OMAP1_CH_COMMON_START)
+ __raw_writew(val, dma_base +
+ (reg_map_omap1[reg] + 0x40 * lch));
+ else
+ __raw_writew(val, dma_base +
G, Manjunath Kondaiah manj...@ti.com writes:
G, Manjunath Kondaiah manj...@ti.com writes:
Enable runtime pm and use pm_runtime_get and pm_runtime_put
for OMAP DMA driver.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
Cc: Benoit Cousson b-cous...@ti.com
Cc: Kevin Hilman
G, Manjunath Kondaiah manj...@ti.com writes:
-Original Message-
From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
Sent: Wednesday, November 10, 2010 3:56 AM
To: G, Manjunath Kondaiah
Cc: linux-omap@vger.kernel.org;
linux-arm-ker...@lists.infradead.org; Cousson, Benoit;
G, Manjunath Kondaiah manj...@ti.com writes:
[...]
+ if (omap_type() == OMAP3430_REV_ES1_0)
+ SET_DMA_ERRATA(DMA_ERRATA_i88);
+
+ /*
+ * Errata 3.2/3.3: sometimes 0 is returned if CSAC/CDAC is
This doesn't look like a unique errata identifier. Chapter 3
is usually
Hi Thomas,
l-o is currently broken wrt to suspend and idle.
Solutions are being worked on for the moment.
Kevin, are there solutions available yet?
Regards,
Jean
On Wed, Nov 10, 2010 at 4:44 PM, Thomas Petazzoni
thomas.petazz...@free-electrons.com wrote:
Hello,
I've updated my tree to the
Hi Hari,
On 11/10/2010 1:45 PM, Hari Kanigeri wrote:
Thanks to Rene Sapiens and Omar Ramirez for their inputs on initial patch
set.
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg37278.html
The patch set addresses the following review comments from Rene and Omar.
On 11/10/2010 04:57 PM, Grant Likely wrote:
On Wed, Nov 10, 2010 at 11:32:59AM +0100, Gregory CLEMENT wrote:
When SPI wake up from OFF mode, CS is in the wrong state: force it
to the inactive state.
During the system life, I monitored the CS behavior using a
oscilloscope. I also activated
Hello.
Hari Kanigeri wrote:
Fix the checkpatch warnings observed in mailbox module
Signed-off-by: Hari Kanigeri h-kanige...@ti.com
---
arch/arm/plat-omap/mailbox.c |9 +
1 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/arch/arm/plat-omap/mailbox.c
Hari,
I forgot one comment. Since this series is a v2, every patches subject
should contain the [PATCH v2 x/6].
FYI, patchwork will not track the cover letter, so we will miss that
version information in the real patches.
I forgot as well this subject:
mailbox: change full flag per
On Wed, Nov 10, 2010 at 9:41 AM, Gregory CLEMENT
gregory.clem...@free-electrons.com wrote:
On 11/10/2010 04:57 PM, Grant Likely wrote:
On Wed, Nov 10, 2010 at 11:32:59AM +0100, Gregory CLEMENT wrote:
When SPI wake up from OFF mode, CS is in the wrong state: force it
to the inactive state.
-Original Message-
From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
Sent: Wednesday, November 10, 2010 9:33 PM
To: G, Manjunath Kondaiah
Cc: linux-omap@vger.kernel.org;
linux-arm-ker...@lists.infradead.org; Cousson, Benoit;
Shilimkar, Santosh
Subject: Re: [PATCH v3
-Original Message-
From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
Sent: Wednesday, November 10, 2010 9:54 PM
To: G, Manjunath Kondaiah
Cc: linux-omap@vger.kernel.org;
linux-arm-ker...@lists.infradead.org; Cousson, Benoit;
Shilimkar, Santosh
Subject: Re: [PATCH v3
Dmitry Kasatkin (5):
crypto: omap-aes: change in prevention of OCP bus error
omap-aes: DMA initialization fixes for OMAP off mode
omap-aes: redundant locking is removed
omap-aes: error handling implementation improved
omap-aes: unnecessary code removed
drivers/crypto/omap-aes.c | 269
Suggested to use udelay() instead of nop as on the higher
core frequencies it might not be enough time.
Signed-off-by: Dmitry Kasatkin dmitry.kasat...@nokia.com
---
drivers/crypto/omap-aes.c | 10 ++
1 files changed, 6 insertions(+), 4 deletions(-)
diff --git
DMA parameters for constant data were initialized during driver probe().
It seems that those settings sometimes are lost when devices goes to off mode.
This patch makes DMA initialization just before use.
It solves off mode problems.
Signed-off-by: Dmitry Kasatkin dmitry.kasat...@nokia.com
---
Key and IV should always be set before AES operation.
So no need to check if it has changed or not.
Signed-off-by: Dmitry Kasatkin dmitry.kasat...@nokia.com
---
drivers/crypto/omap-aes.c | 64 +++-
1 files changed, 16 insertions(+), 48 deletions(-)
diff
Dmitry Kasatkin (7):
crypto: updates omap sham device related platform code
crypto: omap-sham - omap sha1 md5 driver
omap-sham: OMAP macros corrected
omap-sham: uses digest buffer in request context
omap-sham: DMA initialization fixes for off mode
omap-sham: error handling improved
- registration with multi OMAP kernels support
- clocks
Signed-off-by: Dmitry Kasatkin dmitry.kasat...@nokia.com
---
arch/arm/mach-omap2/clock2420_data.c |2 +-
arch/arm/mach-omap2/clock2430_data.c |2 +-
arch/arm/mach-omap2/clock3xxx_data.c |2 +-
Earlier kernel contained omap sha1 and md5 driver, which was not maintained,
was not ported to new crypto APIs and removed from the source tree.
- implements async crypto API using dma and cpu.
- supports multiple sham instances if available
- hmac
- concurrent requests
Signed-off-by: Dmitry
Signed-off-by: Dmitry Kasatkin dmitry.kasat...@nokia.com
---
arch/arm/mach-omap2/devices.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mach-omap2/devices.c b/arch/arm/mach-omap2/devices.c
index beac46c..79dbf04 100644
--- a/arch/arm/mach-omap2/devices.c
Currently driver storred digest results in req-results
provided by the client. But some clients do not set it
until final() call. It leads to crash.
Changed to use internal buffer to store temporary digest results.
Signed-off-by: Dmitry Kasatkin dmitry.kasat...@nokia.com
---
DMA parameters for constant data were initialized during driver probe().
It seems that those settings sometimes are lost when devices goes to off mode.
This patch makes DMA initialization just before use.
It solves off mode problems.
Fixes: NB#202786 - Aegis SHA1 block off mode changes
Introduces DMA error handling.
DMA error is returned as a result code of the hash request.
Clients needs to handle error codes and may repeat hash calculation attempt.
Also in the case of DMA error, SHAM module is set to be re-initialized again.
It significantly improves stability against
Locking for queuing and dequeuing is combined.
test_and_set_bit() is also replaced with checking under dd-lock.
Signed-off-by: Dmitry Kasatkin dmitry.kasat...@nokia.com
---
drivers/crypto/omap-sham.c | 47 +++
1 files changed, 21 insertions(+), 26
Jean Pihet jean.pi...@newoldbits.com writes:
l-o is currently broken wrt to suspend and idle.
Solutions are being worked on for the moment.
Kevin, are there solutions available yet?
The solution to your previous problem (ensuring runtime PM transitions
work during system PM) is included in
DMA parameters for constant data were initialized during driver probe().
It seems that those settings sometimes are lost when devices goes to off mode.
This patch makes DMA initialization just before use.
It solves off mode problems.
Fixes: NB#202786 - Aegis SHA1 block off mode changes
Introduces DMA error handling.
DMA error is returned as a result code of the hash request.
Clients needs to handle error codes and may repeat hash calculation attempt.
Also in the case of DMA error, SHAM module is set to be re-initialized again.
It significantly improves stability against
Locking for queuing and dequeuing is combined.
test_and_set_bit() is also replaced with checking under dd-lock.
Signed-off-by: Dmitry Kasatkin dmitry.kasat...@nokia.com
---
drivers/crypto/omap-sham.c | 47 +++
1 files changed, 21 insertions(+), 26
-Original Message-
From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
Sent: Wednesday, November 10, 2010 9:56 PM
To: G, Manjunath Kondaiah
Cc: linux-omap@vger.kernel.org;
linux-arm-ker...@lists.infradead.org; Peter Ujfalusi;
Cousson, Benoit; Shilimkar, Santosh
Subject:
Hi,
On Wed, 2010-11-10 at 19:26 +0200, Dmitry Kasatkin wrote:
diff --git a/drivers/crypto/omap-aes.c b/drivers/crypto/omap-aes.c
index 9d65611..04cab70 100644
--- a/drivers/crypto/omap-aes.c
+++ b/drivers/crypto/omap-aes.c
@@ -99,7 +99,7 @@ struct omap_aes_reqctx {
struct omap_aes_dev {
G, Manjunath Kondaiah manj...@ti.com writes:
+#define OMAP_DMA4_LOGICAL_DMA_CH_COUNT 32 /*
REVISIT: Is this 32 + 2? */
+
There are no users of this in this patch, all users are removed.
This macro is used in hwmod data base. Do you mean hard coding this
value in hwmod db
Fix the checkpatch warnings observed in mailbox module
Signed-off-by: Hari Kanigeri h-kanige...@ti.com
---
arch/arm/plat-omap/mailbox.c |9 +
1 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/arch/arm/plat-omap/mailbox.c b/arch/arm/plat-omap/mailbox.c
index
In omap4, there is no explicit configuration register to enable mailbox clocks.
Defining dummy clock for mailbox clock module to keep the mailbox driver
backward compatible with previous omaps.
Signed-off-by: Hari Kanigeri h-kanige...@ti.com
---
arch/arm/mach-omap2/clock44xx_data.c |1 +
1
In the current mailbox driver, the mailbox internal pointer for
callback can be directly manipulated by the Users, so a second
User can easily corrupt the first user's callback pointer.
The initial effort to correct this issue can be referred here:
https://patchwork.kernel.org/patch/107520/
Along
Schedule the Tasklet to send only when mailbox fifo is full and there are
pending messages in kifo, else send the message directly in the Process
context. This would avoid needless scheduling of Tasklet for every message
transfer
Signed-off-by: Hari Kanigeri h-kanige...@ti.com
---
From: Fernando Guzman Lugo x0095...@ti.com
As pointed by Ohad Ben-Cohen, the variable rq_full flag is a
global variable, so if there are multiple mailbox users
there will be conflics. Now there is a full flag per
mailbox queue.
Version 2:
- Rebase to the latest.
Version 3:
- Remove spin_lock
Gopinath, Thara th...@ti.com writes:
Gopinath, Thara th...@ti.com writes:
On Wed, 2010-09-22 at 20:15 +0530, Thara Gopinath wrote:
This patch adds support for device registration of various
smartreflex module present in the system. This patch introduces
the platform data for smartreflex
On 11/10/2010 5:56 PM, Hari Kanigeri wrote:
Benoit,
Thanks for your comments.
On Wed, Nov 10, 2010 at 10:40 AM, Cousson, Benoitb-cous...@ti.com wrote:
Hi Hari,
On 11/10/2010 1:45 PM, Hari Kanigeri wrote:
Thanks to Rene Sapiens and Omar Ramirez for their inputs on initial patch
set.
[resend with thinned out response, since original reply was determined
to be spam by vger.kernel.org. wondering that tells me about my review
style... ]
Thara Gopinath th...@ti.com writes:
This patch adds voltage driver support for OMAP3. The driver
allows configuring the voltage
On 11/10/2010 5:56 PM, Hari Kanigeri wrote:
[...]
Good point, thanks for pointing about consistency. I wasn't aware
about the rule to use OMAP in caps.
Well, I'm not sure there is any rule like that, it is just what was
mostly used so far. My point was more about the text after the omap.
Gopinath, Thara th...@ti.com writes:
[...]
Also curious should:
OMAP: OPP: twl/tps: Introduce TWL/TPS-specific code should probably be
dropped with OMAP3: PM: Register TWL4030 pmic info with the voltage ?
Hmm.. Last time I suggested moving the contents of this patch to
twl-core.c Nobody
Thara Gopinath th...@ti.com writes:
This patch adds debug support to the voltage and smartreflex drivers.
This means a whole bunch of voltage processor and smartreflex
parameters are now visible through the pm debugfs.
The voltage parameters can be viewed at
On 11/10/2010 7:00 PM, Hari Kanigeri wrote:
Resending correcting the subject format based on Benoit's comment and
fixing the over-indentation pointed out by Sergei.
Pure nitpicking:
That's a pretty fast update... but then it should be a v3 :-)
Why does the cover letter not use the same
Hi,
On Wed, 2010-11-10 at 19:58 +0100, Cousson, Benoit wrote:
My point was that checkpatch is supposed to check patch... but it's true
that is can check the code as well. I was assuming that all the code in
mainline is supposed to be already checkpatch proof :-)
It seems that this is not
Thara Gopinath th...@ti.com writes:
OMAP4 has three scalable voltage domains vdd_mpu, vdd_iva
and vdd_core. This patch adds the voltage tables and other
configurable voltage processor and voltage controller
settings to control these three scalable domains in OMAP4.
Signed-off-by: Thara
Benoit,
Resending correcting the subject format based on Benoit's comment and
fixing the over-indentation pointed out by Sergei.
Pure nitpicking:
That's a pretty fast update... but then it should be a v3 :-)
Have to do it fast to keep your attention :). Since you are saying it
is pure
On 11/10/2010 9:16 PM, Hari Kanigeri wrote:
Benoit,
Resending correcting the subject format based on Benoit's comment and
fixing the over-indentation pointed out by Sergei.
Pure nitpicking:
That's a pretty fast update... but then it should be a v3 :-)
Have to do it fast to keep your
Hello Manju,
On Tue, 26 Oct 2010, G, Manjunath Kondaiah wrote:
Certain errata's in OMAP2+ processors will require disabling
master standby mode before completing on going operation. Without
this, the results will be unpredictable.
Since current implementation of PM run time framework does
Hello Hari
On Wed, 10 Nov 2010, Hari Kanigeri wrote:
In omap4, there is no explicit configuration register to enable mailbox
clocks.
Defining dummy clock for mailbox clock module to keep the mailbox driver
backward compatible with previous omaps.
If you split this off from the rest of your
Hello Adrian,
On Wed, 10 Nov 2010, Adrian Hunter wrote:
On 05/10/10 09:45, Peter Ujfalusi wrote:
+ if (cpu_is_omap34xx() (l OMAP_DMA_CCR_SEL_SRC_DST_SYNC)) {
+ int i = 0;
+ u32 sys_cf;
+
+ /* Configure No-Standby */
+ l =
On Tue, Nov 09, 2010 at 04:20:57AM -0500, Keerthy wrote:
Introducing a driver for MADC on TWL4030 powerIC. MADC stands for monitoring
ADC. This driver monitors the real time conversion of analog signals like
battery temperature, battery type, battery level etc. User can also ask for
the
Paul,
On Wed, Nov 10, 2010 at 5:27 PM, Paul Walmsley p...@pwsan.com wrote:
Hello Hari
On Wed, 10 Nov 2010, Hari Kanigeri wrote:
In omap4, there is no explicit configuration register to enable mailbox
clocks.
Defining dummy clock for mailbox clock module to keep the mailbox driver
* Benoit Cousson b-cous...@ti.com [101019 15:14]:
Add data for OMAP4430 generated from HW pinout register database.
The data set is split in two partitions for both core and wkup.
We should drop patch 3/7 and merge the following patch to your
4/7 patch.
Basically let's keep the
From: Felipe Contreras felipe.contre...@gmail.com
Also, don't be picky about the location, which incidentally fixes the
build since MEMBLOCK_REAL_LIMIT is gone on 2.6.37.
arch/arm/plat-omap/devices.c: In function 'omap_dsp_reserve_sdram_memblock':
arch/arm/plat-omap/devices.c:287: error:
Hi Greg,
Please consider the following patch set for tidspbridge driver in
staging tree, the following has been tested on an omap3430 based board
+ gst-dsp environment. Many thanks to Felipe Contreras for piling this up,
as I'm just propagating his patches.
First two patches:
1. omap: dsp:
From: Felipe Contreras felipe.contre...@gmail.com
On 2.6.37-rc1, omap platform internals for SCM have changed,
so the build is broken again.
drivers/staging/tidspbridge/core/tiomap3430.c:26:
fatal error: plat/control.h: No such file or directory
This is a totally ugly layer violation, but
On 11/11/10 01:30, ext Paul Walmsley wrote:
Hello Adrian,
On Wed, 10 Nov 2010, Adrian Hunter wrote:
On 05/10/10 09:45, Peter Ujfalusi wrote:
+ if (cpu_is_omap34xx() (l OMAP_DMA_CCR_SEL_SRC_DST_SYNC)) {
+ int i = 0;
+ u32 sys_cf;
+
+ /*
88 matches
Mail list logo
