Add missing break statement in the function omap3xxx_check_revision.
The commit id 4390f5b2cb1f56 [ARM: OMAP: TI814X: Add cpu type macros
and detection support], removed the 'break' statement from the function
omap3xxx_check_revision(), resulting into wrong omap/cpu_revision
initialization for AM3
following statement can only change device size from 8-bit(0) to 16-bit(1),
but not vice versa:
regval |= GPMC_CONFIG1_DEVICESIZE(wval);
so as this field has 1 reserved bit, that could be used in future,
just clear both bits and then OR with the desired value
Signed-off-by: Yegor Yefremov
---
v
In dmtimer_read_sched_clock(), wrong argument was getting passed to
__omap_dm_timer_read_counter() function call; instead of "&clksrc",
we were passing "clksrc.io_base", which results into kernel crash.
To reproduce kernel crash, just disable the CONFIG_OMAP_32K_TIMER config
option (and DEBUG_LL)
Hi,
I'm using the DM37x EVM and need to trigger the vibra ports on the
TPS65950.
It appears that I just need to define INPUT_TWL4030_VIBRA in the config.
After doing this, I see that the twl4030-vibra platform driver is
registered, but the twl4030_vibra_probe() function is never called.
Is there s
On Sat, Jan 21, 2012 at 21:46:38, Gary Thomas wrote:
> I'm running the public 3.0 kernel on my boards. I have some boards
> which can have either OMAP3530 or DM3730 (newer boards have the
> newer part, but everything else is the same).
>
> On the OMAP3530, I can enable the graphics overlay on the
I experience an unhandled fault on reboot/shutdown using the ARM-OMAP
kernel-2.6.41.3-1 and later (from Fedora) on a Panda Board. I have logged a
bug in:
https://bugzilla.redhat.com/show_bug.cgi?id=781552
which provides the details, and a work around which reverts one commit
from kernel-3
Hello Govindraj
while trying to track down some of the serial-related PM issues in
v3.3-rc1, I noticed that the omap-serial.c driver sets a 1 microsecond
polling timer when DMA is enabled (uart_dma.rx_timer) (!) This seems
quite broken from both the DMA and PM points of view.
>From a DMA poi
HDQ/1-wire registers are 32 bits long, even if the register contents
fit into 8 bits, so accesses must be 32-bit aligned. Evidently the
OMAP2/3 interconnects allowed the driver to get away with 8 bit accesses,
but the OMAP4 puts a stop to that:
[1.488800] Driver for 1-wire Dallas network pro
On Sun, 22 Jan 2012 12:54:21 -0700 (MST), Paul Walmsley wrote:
> cc Ben, Jean
I'm not involved in this at all.
Jean
>
> On Sun, 22 Jan 2012, Cousson, Benoit wrote:
>
> > http://lists.ozlabs.org/pipermail/devicetree-discuss/2011-December/010541.html
> >
> > But it looks like it was stuck in li
cc Ben, Jean
On Sun, 22 Jan 2012, Cousson, Benoit wrote:
> http://lists.ozlabs.org/pipermail/devicetree-discuss/2011-December/010541.html
>
> But it looks like it was stuck in linux-omap dt branch and not pulled for 3.3.
> Maybe Tony can try to sent it during -rc phase.
>
> That being said, thi
On 1/22/2012 5:06 PM, Rob Herring wrote:
On 01/22/2012 09:45 AM, Grant Likely wrote:
On Sun, Jan 22, 2012 at 04:02:33AM -0700, Paul Walmsley wrote:
Commit 6145197be6cc0583fa1a2f4ec1079d366137061e ("i2c: OMAP: Add DT
support for i2c controller") breaks compilation when CONFIG_OF is not
defined:
On 01/22/2012 09:45 AM, Grant Likely wrote:
> On Sun, Jan 22, 2012 at 04:02:33AM -0700, Paul Walmsley wrote:
>> Commit 6145197be6cc0583fa1a2f4ec1079d366137061e ("i2c: OMAP: Add DT
>> support for i2c controller") breaks compilation when CONFIG_OF is not
>> defined:
>>
>> CC drivers/i2c/busses
On Sun, Jan 22, 2012 at 8:40 AM, Rob Herring wrote:
> On 01/22/2012 05:02 AM, Paul Walmsley wrote:
>> Commit 6145197be6cc0583fa1a2f4ec1079d366137061e ("i2c: OMAP: Add DT
>> support for i2c controller") breaks compilation when CONFIG_OF is not
>> defined:
>>
>> CC drivers/i2c/busses/i2c-omap
On Sun, Jan 22, 2012 at 04:02:33AM -0700, Paul Walmsley wrote:
> Commit 6145197be6cc0583fa1a2f4ec1079d366137061e ("i2c: OMAP: Add DT
> support for i2c controller") breaks compilation when CONFIG_OF is not
> defined:
>
> CC drivers/i2c/busses/i2c-omap.o
> drivers/i2c/busses/i2c-omap.c: In fu
On 01/22/2012 05:02 AM, Paul Walmsley wrote:
> Commit 6145197be6cc0583fa1a2f4ec1079d366137061e ("i2c: OMAP: Add DT
> support for i2c controller") breaks compilation when CONFIG_OF is not
> defined:
>
> CC drivers/i2c/busses/i2c-omap.o
> drivers/i2c/busses/i2c-omap.c: In function 'omap_i2c_p
On Sat, 21 Jan 2012, Paul Walmsley wrote:
> [ This series is targeted for merging during v3.3-rc ]
>
> On v3.3-rc1, the OMAP serial console doesn't behave properly when
> power management is enabled (the default with omap2plus_defconfig).
> This seems to be due to a combination of a silicon bug i
On Sat, 21 Jan 2012 17:07:18 -0700 (MST) Paul Walmsley wrote:
> On Wed, 18 Jan 2012, NeilBrown wrote:
>
> > Oh - another thing.
> > Sometimes during early boot I get:
> >
> > [0.158447] omap_hwmod: usbtll_fck: missing clockdomain for usbtll_fck.
> > [0.176879] omap_hwmod: hdq: softreset
On Fri, 20 Jan 2012 17:00:09 +0200 Tomi Valkeinen
wrote:
> Hmm, So CPU_IDLE is also about other power domains than mpu? What does
> it do? The CONFIG_CPU_IDLE help text doesn't say much.
On OMAP3x, CPU_IDLE is about the MPU and CORE power domains .. and about PER
to some extent I think.
Differ
On Sat, Jan 21, 2012 at 10:47 PM, Paul Walmsley wrote:
> On Sat, 21 Jan 2012, Tomi Valkeinen wrote:
>
>> On Sat, 2012-01-21 at 00:47 -0700, Paul Walmsley wrote:
>> > On Fri, 20 Jan 2012, Tomi Valkeinen wrote:
>> >
>> > > Third, when I load the DSS modules, I see only ON state increasing for
>> > >
Commit 7b250aff1ce346b6c7bc0329a2350334d1c66525 ("ARM: OMAP: Avoid
cpu_is_omap usage until map_io is done") breaks the build on a
2420-only config on v3.3-rc1:
arch/arm/mach-omap2/built-in.o: In function `omap2430_init_early':
arch/arm/mach-omap2/io.c:406: undefined reference to `omap2_set_glo
Commit 22f51371f8c35869ed850f46aa76b6cc2b502110 ("ARM: OMAP3: pm: use
prcm chain handler") breaks the build on a 2420-only config, due to
a missing include for plat/irqs.h:
CC arch/arm/mach-omap2/prm2xxx_3xxx.o
arch/arm/mach-omap2/prm2xxx_3xxx.c:41:11: error: 'INT_34XX_PRCM_MPU_IRQ'
undecl
Fix several compilation problems detected with a 2420-only kernel
configuration. This series is intended for the v3.3-rc merge window.
These patches are available via git at git://git.pwsan.com/linux-2.6 in the
branch "omap2420_compilation_fixes_3.3rc"
- Paul
---
Paul Walmsley (3):
ARM:
Commit 6145197be6cc0583fa1a2f4ec1079d366137061e ("i2c: OMAP: Add DT
support for i2c controller") breaks compilation when CONFIG_OF is not
defined:
CC drivers/i2c/busses/i2c-omap.o
drivers/i2c/busses/i2c-omap.c: In function 'omap_i2c_probe':
drivers/i2c/busses/i2c-omap.c:1021:26: error: 'oma
23 matches
Mail list logo
