On Wed, Nov 24, 2010 at 10:46:04AM +0530, Varadarajan, Charulatha wrote:
diff --git a/arch/arm/plat-omap/mailbox.c b/arch/arm/plat-omap/mailbox.c
index 48e161c..a1c6bd9 100644
--- a/arch/arm/plat-omap/mailbox.c
+++ b/arch/arm/plat-omap/mailbox.c
@@ -358,6 +358,10 @@ int omap_mbox_register(struct
On Wed, 24 Nov 2010 15:20:48 +0800
Axel Lin axel@gmail.com wrote:
Return PTR_ERR(omap3pandora_dac_reg) instead of 0 if regulator_get failed.
Signed-off-by: Axel Lin axel@gmail.com
---
sound/soc/omap/omap3pandora.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff
On Wed, 24 Nov 2010 15:23:20 +0800
Axel Lin axel@gmail.com wrote:
Signed-off-by: Axel Lin axel@gmail.com
---
sound/soc/omap/osk5912.c | 11 ---
1 files changed, 8 insertions(+), 3 deletions(-)
Good catches,
Acked-by: Jarkko Nikula jhnik...@gmail.com
--
To unsubscribe
On Wed, Nov 24, 2010 at 12:53, Axel Lin axel@gmail.com wrote:
Add Patch description.
Signed-off-by: Axel Lin axel@gmail.com
---
sound/soc/omap/osk5912.c | 11 ---
1 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/sound/soc/omap/osk5912.c
Hi,
On Tue, 2010-11-23 at 19:00 -0600, ext Omar Ramirez Luna wrote:
From: Yanick Saugy yanick.sa...@heig-vd.ch
The PIN which controls LCD's reset signal (VGA_nRESET/h_GPIO_96) was not
configured as a GPIO. We had to modify the OMAP MUX, and select this PIN
(CAM_XCLKA) as an output GPIO
On Wed, Nov 24, 2010 at 13:52, Felipe Balbi ba...@ti.com wrote:
On Wed, Nov 24, 2010 at 10:46:04AM +0530, Varadarajan, Charulatha wrote:
diff --git a/arch/arm/plat-omap/mailbox.c b/arch/arm/plat-omap/mailbox.c
index 48e161c..a1c6bd9 100644
--- a/arch/arm/plat-omap/mailbox.c
+++
On Wed, Nov 24, 2010 at 02:20:40PM +0530, Varadarajan, Charulatha wrote:
On Wed, Nov 24, 2010 at 13:52, Felipe Balbi ba...@ti.com wrote:
On Wed, Nov 24, 2010 at 10:46:04AM +0530, Varadarajan, Charulatha wrote:
diff --git a/arch/arm/plat-omap/mailbox.c b/arch/arm/plat-omap/mailbox.c
index
(Sorry. You will see two replies from me on your email)
-Original Message-
From: Santosh Shilimkar [mailto:santosh.shilim...@ti.com]
Sent: Wednesday, November 24, 2010 11:04 AM
To: 'Kevin Hilman'
Cc: Nishanth Menon; 'linux-omap'; 'Jean Pihet'; Vishwanath Sripathy;
'Tony'
Subject:
On Tue, 2010-11-23 at 23:46 +0530, ext Hiremath, Vaibhav wrote:
Hi,
While supporting one of customer I came across one interesting issue and
finding with WAITFORVSYNC ioctl -
Problem Statement -
---
With WAITFORVSYNC lots of tearing artifacts are visible on LCD output,
Hello Mark,
On Fri, 3 Sep 2010 19:20:52 +0100
Mark Brown broo...@opensource.wolfsonmicro.com wrote:
Essentially all that needs doing is that when regulator_set_voltage() is
called instead of merging with the machine constraints and applying the
setting immediately we store the constraints
On Wed, Nov 24, 2010 at 10:45:44AM +0100, Thomas Petazzoni wrote:
I went ahead and implemented this (without looking at previous existing
code since I couldn't find it). What about the following patch ?
That's pretty much exactly what the old code did - told you it was
trivial :)
--
To
Power to the wl12xx wlan device is controlled by a fixed regulator.
Boards that have the wl12xx should select REGULATOR_FIXED_VOLTAGE so
users will not be baffled.
Signed-off-by: Ohad Ben-Cohen o...@wizery.com
---
arch/arm/mach-omap2/Kconfig |3 +++
1 files changed, 3 insertions(+), 0
-Original Message-
From: Tomi Valkeinen [mailto:tomi.valkei...@nokia.com]
Sent: Wednesday, November 24, 2010 2:28 PM
To: Hiremath, Vaibhav
Cc: linux-omap@vger.kernel.org
Subject: Re: OMAP:DSS: possible bug in WAITFOR_VSYNC ioctl
On Tue, 2010-11-23 at 23:46 +0530, ext Hiremath,
On Wed, Nov 24, 2010 at 1:23 AM, Ionut Nicu ionut.n...@mindbit.ro wrote:
At iounmap_base you unmap state-io_base, but that's set only after this
check. You should probably iounmap(io_base).
Of course. Thanks.
Regards,
Ionut.
--
To unsubscribe from this list: send the line unsubscribe
On Wed, 2010-11-24 at 15:20 +0800, Axel Lin wrote:
Return PTR_ERR(omap3pandora_dac_reg) instead of 0 if regulator_get failed.
Signed-off-by: Axel Lin axel@gmail.com
---
sound/soc/omap/omap3pandora.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git
On Wed, 2010-11-24 at 14:07 +0530, Varadarajan, Charulatha wrote:
On Wed, Nov 24, 2010 at 12:53, Axel Lin axel@gmail.com wrote:
Add Patch description.
Signed-off-by: Axel Lin axel@gmail.com
---
Please resubmit with a patch description and Jarkko's Ack.
Thanks
Liam
--
Certain errata in OMAP2+ processors will require forcing
master standby to no standby mode before completing on going
operation. Without this, the results will be unpredictable.
Since current implementation of PM run time framework does not support
changing sysconfig settings during middle of the
On Wed, Nov 24, 2010 at 03:20:48PM +0800, Axel Lin wrote:
Return PTR_ERR(omap3pandora_dac_reg) instead of 0 if regulator_get failed.
Signed-off-by: Axel Lin axel@gmail.com
Applied, thanks.
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to
On Tue, Nov 23, 2010 at 11:21 PM, Varadarajan, Charulatha ch...@ti.com wrote:
On Wed, Nov 24, 2010 at 02:56, Hari Kanigeri h-kanige...@ti.com wrote:
From: Fernando Guzman Lugo x0095...@ti.com
The variable rq_full flag is a global variable, so if there are multiple
mailbox users there will be
Patch series to convert DMA library into platform driver using platform
device model and adapting hwmod for omap2+.
The initial patches in the patch series(first 6 patches) prepares
existing DMA library for getting converted into platform driver.
steps used:
1. The low level read/write
Prepare DMA library to get converted into DMA driver using platform
device model using hwmod infrastucture for omap2+ and resource structures
for omap1.
The low level read/write macros are replaced with static inline
functions and register offsets are handled through static register
offset tables
Implement errata handling to use flags instead of cpu_is_* and
cpu_class_* in the code.
The errata flags are initialized at init time and during runtime we are
using the errata variable (via the IS_DMA_ERRATA macro) to execute the
required errata workaround.
Reused errata handling patch from:
Add OMAP2420 DMA hwmod data and also add required
DMA device attributes.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
Cc: linux-arm-ker...@lists.infradead.org
Cc: Kevin Hilman khil...@deeprootsystems.com
Cc: Tony Lindgren t...@atomide.com
Cc: Santosh Shilimkar santosh.shilim...@ti.com
Cc:
Add OMAP2430 DMA hwmod data and also add required
DMA device attributes.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
Cc: linux-arm-ker...@lists.infradead.org
Cc: Kevin Hilman khil...@deeprootsystems.com
Cc: Tony Lindgren t...@atomide.com
Cc: Santosh Shilimkar santosh.shilim...@ti.com
Cc:
Add OMAP3 DMA hwmod data
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
Cc: linux-arm-ker...@lists.infradead.org
Cc: Kevin Hilman khil...@deeprootsystems.com
Cc: Tony Lindgren t...@atomide.com
Cc: Santosh Shilimkar santosh.shilim...@ti.com
Cc: Benoit Cousson b-cous...@ti.com
---
From: Benoit Cousson b-cous...@ti.com
Add OMAP4 DMA hwmod data
Signed-off-by: Benoit Cousson b-cous...@ti.com
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
Cc: linux-arm-ker...@lists.infradead.org
Cc: Kevin Hilman khil...@deeprootsystems.com
Cc: Tony Lindgren t...@atomide.com
Cc: Santosh
Implement OMAP1 DMA as platform device and add support for
registering through platform device layer using resource
structures.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
Cc: linux-arm-ker...@lists.infradead.org
Cc: Kevin Hilman khil...@deeprootsystems.com
Cc: Tony Lindgren
Prepare OMAP2+ DMA to use hwmod infrastructure so that DMA can register
as platform device.
Signed-off-by: G, Manjunath Kondaiah manj...@ti.com
Cc: linux-arm-ker...@lists.infradead.org
Cc: Kevin Hilman khil...@deeprootsystems.com
Cc: Tony Lindgren t...@atomide.com
Cc: Santosh Shilimkar
From: Venkatraman S svenk...@ti.com
Add sDMA driver support for descriptor autoloading feature.
Descriptor autoloading is OMAP sDMA v5 hardware capability that can be
exploited for scatter gather scenarios, currently available in OMAP3630
and OMAP4430.
The feature works as described below.
1. A
DMA4 channel fails to continue with descriptor load when
pause bit is cleared through config port access while in
mstandby.
Work around: Software should configure DMA in no standby mode
or force standby before clearing the pause bit(CDPi[7]) using
mstandby mode control API's.
Applicable for all
Few errata in OMAP2+ DMA driver require forcing DMA controller
mstandby mode to 'no standby' mode. Current implementation
directly access sysconfig registers for this operation.
Since there are API's for controlling mstandby mode, cleanup
sysconfig register access and replace the same with API's.
Enable runtime pm and use pm_runtime_get_sync and pm_runtime_put
for OMAP DMA driver.
Since DMA driver callback will happen from interrupt context and
DMA client driver will release all DMA resources from interrupt
context itself, pm_runtime_put_sync() cannot be used in DMA driver.
Instead,
On Wed, Nov 24, 2010 at 2:50 AM, Varadarajan, Charulatha ch...@ti.com wrote:
On Wed, Nov 24, 2010 at 13:52, Felipe Balbi ba...@ti.com wrote:
On Wed, Nov 24, 2010 at 10:46:04AM +0530, Varadarajan, Charulatha wrote:
diff --git a/arch/arm/plat-omap/mailbox.c b/arch/arm/plat-omap/mailbox.c
index
On Wed, Nov 24, 2010 at 18:17, Kanigeri, Hari h-kanige...@ti.com wrote:
On Tue, Nov 23, 2010 at 11:21 PM, Varadarajan, Charulatha ch...@ti.com
wrote:
On Wed, Nov 24, 2010 at 02:56, Hari Kanigeri h-kanige...@ti.com wrote:
From: Fernando Guzman Lugo x0095...@ti.com
The variable rq_full flag
On Tue, Nov 23, 2010 at 11:29 PM, Varadarajan, Charulatha ch...@ti.com wrote:
On Wed, Nov 24, 2010 at 02:56, Hari Kanigeri h-kanige...@ti.com wrote:
In the current mailbox driver, the mailbox internal pointer for
callback can be directly manipulated by the Users, so a second
User can easily
On Wed, Nov 24, 2010 at 18:39, Kanigeri, Hari h-kanige...@ti.com wrote:
On Tue, Nov 23, 2010 at 11:29 PM, Varadarajan, Charulatha ch...@ti.com
wrote:
On Wed, Nov 24, 2010 at 02:56, Hari Kanigeri h-kanige...@ti.com wrote:
In the current mailbox driver, the mailbox internal pointer for
On Tue, Nov 23, 2010 at 11:26 PM, Varadarajan, Charulatha ch...@ti.com wrote:
On Wed, Nov 24, 2010 at 02:56, Hari Kanigeri h-kanige...@ti.com wrote:
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
On Wed, Nov 24, 2010 at 7:12 AM, Varadarajan, Charulatha ch...@ti.com wrote:
On Wed, Nov 24, 2010 at 18:39, Kanigeri, Hari h-kanige...@ti.com wrote:
On Tue, Nov 23, 2010 at 11:29 PM, Varadarajan, Charulatha ch...@ti.com
wrote:
On Wed, Nov 24, 2010 at 02:56, Hari Kanigeri h-kanige...@ti.com
[..snip..]
% mkfs.jffs2 --little-endian --no-cleanmarkers --pad 2048 --pagesize 2048
--eraseblock 131072 -d /tmp/tmp.h9dKGpcNFw -D root.devices -o root.jffs2
nand write.i ${loadaddr} 0x00c0 0x200
nand write.i ${loadaddr} 0x0420 0x200
[Ghorai] why you writing
In current implementation, there are resources leak in the error path.
This patch properly reclaims the allocated resources in the error path.
Also adds a missing clk_put in osk_soc_exit.
Signed-off-by: Axel Lin axel@gmail.com
Acked-by: Jarkko Nikula jhnik...@gmail.com
---
On Tue, 23 Nov 2010, Rafael J. Wysocki wrote:
Or maybe you think that when pm_runtime_put_sync detects the
usage_count has decremented to 0 and the device is irq-safe, it should
call rpm_suspend directly instead of calling rpm_idle?
That also would work for me, actually.
Okay, then
Many thanks for the help Rene, it makes a huge difference being told
whereabouts in the gigabytes of source to start looking!
You are quite correct in that the error comes from NODE_Create.
Node_Create calls DISP_NodeCreate
DISP_NodeCreate calls SendMessage
SendMessage succeeds, but after
On Wed, Nov 24, 2010 at 03:39:44PM +0530, ext Hiremath, Vaibhav wrote:
-Original Message-
From: Tomi Valkeinen [mailto:tomi.valkei...@nokia.com]
Sent: Wednesday, November 24, 2010 2:28 PM
To: Hiremath, Vaibhav
Cc: linux-omap@vger.kernel.org
Subject: Re: OMAP:DSS: possible bug
On Tue, 23 Nov 2010, Kevin Hilman wrote:
While I like the idea of the symmetry of having both _get_sync() and
_put_sync() callable from an interrupt handler, I can't currently think
of a situation where we would need to _put_sync() in the ISR. A
standard _put() should suffice for all cases I
Nishant,
On Fri, Nov 19, 2010 at 7:24 AM, Nishanth Menon n...@ti.com wrote:
From: Peter 'p2' De Schrijver peter.de-schrij...@nokia.com
Errata i581 impacts OMAP3 platforms.
PRCM DPLL control FSM removes SDRC_IDLEREQ before DPLL3 locks causing
the DPLL not to be locked at times.
IMPORTANT:
Major changes in V5:
rebased to k.org 2.6.37-rc3
introduced omap_opp_data.h
couple of whitespace and offline license suggestion cleanups
V4: http://marc.info/?l=linux-omapm=128993367112637w=2
V3: http://marc.info/?l=linux-omapm=128984926812800w=2
V2:
This patch adds OPP tables for OMAP4. New file has been added to keep
the OMAP4 opp tables and the registration of these tables with the
generic opp framework by OMAP SoC OPP interface.
Based on:
Add OPP data for OMAP34xx and OMAP36xx and initialization functions
to populate OPP tables based on current SoC.
introduce an OMAP generic opp initialization routine which OMAP3
and OMAP4+ SoCs can use to register their OPP definitions.
Cc: Thomas Petazzoni thomas.petazz...@free-electrons.com
From: Kevin Hilman khil...@deeprootsystems.com
With new OPP layer, OPP users will access OPP API directly instead of
using OMAP PM layer, so remove all notions of OPPs from the OMAP PM
layer.
Signed-off-by: Nishanth Menon n...@ti.com
Signed-off-by: Kevin Hilman khil...@deeprootsystems.com
---
Nishant,
On Wed, Nov 24, 2010 at 10:22 AM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
(Sorry. You will see two replies from me on your email)
-Original Message-
From: Santosh Shilimkar [mailto:santosh.shilim...@ti.com]
Sent: Wednesday, November 24, 2010 11:04 AM
To: 'Kevin
Jean Pihet had written, on 11/24/2010 11:11 AM, the following:
[...]
When the code is split into the pure sleep code and the secure code
parts, I would like to have the sleep code part cleaned up.
BTW I rebased my clean-up patch on top of the 13 patches you sent and
performed some testing. It is
Sripathy, Vishwanath had written, on 11/24/2010 10:51 AM, the following:
On Fri, Nov 19, 2010 at 7:24 AM, Nishanth Menon n...@ti.com wrote:
From: Peter 'p2' De Schrijver peter.de-schrij...@nokia.com
Errata i581 impacts OMAP3 platforms.
PRCM DPLL control FSM removes SDRC_IDLEREQ before DPLL3
Alan Stern st...@rowland.harvard.edu writes:
On Tue, 23 Nov 2010, Kevin Hilman wrote:
While I like the idea of the symmetry of having both _get_sync() and
_put_sync() callable from an interrupt handler, I can't currently think
of a situation where we would need to _put_sync() in the ISR. A
Add additional check to omap_uart_resume_idle() so that only
enabled (specfically, idle-enabled) UARTs are allowed to resume.
This matches the existing check in prepare idle.
Cc: Govindraj R. govindraj.r...@ti.com
Signed-off-by: Kevin Hilman khil...@deeprootsystems.com
---
Unless there are any
Hi James,
It seems that this question is more intended to the TI SN team, anyway
I have taken a look at the mail chain and from your conclusions below
seems that you are facing memory allocation issues. I think it is
probably you are getting a SYS_EALLOC coming in from the call to
Hi Mugdha,
On Wed, Nov 24, 2010 at 9:44 AM, Kamoolkar, Mugdha mug...@ti.com wrote:
How do multiple clients get a handle that they can use? Are they expected to
share the handle they get from the call above?
Currently, yes.
What if they are independent
clients with no means of communication
On Wednesday, November 24, 2010, Alan Stern wrote:
On Tue, 23 Nov 2010, Rafael J. Wysocki wrote:
Or maybe you think that when pm_runtime_put_sync detects the
usage_count has decremented to 0 and the device is irq-safe, it should
call rpm_suspend directly instead of calling rpm_idle?
Hi,
On Wed, 2010-11-24 at 11:09 -0800, Kevin Hilman wrote:
Add additional check to omap_uart_resume_idle() so that only
enabled (specfically, idle-enabled) UARTs are allowed to resume.
typo: specifically
--
balbi
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the
Hi Charu,
On 11/23/2010 3:56 PM, Varadarajan, Charulatha wrote:
Implement OMAP GPIO module in platform device model. OMAP2+ specific GPIO
module uses hwmod FW.
Tested on OMAP2430, OMAP44430, OMAP3430 SDP boards, OMAP4430 Blaze board
How did you get some top secret samples of the ultra new
On 11/23/2010 3:56 PM, Varadarajan, Charulatha wrote:
Add GPIO hwmod data for OMAP2420
Signed-off-by: Charulatha Vch...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_2420_data.c | 229
arch/arm/plat-omap/include/plat/gpio.h |5 +
2 files changed, 234
As request by Grant Likely, there is no more cover letter. Full changelog is
following.
I am still reluctant to add this changelog in the patch description, as it adds
no value to
the patch itself: when it was needed I try to updat comments or patch
description.
I understand that Grant Likely
I am trying to write a device driver to stream data via a McBSP
module. Most of it is a pretty thin layer, thanks to all the
framework in plat-omap/mcbsp.c and .../mcbsp.h. However, I am getting
stuck on the read() and write() implementation -- in particular,
retrieving the device pointer for
* Felipe Balbi m...@felipebalbi.com [101124 12:39]:
Hi,
On Wed, 2010-11-24 at 11:09 -0800, Kevin Hilman wrote:
Add additional check to omap_uart_resume_idle() so that only
enabled (specfically, idle-enabled) UARTs are allowed to resume.
typo: specifically
Also, without this patch,
On 11/23/2010 3:56 PM, Varadarajan, Charulatha wrote:
Add GPIO hwmod data for OMAP2430
Signed-off-by: Charulatha Vch...@ti.com
Acked-by: Benoit Cousson b-cous...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_2430_data.c | 279
1 files changed, 279 insertions(+),
On 11/23/2010 3:56 PM, Varadarajan, Charulatha wrote:
Add GPIO hwmod data for OMAP3
Signed-off-by: Charulatha Vch...@ti.com
Signed-off-by: Rajendra Nayakrna...@ti.com
Acked-by: Benoit Cousson b-cous...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 360
On 11/23/2010 3:56 PM, Varadarajan, Charulatha wrote:
Use omap_device_build() API to do platform_device_register of
GPIO devices. For OMAP2+ chips, the device specific data defined
in the centralized hwmod database will be used.
gpio_init needs to be done before machine_init functions access
* Varadarajan, Charulatha ch...@ti.com [101123 06:47]:
Remove the usage of omap_gpio_init() from all omap board files
since omap_gpio_init() does nothing, after gpio is implemented
as a platform device.
Great, glad to see these go!
Tony
--
To unsubscribe from this list: send the line
* Jarkko Nikula jhnik...@gmail.com [101122 23:16]:
On Mon, 22 Nov 2010 17:48:24 -0700 (MST)
Paul Walmsley p...@pwsan.com wrote:
Signed-off-by: Janusz Krzysztofik jkrzy...@tis.icnet.pl
Thanks for fixing this. What do you think about the following patch
instead? It should avoid any
* Aaro Koskinen aaro.koski...@nokia.com [101118 09:50]:
Some small OMAP cleanups to eliminate noise from compilation/sparse
checks:
Thanks, will queue these for 2.6.38 merge window.
Regards,
Tony
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message
Paul Walmsley p...@pwsan.com writes:
The console semaphore must be held while the OMAP UART devices are
disabled, lest a console write cause an ARM abort (and a kernel crash)
when the underlying console device is inaccessible. These crashes
only occur when the console is on one of the OMAP
Gregory CLEMENT gregory.clem...@free-electrons.com writes:
As request by Grant Likely, there is no more cover letter. Full changelog is
following.
I am still reluctant to add this changelog in the patch description, as it
adds no value to
the patch itself: when it was needed I try to updat
* Kevin Hilman khil...@deeprootsystems.com [101124 16:32]:
Paul Walmsley p...@pwsan.com writes:
snip
Acked-by: Kevin Hilman khil...@deeprootsystems.com
Very nice. I've been exploring various solutions to this problem as
well, but this one is much cleaner. Also, I hadn't discovered the
Varadarajan, Charulatha ch...@ti.com writes:
Implement OMAP GPIO module in platform device model. OMAP2+ specific GPIO
module uses hwmod FW.
Tested on OMAP2430, OMAP44430, OMAP3430 SDP boards, OMAP4430 Blaze board
and zoom3 board. Verified that this patch series does not break the OMAP1
On Wed, 24 Nov 2010, Nishanth Menon wrote:
From: Kevin Hilman khil...@deeprootsystems.com
With new OPP layer, OPP users will access OPP API directly instead of
using OMAP PM layer, so remove all notions of OPPs from the OMAP PM
layer.
Signed-off-by: Nishanth Menon n...@ti.com
The pointer will later be used to register/unregister media entities
when registering/unregistering a v4l2_subdev or a video_device.
With the introduction of media devices, device drivers need to store a
pointer to a driver-specific structure in the device's drvdata.
v4l2_device can't claim
V4L2 devices are media entities. As such they need to inherit from
(include) the media_entity structure.
When registering/unregistering the device, the media entity is
automatically registered/unregistered. The entity is acquired on device
open and released on device close.
Signed-off-by:
The media_devnode structure provides support for registering and
unregistering character devices using a dynamic major number. Reference
counting is handled internally, making device drivers easier to write
without having to solve the open/disconnect race condition issue over
and over again.
The
Hi everybody,
Here is the sixth version of the media controller core and V4L2 patches, and
the first one to be sent outside of the linux-media mailing list.
For those who haven't heard about the media controller yet, let me quote the
documentation
Create the following ioctl and implement it at the media device level to
query device information.
- MEDIA_IOC_DEVICE_INFO: Query media device information
The ioctl and its data structure are defined in the new kernel header
linux/media.h available to userspace applications.
Signed-off-by:
The media_device structure abstracts functions common to all kind of
media devices (v4l2, dvb, alsa, ...). It manages media entities and
offers a userspace API to discover and configure the media device
internal topology.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
---
Link states must not be modified while streaming is in progress on a
graph they belong or connect to. The entity locking API helps drivers
enforcing that requirement.
When starting streaming on a graph, drivers lock all entities in the
graph with a call to media_entity_graph_lock(). Similarly,
Create the following two ioctls and implement them at the media device
level to enumerate entities, pads and links.
- MEDIA_IOC_ENUM_ENTITIES: Enumerate entities and their properties
- MEDIA_IOC_ENUM_LINKS: Enumerate all pads and links for a given entity
Entity IDs can be non-contiguous.
Create the following ioctl and implement it at the media device level to
setup links.
- MEDIA_IOC_SETUP_LINK: Modify the properties of a given link
The only property that can currently be modified is the ACTIVE link flag
to activate/deactivate a link. Links marked with the IMMUTABLE link flag
From: Sakari Ailus sakari.ai...@maxwell.research.nokia.com
Add media entity graph traversal. The traversal follows active links by
depth first. Traversing graph backwards is prevented by comparing the next
possible entity in the graph with the previous one. Multiply connected
graphs are thus not
From: Sakari Ailus sakari.ai...@maxwell.research.nokia.com
Basically these are the interface functions:
media_entity_get() - acquire entity
media_entity_put() - release entity
If the entity is of node type, the power change is distributed to
all connected entities. For non-nodes
As video hardware pipelines become increasingly complex and
configurable, the current hardware description through v4l2 subdevices
reaches its limits. In addition to enumerating and configuring
subdevices, video camera drivers need a way to discover and modify at
runtime how those subdevices are
V4L2 subdevices are media entities. As such they need to inherit from
(include) the media_entity structure.
When registering/unregistering the subdevice, the media entity is
automatically registered/unregistered. The entity is acquired on device
open and released on device close.
Signed-off-by:
Hi everybody,
Here's the third version of the OMAP3 ISP driver patches (and the first one to
be posted to linux-omap), updated to 2.6.37-rc3 and the latest changes in the
media controller and sub-device APIs. The patches have been posted to the
linux-media mailing list minutes ago and I managed
Instead of returning an error when receiving an ioctl call with an
unsupported command, forward the call to the subdev core::ioctl handler.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
---
Documentation/video4linux/v4l2-framework.txt |5 +
Some buggy sensors generate corrupt frames when the stream is started.
This new operation return the number of corrupt frames to skip when
starting the stream.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
---
include/media/v4l2-subdev.h |4
1 files changed, 4
The later makes extensive use of structures defined in the former.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
---
include/media/v4l2-ctrls.h |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/include/media/v4l2-ctrls.h b/include/media/v4l2-ctrls.h
From: Tuukka Toivonen tuukka.o.toivo...@nokia.com
Add new/changed base address definitions and resources for
OMAP3630 ISP.
The OMAP3430 CSI2PHY block is same as the OMAP3630 CSIPHY2
block. But the later name is chosen as it gives more symmetry
to the names.
Signed-off-by: Tuukka Toivonen
From: Stanimir Varbanov svarba...@mm-sol.com
The omap3isp platform device requires platform data. As the data can be
provided by a kernel module, the device can't be registered during arch
initialization.
Remove the omap3isp platform device registration from
omap_init_camera(), and export the
--- On Wed, 11/24/10, Kevin Hilman khil...@deeprootsystems.com wrote:
I'm not SPI-aware enough to ack
this patch or
test it thoroughly.
Heh, my excuse is usually not enough time
or sometimes no test setup ... ;)
In this case I can at least ack the fix in
principle. CS active means an
My rule of thumb is that nothing is generic
until at least three whatever-it-is instances
plug in to it. Sometimes this is called
the Rule of Three.
Other than OMAP, what's providing hardware
spinlocks that plug into this framework?
- Dave
--
To unsubscribe from this list: send the line
On Thu, Nov 25, 2010 at 02:28, Cousson, Benoit b-cous...@ti.com wrote:
Hi Charu,
On 11/23/2010 3:56 PM, Varadarajan, Charulatha wrote:
Implement OMAP GPIO module in platform device model. OMAP2+ specific GPIO
module uses hwmod FW.
Tested on OMAP2430, OMAP44430, OMAP3430 SDP boards,
Kevin,
On Thu, Nov 25, 2010 at 07:10, Kevin Hilman khil...@deeprootsystems.com wrote:
Varadarajan, Charulatha ch...@ti.com writes:
Implement OMAP GPIO module in platform device model. OMAP2+ specific GPIO
module uses hwmod FW.
Tested on OMAP2430, OMAP44430, OMAP3430 SDP boards, OMAP4430
Benoit,
On Thu, Nov 25, 2010 at 03:43, Cousson, Benoit b-cous...@ti.com wrote:
On 11/23/2010 3:56 PM, Varadarajan, Charulatha wrote:
Add GPIO hwmod data for OMAP2420
Signed-off-by: Charulatha Vch...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_2420_data.c | 229
Benoit,
On Thu, Nov 25, 2010 at 04:21, Cousson, Benoit b-cous...@ti.com wrote:
On 11/23/2010 3:56 PM, Varadarajan, Charulatha wrote:
Add GPIO hwmod data for OMAP3
Signed-off-by: Charulatha Vch...@ti.com
Signed-off-by: Rajendra Nayakrna...@ti.com
Acked-by: Benoit Cousson b-cous...@ti.com
Ohad,
-Original Message-
From: Ohad Ben-Cohen [mailto:o...@wizery.com]
Sent: Thursday, November 25, 2010 1:29 AM
To: Kamoolkar, Mugdha
Cc: linux-omap@vger.kernel.org; linux-ker...@vger.kernel.org; linux-arm-
ker...@lists.infradead.org; a...@linux-foundation.org; Greg KH; Tony
1 - 100 of 110 matches
Mail list logo
