Hi Laurent,
I have a beagle xm board, but no sensor board. Is it possible to have
the omap3-isp initialised ?
I would like to try my program on a beagle board to eliminate any
hardware related problem.
>From the board file in mainline kernel, it seems omap3_init_camera is
not called, do you know a
Trying to boot 3.10-rc1 on an am3515 based board. With the same .config as 3.7
the system comes to RTC stops there. I've also tried make omap2plus_defconfig
with no visible difference. I'm booting from MMC card and it will be detected
by the system. Kernel is from
http://git.kernel.org/cgit/lin
@@ -745,6 +781,11 @@ static int omap2_mcspi_setup_transfer(struct
spi_device *spi,
mcspi = spi_master_get_devdata(spi->master);
spi_cntrl = mcspi->master;
+ if (!cd && spi->dev.of_node) {
+ cd = omap2_mcspi_get_slave_ctrldata(spi);
> + spi->c
The commit:
388e5c5 usb: dwc3: remove dwc3 dependency on host AND gadget
breaks compilation when
USB=y, USB_GADGET=m, USB_DWC3=y and USB_DWC3_DUAL_ROLE=y.
drivers/built-in.o: In function `dwc3_gadget_giveback':
drivers/usb/dwc3/gadget.c:271: undefined reference to `usb_gadget_unmap_request'
driver
On Tue, May 14, 2013 at 11:24:44AM +0200, Yegor Yefremov wrote:
> Trying to boot 3.10-rc1 on an am3515 based board. With the same
> .config as 3.7 the system comes to RTC stops there. I've also tried
> make omap2plus_defconfig with no visible difference. I'm booting from
> MMC card and it will be d
On 14.05.2013 14:52, Felipe Balbi wrote:
> On Tue, May 14, 2013 at 11:24:44AM +0200, Yegor Yefremov wrote:
>> Trying to boot 3.10-rc1 on an am3515 based board. With the same
>> .config as 3.7 the system comes to RTC stops there. I've also tried
>> make omap2plus_defconfig with no visible difference
Felipe Balbi writes:
> those USB bits work fine, so we can enable them
> safely. Plus, without USB_PHY EHCI wouldn't work
> and it would take quite a few bogus error reports
> until all users got the new changes.
>
> Signed-off-by: Felipe Balbi
> ---
>
> comiple tested only. Would be great to ha
Joel A Fernandes writes:
> Calling runtime PM API for every block causes serious perf hit to
> crypto operations that are done on a long buffer.
> As crypto is performed on a page boundary, encrypting large buffers can
> cause a series of crypto operations divided by page. The runtime PM API
> is
The GPIO for LED D1 on the omap4-panda a1-a3 rev and the omap4-panda-es
are different.
A1-A3 = gpio_wk7
ES = gpio_110
There is no change to LED D2
Abstract away the pinmux and the LED definitions for the two boards into
the respective DTS files.
Signed-off-by: Dan Murphy
---
arch/arm/boot/dts
_enable_preprogram is marked as __init, but is called from _enable which is not.
This results in oops once init is freed.
Fix this by removing the __init marker.
Signed-off-by: Jean-Philippe François
Index: b/arch/arm/mach-omap2/omap_hwmod.c
=
From: Vincent Stehlé
OMAP5 needs SCU in SMP.
This fixes the following link errors:
arch/arm/mach-omap2/built-in.o: In function `scu_gp_set':
arch/arm/mach-omap2/sleep44xx.S:132: undefined reference to `scu_power_mode'
arch/arm/mach-omap2/built-in.o: In function `scu_gp_clear':
arch/arm/
From: Vincent Stehlé
Fix the following compilation warning:
arch/arm/mach-omap2/gpmc.c: In function 'gpmc_probe_generic_child':
arch/arm/mach-omap2/gpmc.c:1477:4: warning: format '%x' expects argument of
type 'unsigned int', but argument 4 has type 'resource_size_t' [-Wformat]
Signed-off-b
jp.franc...@cynove.com writes:
> _enable_preprogram is marked as __init, but is called from _enable which is
> not.
> This results in oops once init is freed.
> Fix this by removing the __init marker.
>
> Signed-off-by: Jean-Philippe François
Acked-by: Kevin Hilman
Tony, this should probably
On Tue, May 14, 2013 at 06:07:01PM +0200, jp.franc...@cynove.com wrote:
> _enable_preprogram is marked as __init, but is called from _enable which is
> not.
> This results in oops once init is freed.
> Fix this by removing the __init marker.
>
> Signed-off-by: Jean-Philippe François
This is n
By also making it return the modified value, we save the readl
needed to update the context.
Signed-off-by: Andreas Fenkart
---
drivers/gpio/gpio-omap.c | 162 ++
1 file changed, 50 insertions(+), 112 deletions(-)
diff --git a/drivers/gpio/gpio-omap.
OMAP4430 TRM chap. 25.4.5.2
To reduce dynamic consumption, an efficient idle scheme is based on the
following:
• An efficient local autoclock gating for each module
• The implementation of control sideband signals between the PRCM module
and each module
This enhanced idle control allows clocks to
Disabling an IRQ is turning off interrupt generating mechanisms in the
hardware. Masking means, the interrupt doesn't get delivered to the OS,
but the interrupt status register is still getting updated. The
difference is apparent when unmasking or re-enabling the interrupt. In
case of masking you m
Hi,
* Paul Walmsley [130508 12:45]:
>
> PM off, dynamic idle:
> FAIL ( 2/ 5): 4430es2panda, 4460pandaes
> Pass ( 3/ 5): 3530es3beagle, 3730beaglexm, 37xxevm
Looking at your pm logs, 3730beaglexm won't hit off-idle.
I've pasted the relevant lines from your logs below.
Is this a known is
On Tue, 14 May 2013, Tony Lindgren wrote:
> Hi,
>
> * Paul Walmsley [130508 12:45]:
> >
> > PM off, dynamic idle:
> > FAIL ( 2/ 5): 4430es2panda, 4460pandaes
> > Pass ( 3/ 5): 3530es3beagle, 3730beaglexm, 37xxevm
>
> Looking at your pm logs, 3730beaglexm won't hit off-idle.
> I've past
* Paul Walmsley [130514 14:24]:
> On Tue, 14 May 2013, Tony Lindgren wrote:
>
> > Hi,
> >
> > * Paul Walmsley [130508 12:45]:
> > >
> > > PM off, dynamic idle:
> > > FAIL ( 2/ 5): 4430es2panda, 4460pandaes
> > > Pass ( 3/ 5): 3530es3beagle, 3730beaglexm, 37xxevm
> >
> > Looking at you
Hi Jean-Philippe,
On Tuesday 14 May 2013 11:29:39 jean-philippe francois wrote:
> Hi Laurent,
>
> I have a beagle xm board, but no sensor board. Is it possible to have
> the omap3-isp initialised ?
Yes it is. You will just need to call omap3_init_camera() in your board code
with a pointer to pl
Acked-by: Pekon Gupta
> OMAP devices support various NAND transfer modes.
>
> Currently all device-tree definitions will use the default "prefetch
> polled" mode, so this patch enables the transfer mode to be specified
> in the device-tree.
> ---
> .../devicetree/bindings/mtd/gpmc-nand.txt
$subject - add a space?
s/ARM:dts:omap4-panda:Update/ARM: dts: omap4-panda: Update/ ?
On 09:17-20130514, Dan Murphy wrote:
> The GPIO for LED D1 on the omap4-panda a1-a3 rev and the omap4-panda-es
> are different.
>
> A1-A3 = gpio_wk7
Thanks for fixing this - this is a key fix else,
On Saturday 11 May 2013 08:05 AM, Tony Lindgren wrote:
Commit ad871c10 (ARM: dts: OMAP: Add usb_otg and glue data to
OMAP3+ boards) added support for MUSB on omap3 for device tree,
but added the interrupts the wrong way probably as they were
copied from the omap4.dtsi file. On omap3 we have TI sp
Added board specific dt data for omap3 beagle in omap3-beagle.dts
file.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap3-beagle.dts |7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-beagle.dts
b/arch/arm/boot/dts/omap3-beagle.dts
index 6eec69
25 matches
Mail list logo
