On Mon, Nov 12, 2012 at 09:52:32AM -0700, Stephen Warren wrote:
> On 11/12/2012 05:10 AM, Pantelis Antoniou wrote:
[snip]
> > Oh yes. In fact if one was to use a single kernel image for beagleboard
> > and beaglebone, for the cape to work for both, it is required for it's
> > dtb to be compatible.
On Mon, Nov 12, 2012 at 10:22:07PM -0700, Stephen Warren wrote:
> On 11/12/2012 06:05 PM, David Gibson wrote:
> > On Fri, Nov 09, 2012 at 09:42:37PM +, Grant Likely wrote:
> ...
> > 2) graft bundle
> >
> > The base tree has something like this:
> >
> > ...
> > i2c@XXX {
> >
On 11/12/2012 06:05 PM, David Gibson wrote:
> On Fri, Nov 09, 2012 at 09:42:37PM +, Grant Likely wrote:
...
> 2) graft bundle
>
> The base tree has something like this:
>
> ...
> i2c@XXX {
> ...
> cape-socket {
> compatible = "vend
Hi Grant,
On Fri, Nov 9, 2012 at 3:22 PM, Grant Likely wrote:
>> (2)
>> Also this discussed a while back but at some point is going to brought
>> up again- loading of dt fragment directly from EEPROM and merging at
>> run time. If we were to implement this in kernel, we would have to add
>> cape
On Fri, Nov 09, 2012 at 09:36:26PM -0600, Joel A Fernandes wrote:
> Hi Pantelis,
>
> On Fri, Nov 9, 2012 at 2:13 AM, Pantelis Antoniou
> wrote:
>
> Option C: U-Boot loads both the base and overlay FDT files, merges them,
> and passes the resolved tree to the kernel.
>
> >>>
Here's an updated version of this one with the dpll3xxx.c changes rolled
in.
- Paul
From: Mike Turquette
Date: Sat, 10 Nov 2012 16:58:41 -0700
Subject: [PATCH] ARM: OMAP4: clock: Convert to common clk
Convert all OMAP4 specific platform files to use COMMON clk
and keep all the changes under
On Fri, Nov 09, 2012 at 09:42:37PM +, Grant Likely wrote:
> On Fri, Nov 9, 2012 at 2:26 AM, David Gibson
> wrote:
> > (3) Resolving phandle references from the subtree to the main tree.
> >
> > So, I think this can actually be avoided, at least in cases where what
> > physical connections are
* Tony Lindgren [121112 17:01]:
> The following changes since commit edf8dde393f879fc2d8c22d4bc01ff8d37b80e1a:
>
> Merge branch 'linus' into
> omap-for-v3.8/cleanup-headers-prepare-multiplatform-v3 (2012-11-09 14:58:01
> -0800)
>
> are available in the git repository at:
>
>
> git://git.
The following changes since commit edf8dde393f879fc2d8c22d4bc01ff8d37b80e1a:
Merge branch 'linus' into
omap-for-v3.8/cleanup-headers-prepare-multiplatform-v3 (2012-11-09 14:58:01
-0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap
On Mon, Nov 12, 2012 at 5:53 PM, Russell King - ARM Linux
wrote:
> On Mon, Nov 12, 2012 at 05:33:41PM -0600, Rob Clark wrote:
>> I'm sort of thinking maybe we want to change 'switch (sizeof(*(__p)))'
>> with 'switch (sizeof(typeof(x)))' in case someone ignores the compiler
>> warning when they try
On Fri, Nov 09, 2012 at 09:08:14PM +, Grant Likely wrote:
> On Fri, Nov 9, 2012 at 2:26 AM, David Gibson
> wrote:
> >> Summary points:
> >> - Create an FDT overlay data format and usage model
> >> - SHALL reliable resolve or validate of phandles between base and
> >> overlay trees
> >
>
On Fri, Nov 09, 2012 at 04:40:15PM +0100, Pantelis Antoniou wrote:
> Hi David,
[snip]
> > I think graft is basically a safer operation, particular if we're
> > doing this at runtime with userspace passing in these fdt fragments.
> > In fact I'd go so far as to say if you really need the full overl
On Mon, Nov 12, 2012 at 05:33:41PM -0600, Rob Clark wrote:
> I'm sort of thinking maybe we want to change 'switch (sizeof(*(__p)))'
> with 'switch (sizeof(typeof(x)))' in case someone ignores the compiler
> warning when they try something like:
Definitely not. Ttype of access is controlled by the
* Afzal Mohammed [121109 06:23]:
> The following changes since commit 6ba54ab4a49bbad736b0254aa6bdf0cb83013815:
>
> ARM: OMAP: Remove omap_init_consistent_dma_size() (2012-11-06 16:01:19
> -0800)
>
> are available in the git repository at:
>
> git://gitorious.org/x0148406-public/linux-kern
On Mon, Nov 12, 2012 at 5:08 PM, Russell King - ARM Linux
wrote:
> On Mon, Nov 12, 2012 at 01:58:32PM -0600, Rob Clark wrote:
>> On Mon, Nov 12, 2012 at 1:27 PM, Russell King - ARM Linux
>> wrote:
>> > On Fri, Nov 09, 2012 at 03:17:33PM -0600, Rob Clark wrote:
>> >> From: Rob Clark
>> >>
>> >> A
* Sasha Levin [121108 12:26]:
> Just use BUG_ON() instead of constructions such as:
>
> if (...)
> BUG()
>
> A simplified version of the semantic patch that makes this transformation
> is as follows: (http://coccinelle.lip6.fr/)
>
> //
> @@
> expression e;
> @@
> - if (e) B
On Mon, Nov 12, 2012 at 01:58:32PM -0600, Rob Clark wrote:
> On Mon, Nov 12, 2012 at 1:27 PM, Russell King - ARM Linux
> wrote:
> > On Fri, Nov 09, 2012 at 03:17:33PM -0600, Rob Clark wrote:
> >> From: Rob Clark
> >>
> >> A new atomic modeset/pageflip ioctl being developed in DRM requires
> >> ge
Added kerneldoc on the new non-trivial function in this patch, as is local
policy. Updated patch follows.
- Paul
From: Rajendra Nayak
Date: Fri, 1 Jun 2012 14:02:49 +0530
Subject: [PATCH] ARM: OMAP: clock: Define a function to enable clocks at init
Platform code can use omap2_clk_enable_init
Added kerneldoc to the non-trivial new functions added by this patch, as
is local policy. Updated patch below.
- Paul
From: Rajendra Nayak
Date: Fri, 1 Jun 2012 14:02:49 +0530
Subject: [PATCH] ARM: OMAP: clock: list all clk_hw_omap clks to
enable/disable autoidle
Platforms can call omap2_i
* Paul Walmsley [121112 11:33]:
>
> 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, 353
* Jon Hunter [121108 12:43]:
>
> On 11/02/2012 07:32 AM, Vaibhav Bedia wrote:
> > AM33XX has only one usable timer in the WKUP domain.
> > Currently the timer instance in WKUP domain is used
> > as the clockevent and the timer in non-WKUP domain
> > as the clocksource. The timer in WKUP domain ca
Fix a compiler warning on clockfw_lock, and add kerneldoc on the new
non-trivial functions added by this patch, as is policy. Updated patch
follows.
- Paul
From: Mike Turquette
Date: Sat, 10 Nov 2012 16:58:41 -0700
Subject: [PATCH] ARM: OMAP4: clock: Convert to common clk
Convert all OMAP4
* Tomi Valkeinen [121112 02:27]:
> 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 followin
* Aaro Koskinen [121112 10:49]:
> 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,
Quoting Paul Walmsley (2012-11-12 13:50:53)
> Remove all of the code that is compiled when CONFIG_COMMON_CLK=n in the
> OMAP3+ DPLL handling code.
>
> Signed-off-by: Paul Walmsley
> Cc: Mike Turquette
> Cc: Rajendra Nayak
Hmm, dpll3xxx.c fell through the cracks during #ifdef cleanup. Patch
lo
This patch needed some significant modifications to deal with the APLL
changes in its new base; updated patch follows.
- Paul
ARM: OMAP2: clock: Convert to common clk
From: Rajendra Nayak
Convert all OMAP2 specific platform files to use COMMON clk
and keep all the changes under the CONFIG_
* Balaji T K [121112 05:22]:
> 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
>
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
hwmod uses deferencing the clk pointer to acccess the clkdm.
With COMMON clk hwoever this will need to be deferenced through
* Nishanth Menon [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
> > >
> > > On OMAP4 boards using the TWL6030 PMIC, the sys_drm_msecure is
> > > connected to the MSECURE input of the
* Igor Grinberg [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 back.
> I've
* Wei Yongjun [121107 04:55]:
> From: Wei Yongjun
>
> 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.
Regards,
Tony
--
To unsubscribe from this l
* Omar Ramirez Luna [121112 10:42]:
> Hi,
>
> On 11 November 2012 03:39, Ohad Ben-Cohen wrote:
> > On Fri, Nov 2, 2012 at 9:23 PM, Tony Lindgren wrote:
> >> We need to move the iommu code to live under drivers
> >> for arm common zImage support.
> >
> > For the iommu changes in the entire serie
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 1
Remove all of the code that is compiled when CONFIG_COMMON_CLK=n in the
OMAP3+ DPLL handling code.
Signed-off-by: Paul Walmsley
Cc: Mike Turquette
Cc: Rajendra Nayak
---
This will be merged as part of the OMAP CCF conversion set.
arch/arm/mach-omap2/dpll3xxx.c | 231 +--
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
>
On 11/12/2012 02:34 PM, Tony Lindgren wrote:
> * Jon Hunter [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
* Benoit Cousson [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':
> arch/arm/pl
* Jon Hunter [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 merge of the
various
On Mon, Nov 12, 2012 at 3:23 AM, Pantelis Antoniou
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
>> wrote:
>>> On 11/05/2012 01:40 PM, Grant Likely wrote:
Hey folks,
On Mon, Nov 12, 2012 at 1:27 PM, Russell King - ARM Linux
wrote:
> On Fri, Nov 09, 2012 at 03:17:33PM -0600, Rob Clark wrote:
>> From: Rob Clark
>>
>> A new atomic modeset/pageflip ioctl being developed in DRM requires
>> get_user() to work for 64bit types (in addition to just put_user()).
>
> NA
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, 59
On Fri, Nov 09, 2012 at 03:17:33PM -0600, Rob Clark wrote:
> From: Rob Clark
>
> 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 why thi
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 r
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
Acked-by: Tony Lindgren
Signed-off-by: Aaro Koskinen
Cc: Wolfram
Add Retu power button driver.
Cc: linux-in...@vger.kernel.org
Acked-by: Felipe Balbi
Signed-off-by: Aaro Koskinen
Cc: Dmitry Torokhov
---
drivers/input/misc/Kconfig | 10
drivers/input/misc/Makefile |1 +
drivers/input/misc/retu-pwrbutton.c | 102 ++
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: F
Introduce Retu watchdog driver.
Cc: linux-watch...@vger.kernel.org
Acked-by: Felipe Balbi
Acked-by: Tony Lindgren
Signed-off-by: Aaro Koskinen
Cc: Wim Van Sebroeck
---
drivers/watchdog/Kconfig| 12 +++
drivers/watchdog/Makefile |1 +
drivers/watchdog/retu_wdt.c | 178
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 N8
On 11/11/2012 03:16 AM, Igor Grinberg wrote:
> On 11/08/12 18:20, Tony Lindgren wrote:
>> * Igor Grinberg [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.
>>>
>>> W
Eliminate a goto to simplify the code.
Signed-off-by: Aaro Koskinen
Cc: Wim Van Sebroeck
---
drivers/watchdog/omap_wdt.c | 11 ---
1 files changed, 4 insertions(+), 7 deletions(-)
diff --git a/drivers/watchdog/omap_wdt.c b/drivers/watchdog/omap_wdt.c
index af1e72e..bee43a9 100644
---
Use devm_ioremap() to simplify the code.
Signed-off-by: Aaro Koskinen
Cc: Wim Van Sebroeck
---
drivers/watchdog/omap_wdt.c | 14 +++---
1 files changed, 3 insertions(+), 11 deletions(-)
diff --git a/drivers/watchdog/omap_wdt.c b/drivers/watchdog/omap_wdt.c
index 45019b0..7e8d3e0 1006
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
N
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.
S
Use devm_kzalloc() to simplify the code.
Signed-off-by: Aaro Koskinen
Cc: Wim Van Sebroeck
---
drivers/watchdog/omap_wdt.c | 23 ++-
1 files changed, 6 insertions(+), 17 deletions(-)
diff --git a/drivers/watchdog/omap_wdt.c b/drivers/watchdog/omap_wdt.c
index d28ad5e..d67
Use devm_request_mem_region() to simplify the code.
Signed-off-by: Aaro Koskinen
Cc: Wim Van Sebroeck
---
drivers/watchdog/omap_wdt.c | 13 -
1 files changed, 4 insertions(+), 9 deletions(-)
diff --git a/drivers/watchdog/omap_wdt.c b/drivers/watchdog/omap_wdt.c
index d6722db..450
It's not needed to manually reset the driver data.
Signed-off-by: Aaro Koskinen
Cc: Wim Van Sebroeck
---
drivers/watchdog/omap_wdt.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/drivers/watchdog/omap_wdt.c b/drivers/watchdog/omap_wdt.c
index 7e8d3e0..af1e72e 100644
Hi,
On 11 November 2012 03:39, Ohad Ben-Cohen wrote:
> On Fri, Nov 2, 2012 at 9:23 PM, Tony Lindgren 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 Ben-Cohen
>
> Joerg, it might
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
structure
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
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
have
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
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 i
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+
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.
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
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 th
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 s
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 i
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 m
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
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 corr
* Paul Walmsley [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’ undeclared
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
* Tomi Valkeinen [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
> code. The oma
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
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
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:
>> .
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 go
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
>>> wrote:
On 11/05/2012 01:40 PM, Grant Likely wrote:
>>> I'
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
>>> wrote:
>> ...
I do rather suspect this use-case is quite common. NV
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 exis
On 11/09/2012 09:28 AM, Grant Likely wrote:
> On Tue, Nov 6, 2012 at 10:37 PM, Stephen Warren 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. Comments
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)
> arch/arm/mach-
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 U
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 is
On Mon, Nov 12, 2012 at 8:38 AM, Will Deacon wrote:
> On Mon, Nov 12, 2012 at 01:46:57PM +, Rob Clark wrote:
>> On Mon, Nov 12, 2012 at 4:46 AM, Will Deacon wrote:
>> > On Fri, Nov 09, 2012 at 09:17:33PM +, Rob Clark wrote:
>> >> @@ -122,22 +124,35 @@ extern int __get_user_4(void *);
>> >
On Tue, 2012-11-06 at 13:19 -0800, Kevin Hilman wrote:
> Tero Kristo writes:
>
> > Hi Kevin,
> >
> > On Mon, 2012-11-05 at 14:23 -0800, Kevin Hilman wrote:
> >> Hi Tero,
> >>
> >> Tero Kristo writes:
> >>
> >> > Hi,
> >> >
> >> > Changes compared to previous version:
> >> > - rebased on top of
On Mon, Nov 12, 2012 at 01:46:57PM +, Rob Clark wrote:
> On Mon, Nov 12, 2012 at 4:46 AM, Will Deacon wrote:
> > On Fri, Nov 09, 2012 at 09:17:33PM +, Rob Clark wrote:
> >> @@ -122,22 +124,35 @@ extern int __get_user_4(void *);
> >> ({
On 2012-11-12 15:39, Grazvydas Ignotas wrote:
> Hi,
>
> On Mon, Nov 12, 2012 at 12:25 PM, Tomi Valkeinen
> 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 inde
On 2012-11-12 15:39, Grazvydas Ignotas wrote:
> Hi,
>
> On Mon, Nov 12, 2012 at 12:25 PM, Tomi Valkeinen
> 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 inde
On Mon, Nov 12, 2012 at 4:46 AM, Will Deacon wrote:
> On Fri, Nov 09, 2012 at 09:17:33PM +, Rob Clark wrote:
>> From: Rob Clark
>>
>> 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
Hi,
On Mon, Nov 12, 2012 at 12:25 PM, Tomi Valkeinen 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 standard dma funcs c
Remove including plat/dma.h which is not needed.
Signed-off-by: Tomi Valkeinen
---
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 7b1afc8..a2cc634 100644
--- a/
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 o
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
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, *pte=,
Avoid soft reset of command internal state machine on data errors.
Signed-off-by: Balaji T K
Reviewed-by: Felipe Balbi
---
drivers/mmc/host/omap_hsmmc.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsmmc.c
index
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(-)
update error code to cmd->error for commands with response_busy and no data
Signed-off-by: Balaji T K
Reviewed-by: Felipe Balbi
---
drivers/mmc/host/omap_hsmmc.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsmm
"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
1 - 100 of 128 matches
Mail list logo
