Hi,
On Mon, Nov 12, 2012 at 12:38:37AM +0200, Constantine Shulyupin wrote:
What is architecture and the best strategy to port board initialization to
fdt?
Let's see for example omap4_ehci_init and usbhs_bdata @
arch/arm/mach-omap2/board-omap4panda.c.
before getting rid of platform_data,
On Tue, Nov 06, 2012 at 22:26:54, Cousson, Benoit wrote:
Hi Anil,
On 11/06/2012 06:07 AM, AnilKumar, Chimata wrote:
On Mon, Nov 05, 2012 at 22:13:25, Cousson, Benoit wrote:
Hi Anil / Colin,
On 11/05/2012 10:42 AM, AnilKumar Ch wrote:
From: Colin Foe-Parker colin.foepar...@logicpd.com
On Tue, Nov 06, 2012 at 11:15:34, Bedia, Vaibhav wrote:
On Mon, Nov 05, 2012 at 15:12:27, AnilKumar, Chimata wrote:
[...]
+#define SHUTDOWN_TIME_SEC 2
+#define SECS_IN_MIN60
+#define WAIT_AFTER (SECS_IN_MIN - SHUTDOWN_TIME_SEC)
Hi Linus,
On Nov 11, 2012, at 7:26 PM, Linus Walleij wrote:
On Fri, Nov 9, 2012 at 9:06 AM, Thierry Reding
thierry.red...@avionic-design.de wrote:
On Wed, Oct 31, 2012 at 05:57:27PM +0200, Pantelis Antoniou wrote:
+ pinctrl = devm_pinctrl_get_select_default(pdev-dev);
+ if
Hi,
This series changes omapfb to use standard dma_alloc funcs instead of omap
specific vram allocator. This let's us remove the omap vram allocator, making
omapfb platform independent.
However, note that using standard dma funcs causes the following downsides:
1) dma_alloc_attrs doesn't let us
Use DMA_BIT_MASK() for fb's coherent_dma_mask for clarity.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/plat-omap/fb.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/arch/arm/plat-omap/fb.c b/arch/arm/plat-omap/fb.c
index bcbb9d5..218963b 100644
Use dma_alloc_attrs to allocate memory instead of omap specific vram
allocator. After this we can remove the omap vram allocator.
There are some downsides to this change:
1) dma_alloc_attrs doesn't let us allocate at certain physical address.
However, this should not be a problem as this feature
As omapfb no longer uses omap specific vram allocator we can remove the
vram pre-allocation from rx51 board file.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/mach-omap2/board-rx51-video.c | 14 --
arch/arm/mach-omap2/board-rx51.c |3 ---
2 files
OMAP specific vram allocator is no longer used, and we can remove init
call to the vram allocator.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/plat-omap/common.c |2 --
1 file changed, 2 deletions(-)
diff --git a/arch/arm/plat-omap/common.c b/arch/arm/plat-omap/common.c
OMAP specific vram allocator is no longer in use, and we can remove all
the vram code.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/plat-omap/include/plat/vram.h | 43 ---
drivers/video/omap2/Kconfig|3 -
drivers/video/omap2/Makefile |1 -
On Fri, Nov 09, 2012 at 00:46:28, Hunter, Jon wrote:
On 11/08/2012 12:59 PM, Hiremath, Vaibhav wrote:
On Fri, Nov 09, 2012 at 00:24:23, Hunter, Jon wrote:
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
[snip]
There is no reliable way to determine which source should be used in
On Mon, Nov 12, 2012 at 12:54:59, Igor Grinberg wrote:
On 11/12/12 08:38, Hiremath, Vaibhav wrote:
On Sun, Nov 11, 2012 at 17:05:07, Igor Grinberg wrote:
On 11/08/12 20:34, Jon Hunter wrote:
On 11/08/2012 12:17 PM, Paul Walmsley wrote:
On Thu, 8 Nov 2012, Jon Hunter wrote:
On
On Fri, Nov 09, 2012 at 09:17:33PM +, Rob Clark wrote:
From: Rob Clark r...@ti.com
A new atomic modeset/pageflip ioctl being developed in DRM requires
get_user() to work for 64bit types (in addition to just put_user()).
Signed-off-by: Rob Clark r...@ti.com
---
Hi Tony,
After rebasing on top of your omap-for-v3.8/tmp-merge, I realized that this
patch is generating a build break due to removal of the fpga.h include from
debug-leds.c.
arch/arm/plat-omap/debug-leds.c: In function 'fpga_probe':
arch/arm/plat-omap/debug-leds.c:114:9: error:
Op 10 nov. 2012, om 00:40 heeft Grant Likely grant.lik...@secretlab.ca het
volgende geschreven:
On Fri, Nov 9, 2012 at 11:23 PM, Stephen Warren swar...@wwwdotorg.org wrote:
On 11/09/2012 09:28 AM, Grant Likely wrote:
On Tue, Nov 6, 2012 at 10:37 PM, Stephen Warren swar...@wwwdotorg.org
Hi Vaibhav,
On 11/12/2012 11:38 AM, Hiremath, Vaibhav wrote:
On Fri, Nov 09, 2012 at 00:46:28, Hunter, Jon wrote:
On 11/08/2012 12:59 PM, Hiremath, Vaibhav wrote:
On Fri, Nov 09, 2012 at 00:24:23, Hunter, Jon wrote:
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
[snip]
There is no
Op 5 nov. 2012, om 21:40 heeft Grant Likely grant.lik...@secretlab.ca het
volgende geschreven:
Hey folks,
As promised, here is my early draft to try and capture what device
tree overlays need to do and how to get there. Comments and
suggestions greatly appreciated.
Device Tree Overlay
Hi Grant,
Sorry for the late comments, travelling...
On Nov 9, 2012, at 6:28 PM, Grant Likely wrote:
On Tue, Nov 6, 2012 at 10:37 PM, Stephen Warren swar...@wwwdotorg.org wrote:
On 11/05/2012 01:40 PM, Grant Likely wrote:
Hey folks,
As promised, here is my early draft to try and capture
Hi Grant,
On Nov 9, 2012, at 7:02 PM, Grant Likely wrote:
On Wed, Nov 7, 2012 at 12:54 AM, Mitch Bradley w...@firmworks.com wrote:
On 11/6/2012 12:37 PM, Stephen Warren wrote:
This proposal is very oriented at an overlay-based approach. I'm not
totally convinced that a pure overlay approach
Hi Grant,
On Nov 9, 2012, at 10:33 PM, Grant Likely wrote:
On Wed, Nov 7, 2012 at 11:02 AM, Pantelis Antoniou
pa...@antoniou-consulting.com wrote:
On Nov 7, 2012, at 11:19 AM, Benoit Cousson wrote:
Maybe some extra version match table can just be passed during the board
machine_init
Hi Grant,
On Nov 9, 2012, at 11:22 PM, Grant Likely wrote:
On Fri, Nov 9, 2012 at 5:32 AM, Joel A Fernandes agnel.j...@gmail.com wrote:
Hi Pantelis,
I hope I'm not too late to reply as I'm traveling.
On Nov 6, 2012, at 5:30 AM, Pantelis Antoniou
pa...@antoniou-consulting.com wrote:
On 2012-11-07 08:15, Archit Taneja wrote:
Some issues were found in the DISPC driver when performing scaling with
writeback pipeline. This series fixes those issues.
Reference tree:
git://gitorious.org/~boddob/linux-omap-dss2/archit-dss2-clone.git
3.8/writeback_fixes_dispc
Archit Taneja
On 2012-11-07 11:17, Archit Taneja wrote:
This series resolves a few minor issues with APPLY. Tested on a 4430sdp,
checked
switching overlays between DSI command mode and HDMI displays for any
unexpected
behavior.
Reference tree:
Hi Stephen,
On Nov 10, 2012, at 12:57 AM, Stephen Warren wrote:
On 11/08/2012 07:26 PM, David Gibson wrote:
...
I also think graft will handle most of your use cases, although as I
said I don't fully understand the implications of some of them, so I
could be wrong. So, the actual insertion
Hi Stephen,
On Nov 10, 2012, at 1:23 AM, Stephen Warren wrote:
On 11/09/2012 09:28 AM, Grant Likely wrote:
On Tue, Nov 6, 2012 at 10:37 PM, Stephen Warren swar...@wwwdotorg.org
wrote:
...
I do rather suspect this use-case is quite common. NVIDIA certainly has
a bunch of development boards
Hi Joel,
Again, sorry for the late reply due to travel.
On Nov 10, 2012, at 5:36 AM, Joel A Fernandes wrote:
Hi Pantelis,
On Fri, Nov 9, 2012 at 2:13 AM, Pantelis Antoniou
pa...@antoniou-consulting.com wrote:
Option C: U-Boot loads both the base and overlay FDT files, merges them,
Hi Rob.
On Nov 11, 2012, at 10:47 PM, Rob Landley wrote:
On 11/09/2012 10:28:59 AM, Grant Likely wrote:
On Tue, Nov 6, 2012 at 10:37 PM, Stephen Warren swar...@wwwdotorg.org
wrote:
On 11/05/2012 01:40 PM, Grant Likely wrote:
I'm not actually opposed to it, but it needs to be
On Mon, Nov 12, 2012 at 11:34 AM, Pantelis Antoniou
pa...@antoniou-consulting.com wrote:
Hi Grant,
On Nov 9, 2012, at 10:33 PM, Grant Likely wrote:
On Wed, Nov 7, 2012 at 11:02 AM, Pantelis Antoniou
pa...@antoniou-consulting.com wrote:
On Nov 7, 2012, at 11:19 AM, Benoit Cousson wrote:
commit ae4bf788ee9bf7c2d51b0309117d1fcccbdd50a2
mmc: omap_hsmmc: consolidate error report handling of HSMMC IRQ
sets both end_cmd and end_trans to 1.
Setting end_cmd to 1 for Data Timeout/CRC leads to NULL pointer dereference of
host-cmd as the command complete has previously been handled.
Set
update error code to cmd-error for commands with response_busy and no data
Signed-off-by: Balaji T K balaj...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
---
drivers/mmc/host/omap_hsmmc.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/drivers/mmc/host/omap_hsmmc.c
Balaji T K (3):
mmc: omap_hsmmc: Fix Oops in case of data errors
mmc: omap_hsmmc: no reset of cmd state machine for DCRC
mmc: omap_hsmmc: update error code for response_busy cmd
drivers/mmc/host/omap_hsmmc.c | 23 +++
1 files changed, 15 insertions(+), 8 deletions(-)
Avoid soft reset of command internal state machine on data errors.
Signed-off-by: Balaji T K balaj...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
---
drivers/mmc/host/omap_hsmmc.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/mmc/host/omap_hsmmc.c
On Friday 09 November 2012 11:55 PM, Tony Lindgren wrote:
When booting with device tree, we don't have any pdata, and will
get the following when trying to unload omap_hsmmc:
Unable to handle kernel NULL pointer dereference at virtual address 0044
pgd = edafc000
*pgd=adbbd831,
Hi,
This patch removes use of cpu_is_* funcs from omap_vout, and uses omapdss's
version instead. The other patch removes an unneeded plat/dma.h include.
These are based on current omapdss master branch, which has the omapdss version
code. The omapdss version code is queued for v3.8. I'm not sure
cpu_is_* class functions create a dependency to OMAP platform code.
omapdss driver, which omap_vout uses, exposes a function to get the
version of the DSS hardware.
To remove the dependency to OMAP platform code this patch changes
omap_vout to use the omapdss version. For most of the checks, the
Remove including plat/dma.h which is not needed.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/media/platform/omap/omap_vout.c |1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/media/platform/omap/omap_vout.c
b/drivers/media/platform/omap/omap_vout.c
index
Hi,
On Mon, Nov 12, 2012 at 12:25 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
This series changes omapfb to use standard dma_alloc funcs instead of omap
specific vram allocator. This let's us remove the omap vram allocator, making
omapfb platform independent.
However, note that using
On Mon, Nov 12, 2012 at 4:46 AM, Will Deacon will.dea...@arm.com wrote:
On Fri, Nov 09, 2012 at 09:17:33PM +, Rob Clark wrote:
From: Rob Clark r...@ti.com
A new atomic modeset/pageflip ioctl being developed in DRM requires
get_user() to work for 64bit types (in addition to just
On 2012-11-12 15:39, Grazvydas Ignotas wrote:
Hi,
On Mon, Nov 12, 2012 at 12:25 PM, Tomi Valkeinen tomi.valkei...@ti.com
wrote:
This series changes omapfb to use standard dma_alloc funcs instead of omap
specific vram allocator. This let's us remove the omap vram allocator, making
omapfb
On 2012-11-12 15:39, Grazvydas Ignotas wrote:
Hi,
On Mon, Nov 12, 2012 at 12:25 PM, Tomi Valkeinen tomi.valkei...@ti.com
wrote:
This series changes omapfb to use standard dma_alloc funcs instead of omap
specific vram allocator. This let's us remove the omap vram allocator, making
omapfb
On Mon, Nov 12, 2012 at 01:46:57PM +, Rob Clark wrote:
On Mon, Nov 12, 2012 at 4:46 AM, Will Deacon will.dea...@arm.com wrote:
On Fri, Nov 09, 2012 at 09:17:33PM +, Rob Clark wrote:
@@ -122,22 +124,35 @@ extern int __get_user_4(void *);
({
On Mon, Nov 12, 2012 at 8:38 AM, Will Deacon will.dea...@arm.com wrote:
On Mon, Nov 12, 2012 at 01:46:57PM +, Rob Clark wrote:
On Mon, Nov 12, 2012 at 4:46 AM, Will Deacon will.dea...@arm.com wrote:
On Fri, Nov 09, 2012 at 09:17:33PM +, Rob Clark wrote:
@@ -122,22 +124,35 @@ extern
Fixes the following error:
CC arch/arm/mach-omap2/cm_common.o
arch/arm/mach-omap2/cm_common.c: In function ‘cm_register’:
arch/arm/mach-omap2/cm_common.c:42:11: error: ‘EINVAL’ undeclared (first use in
this function)
arch/arm/mach-omap2/cm_common.c:42:11: note: each undeclared identifier
On Friday 09 November 2012, Tony Lindgren wrote:
This series fixes an annoying regression to make MUSB working
on omap4 again. Although it's getting rather late for these
changes for the -rc cycle, it is important as many devices
are using MUSB for charging and connectivity.
With the USB
Hi
On Mon, 12 Nov 2012, Peter Ujfalusi wrote:
Fixes the following error:
CC arch/arm/mach-omap2/cm_common.o
arch/arm/mach-omap2/cm_common.c: In function ‘cm_register’:
arch/arm/mach-omap2/cm_common.c:42:11: error: ‘EINVAL’ undeclared (first use
in this function)
On 11/09/2012 09:28 AM, Grant Likely wrote:
On Tue, Nov 6, 2012 at 10:37 PM, Stephen Warren swar...@wwwdotorg.org wrote:
On 11/05/2012 01:40 PM, Grant Likely wrote:
Hey folks,
As promised, here is my early draft to try and capture what device
tree overlays need to do and how to get there.
On 11/12/2012 04:23 AM, Pantelis Antoniou wrote:
Hi Grant,
Sorry for the late comments, travelling...
On Nov 9, 2012, at 6:28 PM, Grant Likely wrote:
...
*with the caveat that not all types of changes are a good idea and we
may disallow. For example, is changing properties in existing
On 11/12/2012 05:10 AM, Pantelis Antoniou wrote:
Hi Stephen,
On Nov 10, 2012, at 1:23 AM, Stephen Warren wrote:
On 11/09/2012 09:28 AM, Grant Likely wrote:
On Tue, Nov 6, 2012 at 10:37 PM, Stephen Warren swar...@wwwdotorg.org
wrote:
...
I do rather suspect this use-case is quite
On 11/12/2012 05:50 AM, Pantelis Antoniou wrote:
Hi Rob.
On Nov 11, 2012, at 10:47 PM, Rob Landley wrote:
On 11/09/2012 10:28:59 AM, Grant Likely wrote:
On Tue, Nov 6, 2012 at 10:37 PM, Stephen Warren swar...@wwwdotorg.org
wrote:
On 11/05/2012 01:40 PM, Grant Likely wrote:
Hi Stephen,
On Nov 12, 2012, at 6:49 PM, Stephen Warren wrote:
On 11/12/2012 04:23 AM, Pantelis Antoniou wrote:
Hi Grant,
Sorry for the late comments, travelling...
On Nov 9, 2012, at 6:28 PM, Grant Likely wrote:
...
*with the caveat that not all types of changes are a good idea and we
On 11/12/2012 10:00 AM, Pantelis Antoniou wrote:
Hi Stephen,
On Nov 12, 2012, at 6:49 PM, Stephen Warren wrote:
On 11/12/2012 04:23 AM, Pantelis Antoniou wrote:
Hi Grant,
Sorry for the late comments, travelling...
On Nov 9, 2012, at 6:28 PM, Grant Likely wrote:
...
*with the caveat
Hi Stephen,
On Nov 12, 2012, at 7:10 PM, Stephen Warren wrote:
On 11/12/2012 10:00 AM, Pantelis Antoniou wrote:
Hi Stephen,
On Nov 12, 2012, at 6:49 PM, Stephen Warren wrote:
On 11/12/2012 04:23 AM, Pantelis Antoniou wrote:
Hi Grant,
Sorry for the late comments, travelling...
On
On 11/12/2012 10:19 AM, Pantelis Antoniou wrote:
Hi Stephen,
On Nov 12, 2012, at 7:10 PM, Stephen Warren wrote:
On 11/12/2012 10:00 AM, Pantelis Antoniou wrote:
Hi Stephen,
On Nov 12, 2012, at 6:49 PM, Stephen Warren wrote:
On 11/12/2012 04:23 AM, Pantelis Antoniou wrote:
Hi Grant,
* Tomi Valkeinen tomi.valkei...@ti.com [121112 05:35]:
Hi,
This patch removes use of cpu_is_* funcs from omap_vout, and uses omapdss's
version instead. The other patch removes an unneeded plat/dma.h include.
These are based on current omapdss master branch, which has the omapdss
version
Hi Stephen,
On Nov 12, 2012, at 7:29 PM, Stephen Warren wrote:
On 11/12/2012 10:19 AM, Pantelis Antoniou wrote:
Hi Stephen,
On Nov 12, 2012, at 7:10 PM, Stephen Warren wrote:
On 11/12/2012 10:00 AM, Pantelis Antoniou wrote:
Hi Stephen,
On Nov 12, 2012, at 6:49 PM, Stephen Warren
* Paul Walmsley p...@pwsan.com [121112 08:27]:
Hi
On Mon, 12 Nov 2012, Peter Ujfalusi wrote:
Fixes the following error:
CC arch/arm/mach-omap2/cm_common.o
arch/arm/mach-omap2/cm_common.c: In function ‘cm_register’:
arch/arm/mach-omap2/cm_common.c:42:11: error: ‘EINVAL’
This series includes several fixes for the OMAP DMTIMER driver. This is
based upon Tony Lindgren's current master branch [1].
Tested on OMAP5912 OSK, OMAP2420 H4, OMAP3430 Beagle and OMAP4430 Panda.
Testing includes ...
1. Booting kernel on above boards
2. Set date and ensuring time of day is
Errata Titles:
i103: Delay needed to read some GP timer, WD timer and sync timer
registers after wakeup (OMAP3/4)
i767: Delay needed to read some GP timer registers after wakeup (OMAP5)
Description (i103/i767):
If a General Purpose Timer (GPTimer) is in posted mode
(TSICR [2].POSTED=1), due
For OMAP2+ devices, when using DMTIMERs for system timers (clock-events and
clock-source) the posted mode configuration of the timers is used. To allow
the compiler to optimise the functions for configuring and reading the system
timers, the posted flag variable is hard-coded with the value 1. To
Currently the dmtimer posted mode is being enabled when the function
omap_dm_timer_enable_posted() is called. This function is only being called
for OMAP1 timers and OMAP2+ timers that are being used as system timers. Hence,
for OMAP2+ timers that are NOT being used as a system timer, posted mode
Currently, the OMAP3 HWMOD data defines two TIOCP_CFG register structures
(referred to as the SYSC register in the HWMOD data) where timers 1, 2 and 10
use one of the defintions and the other timers use the other definition. For
OMAP3 devices the structure of the DMTIMER TIOCP_CFG register is the
For OMAP2/3 devices, the HWMOD data does not define a software reset status
field for the DMTIMERs. Therefore, when HWMOD performs a soft-reset of the
DMTIMER we don't check and wait for the reset to complete. For OMAP2/3 devices,
the software reset status for a DMTIMER can be read from bit 0 of
The timer TISTAT register is a read-only register and therefore restoring the
context is not needed. Furthermore, the context of TISTAT is never saved
anywhere in the current code. The TISTAT register is read-only for all OMAP
devices from OMAP1 to OMAP4. OMAP5 timers no longer have this register.
Currently OMAP2+ devices are using the function __omap_dm_timer_reset() to
configure the clock-activity, idle, wakeup-enable and auto-idle fields in the
timer OCP_CFG register. The name of the function is mis-leading because this
function does not actually perform a reset of the timer.
For OMAP2+
Restoring the timer interrupt status is not possible because writing a 1 to any
bit in the register clears that bit if set and writing a 0 has no affect.
Furthermore, if an interrupt is pending when someone attempts to disable a
timer, the timer will fail to transition to the idle state and hence
The __omap_dm_timer_set_source() function is only used by the system timer
(clock-events and clock-source) code for OMAP2+ devices. Therefore, we can
remove this code from the dmtimer driver and move it to the system timer
code for OMAP2+ devices.
The current __omap_dm_timer_set_source() function
The OMAP dmtimer driver does not currently have a function to disable the
timer interrupts. For some timer instances the timer interrupt enable
function can be used to disable the interrupts because the same interrupt
enable register is used to disable interrupts. However, some timer instances
In commit e32f7ec2 (ARM: OMAP: Fix 32 kHz timer and modify GP timer to use GPT1)
a fix was added to prevent timer1 being reset in the function
omap_dm_timer_reset() because timer1 was being used as the system timer for
OMAP2 devices. Although timer1 is still used by most OMAP2+ devices as a system
The OMAP DMTIMERs can generate an interrupt when the timer counter value
matches the value stored in the timer's match register. When using this
feature spurious interrupts were seen, because the compare logic is being
enabled before the match value is loaded and according to the documentation
the
Whenever we call the function omap_dm_timer_set_source() to set the clock
source of a dmtimer we look-up the dmtimer functional clock source by
calling clk_get(). This is not necessary because on requesting a dmtimer
we look-up the functional clock source and store it in the omap_dm_timer
Hi,
On 11 November 2012 03:39, Ohad Ben-Cohen o...@wizery.com wrote:
On Fri, Nov 2, 2012 at 9:23 PM, Tony Lindgren t...@atomide.com wrote:
We need to move the iommu code to live under drivers
for arm common zImage support.
For the iommu changes in the entire series:
Acked-by: Ohad
It's not needed to manually reset the driver data.
Signed-off-by: Aaro Koskinen aaro.koski...@iki.fi
Cc: Wim Van Sebroeck w...@iguana.be
---
drivers/watchdog/omap_wdt.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/drivers/watchdog/omap_wdt.c
Use devm_request_mem_region() to simplify the code.
Signed-off-by: Aaro Koskinen aaro.koski...@iki.fi
Cc: Wim Van Sebroeck w...@iguana.be
---
drivers/watchdog/omap_wdt.c | 13 -
1 files changed, 4 insertions(+), 9 deletions(-)
diff --git a/drivers/watchdog/omap_wdt.c
Use devm_kzalloc() to simplify the code.
Signed-off-by: Aaro Koskinen aaro.koski...@iki.fi
Cc: Wim Van Sebroeck w...@iguana.be
---
drivers/watchdog/omap_wdt.c | 23 ++-
1 files changed, 6 insertions(+), 17 deletions(-)
diff --git a/drivers/watchdog/omap_wdt.c
Convert omap_wdt to new watchdog core. On OMAP boards, there are usually
multiple watchdogs. Since the new watchdog core supports multiple
watchdogs, all watchdog drivers used on OMAP should be converted.
The legacy watchdog device node is still created, so this should not
break existing users.
Hello,
This is a third version of the patch to convert omap_wdt to new watchdog
core. On OMAP boards, there are usually multiple watchdogs. Since the new
watchdog core supports multiple watchdogs, all watchdog drivers used on
OMAP should be converted. This is especially important on devices like
Use devm_ioremap() to simplify the code.
Signed-off-by: Aaro Koskinen aaro.koski...@iki.fi
Cc: Wim Van Sebroeck w...@iguana.be
---
drivers/watchdog/omap_wdt.c | 14 +++---
1 files changed, 3 insertions(+), 11 deletions(-)
diff --git a/drivers/watchdog/omap_wdt.c
Eliminate a goto to simplify the code.
Signed-off-by: Aaro Koskinen aaro.koski...@iki.fi
Cc: Wim Van Sebroeck w...@iguana.be
---
drivers/watchdog/omap_wdt.c | 11 ---
1 files changed, 4 insertions(+), 7 deletions(-)
diff --git a/drivers/watchdog/omap_wdt.c
On 11/11/2012 03:16 AM, Igor Grinberg wrote:
On 11/08/12 18:20, Tony Lindgren wrote:
* Igor Grinberg grinb...@compulab.co.il [121107 23:15]:
On 11/07/12 19:33, Tony Lindgren wrote:
I think this should be the default for the timers as that counter
does not stop during deeper idle states.
This patch set introduces drivers for CBUS access and Retu multifunction
chip found on Nokia Internet Tablets (770, N800, N810). It would be
nice get these patches applied as the functionality of these devices is
severely lacking without Retu. E.g. watchdog support is mandatory at
least on Nokia
Introduce Retu watchdog driver.
Cc: linux-watch...@vger.kernel.org
Acked-by: Felipe Balbi ba...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
Signed-off-by: Aaro Koskinen aaro.koski...@iki.fi
Cc: Wim Van Sebroeck w...@iguana.be
---
drivers/watchdog/Kconfig| 12 +++
Retu is a multi-function device found on Nokia Internet Tablets
implementing at least watchdog, RTC, headset detection and power button
functionality.
This patch implements minimum functionality providing register access,
IRQ handling and power off functions.
Cc: sa...@linux.intel.com
Acked-by:
Add Retu power button driver.
Cc: linux-in...@vger.kernel.org
Acked-by: Felipe Balbi ba...@ti.com
Signed-off-by: Aaro Koskinen aaro.koski...@iki.fi
Cc: Dmitry Torokhov dmitry.torok...@gmail.com
---
drivers/input/misc/Kconfig | 10
drivers/input/misc/Makefile |1 +
Add i2c driver to enable access to devices behind CBUS on Nokia Internet
Tablets.
The patch also adds CBUS I2C configuration for N8x0 which is one of the
users of this driver.
Cc: linux-...@vger.kernel.org
Acked-by: Felipe Balbi ba...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
On 11/11/2012 05:28 AM, Igor Grinberg wrote:
On 11/08/12 21:16, Jon Hunter wrote:
On 11/08/2012 12:59 PM, Hiremath, Vaibhav wrote:
On Fri, Nov 09, 2012 at 00:24:23, Hunter, Jon wrote:
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
[snip]
There is no reliable way to determine which
On Fri, Nov 09, 2012 at 03:17:33PM -0600, Rob Clark wrote:
From: Rob Clark r...@ti.com
A new atomic modeset/pageflip ioctl being developed in DRM requires
get_user() to work for 64bit types (in addition to just put_user()).
NAK.
(I did write a better email explaining all the ins and outs of
Here are some basic OMAP test results for Linux v3.7-rc5.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.7-rc5/2012081034/
Passing tests
-
Boot to userspace (9/11): 2420n800, 2430sdp, 3517evm, 3530es3beagle,
3730beaglexm, 37xxevm, 4430es2panda,
On Mon, Nov 12, 2012 at 1:27 PM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Fri, Nov 09, 2012 at 03:17:33PM -0600, Rob Clark wrote:
From: Rob Clark r...@ti.com
A new atomic modeset/pageflip ioctl being developed in DRM requires
get_user() to work for 64bit types (in addition to
On Mon, Nov 12, 2012 at 3:23 AM, Pantelis Antoniou
pa...@antoniou-consulting.com wrote:
Hi Grant,
Sorry for the late comments, travelling...
On Nov 9, 2012, at 6:28 PM, Grant Likely wrote:
On Tue, Nov 6, 2012 at 10:37 PM, Stephen Warren swar...@wwwdotorg.org
wrote:
On 11/05/2012 01:40
* Jon Hunter jon-hun...@ti.com [121112 10:22]:
This series includes several fixes for the OMAP DMTIMER driver. This is
based upon Tony Lindgren's current master branch [1].
You should be able to use omap-for-v3.8/dt as the base now with
the cleanup merged there. The master branch is just a
* Benoit Cousson b-cous...@ti.com [121112 02:49]:
Hi Tony,
After rebasing on top of your omap-for-v3.8/tmp-merge, I realized that this
patch is generating a build break due to removal of the fpga.h include from
debug-leds.c.
arch/arm/plat-omap/debug-leds.c: In function 'fpga_probe':
On 11/12/2012 02:34 PM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [121112 10:22]:
This series includes several fixes for the OMAP DMTIMER driver. This is
based upon Tony Lindgren's current master branch [1].
You should be able to use omap-for-v3.8/dt as the base now with
the
On Wednesday 07 November 2012, Tony Lindgren wrote:
The following changes since commit 3d70f8c617a436c7146ecb81df2265b4626dfe89:
Linux 3.7-rc4 (2012-11-04 11:07:39 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap
Remove all of the code that is compiled when CONFIG_COMMON_CLK=n in the
OMAP3+ DPLL handling code.
Signed-off-by: Paul Walmsley p...@pwsan.com
Cc: Mike Turquette mturque...@ti.com
Cc: Rajendra Nayak rna...@ti.com
---
This will be merged as part of the OMAP CCF conversion set.
On Wednesday 07 November 2012, Tony Lindgren wrote:
The following changes since commit a0212796b58061a9716178d261f318925c246643:
Merge tag 'omap-cleanup-fixes-a-for-3.8' of
git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending into
omap-for-v3.8/cleanup-headers (2012-10-26
* Omar Ramirez Luna omar.l...@linaro.org [121112 10:42]:
Hi,
On 11 November 2012 03:39, Ohad Ben-Cohen o...@wizery.com wrote:
On Fri, Nov 2, 2012 at 9:23 PM, Tony Lindgren t...@atomide.com wrote:
We need to move the iommu code to live under drivers
for arm common zImage support.
For
* Wei Yongjun weiyj...@gmail.com [121107 04:55]:
From: Wei Yongjun yongjun_...@trendmicro.com.cn
Remove duplicated include.
dpatch engine is used to auto generate this patch.
(https://github.com/weiyj/dpatch)
Thanks applying into omap-for-v3.8/cleanup-headers-prepare-multiplatform-v3.
* Igor Grinberg grinb...@compulab.co.il [12 01:18]:
On 11/08/12 18:20, Tony Lindgren wrote:
I guess what I'm after is just to avoid renaming the existing
timers in the board-*.c files and only rename the ones that
need gp timer only.
This means: get rid of the 32k to gptimer fall
* Nishanth Menon n...@ti.com [121108 12:12]:
On 21:28-20121108, Felipe Balbi wrote:
Hi,
On Thu, Nov 08, 2012 at 11:08:50AM -0800, Kevin Hilman wrote:
From: Kevin Hilman khil...@ti.com
On OMAP4 boards using the TWL6030 PMIC, the sys_drm_msecure is
connected to the MSECURE input
This patch needed to be modified to avoid some sparse warnings; updated
patch follows.
- Paul
ARM: OMAP: hwmod: Fix up hwmod based clkdm accesses
From: Rajendra Nayak rna...@ti.com
hwmod uses deferencing the clk pointer to acccess the clkdm.
With COMMON clk hwoever this will need to be
1 - 100 of 127 matches
Mail list logo
