31 Aug, 2016

1 commit


16 Aug, 2016

1 commit


13 May, 2016

1 commit

  • The padconf register WAKEUP_EN is now handled in a generic way using
    Linux wakeirqs where pinctrl-single toggles the WAKEUP_EN bit when
    a wakeirq is enabled or disabled.

    At least omap5 gets confused if the WAKEUP_EN bit is set and the pin
    is not claimed as a wakeirq. The end result is that wakeirqs don't
    work properly as there is nothing handling the wakeirq.

    So let's just remove the WAKEUP_EN usage from dts files.

    Signed-off-by: Tony Lindgren

    Tony Lindgren
     

13 Apr, 2016

4 commits


13 Feb, 2016

3 commits


28 Jan, 2016

1 commit

  • Add support for the wl1271 wlan chip. As far as I can see N9 uses the
    same chip with the same enable and irq gpio, but they use the mmc
    interface instead of the spi interface.

    Signed-off-by: Sebastian Reichel
    Acked-by: Igor Grinberg
    Signed-off-by: Tony Lindgren

    Sebastian Reichel
     

01 Dec, 2015

1 commit


13 Oct, 2015

1 commit


20 Mar, 2015

1 commit

  • Harmattan system on Nokia N9 and N950 devices uses omap crypto support.
    Bootloader on those devices is known that it enables HW crypto support.
    This patch just include omap36xx.dtsi directly, so aes and sham is enabled.

    Signed-off-by: Pali Rohár
    Acked-by: Pavel Machek
    Signed-off-by: Tony Lindgren

    Pali Rohár
     

08 Jan, 2015

1 commit


30 Oct, 2014

1 commit

  • The GPMC binding is obviously very confusing as the values
    are all over the place. People seem to confuse the GPMC partition
    size for the chip select, and the device IO size within the GPMC
    partition easily.

    The ranges entry contains the GPMC partition size. And the
    reg entry contains the size of the IO registers of the
    device connected to the GPMC.

    Let's fix the issue according to the following table:

    Device GPMC partition size Device IO size
    connected in the ranges entry in the reg entry

    NAND 0x01000000 (16MB) 4
    16550 0x01000000 (16MB) 8
    smc91x 0x01000000 (16MB) 0xf
    smc911x 0x01000000 (16MB) 0xff
    OneNAND 0x01000000 (16MB) 0x20000 (128KB)
    16MB NOR 0x01000000 (16MB) 0x01000000 (16MB)
    32MB NOR 0x02000000 (32MB) 0x02000000 (32MB)
    64MB NOR 0x04000000 (64MB) 0x04000000 (64MB)
    128MB NOR 0x08000000 (128MB) 0x08000000 (128MB)
    256MB NOR 0x10000000 (256MB) 0x10000000 (256MB)

    Let's also add comments to the fixed entries while at it.

    Acked-by: Roger Quadros
    Signed-off-by: Tony Lindgren

    Tony Lindgren
     

07 May, 2014

1 commit


07 Dec, 2013

1 commit

  • Commit 7ce93f3 (ARM: OMAP2+: Fix more missing data for omap3.dtsi file)
    fixed missing device tree data for omaps, but did not account for some of the
    hardware modules being inaccessible for secure omaps. This causes the
    following error on secure omaps:

    Unhandled fault: external abort on non-linefetch (0x1028) at 0xfa0c5048
    SMP ARM
    Modules linked in:
    CPU: 0 PID: 1 Comm: swapper/0 Tainted: G W 3.13.0-rc2+ #446
    task: ce057b40 ti: ce058000 task.ti: ce058000
    PC is at omap_aes_dma_stop+0x24/0x3c
    LR is at omap_aes_probe+0x1cc/0x584
    psr: 60000113
    sp : ce059e20 ip : ce0b4ee0 fp : 00000000
    r10: c0573ae8 r9 : c0749508 r8 : 00000000
    r7 : ce0b4e00 r6 : 00000000 r5 : ce0b4e10 r4 : ce274890
    r3 : fa0c5048 r2 : 00000048 r1 : 0000002c r0 : ce274890
    Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
    Control: 10c5387d Table: 80004019 DAC: 00000015
    Process swapper/0 (pid: 1, stack limit = 0xce058248)
    Stack: (0xce059e20 to 0xce05a000)
    9e20: c0749508 0000a1ff 00000000 c016cd8c c06b5a06 ce2a45f0 ce2a4570 ce0b5fb0
    9e40: 00000000 480c5000 480c504f c0abe4e4 00000200 00000000 00000000 00000000
    9e60: ce0b4e10 ce0b4e10 c082da3c c082da3c c02b8c70 c077c610 c0749508 00000000
    9e80: 00000000 c02b9e7c c02b9e64 ce0b4e10 00000000 c02b8b20 ce0b4e10 ce0b4e44
    9ea0: c082da3c c02b8cd8 00000000 ce059eb8 c082da3c c02b7408 ce079edc ce0b1a34
    9ec0: c082da3c c082da3c ce2a0280 00000000 c08158d8 c02b8358 c0663405 c0663405
    9ee0: 00000073 c082da3c c079e4e8 c07ab3bc c0844340 c02b9334 00000000 00000006
    9f00: c079e4e8 c0008920 c067f6bf c0ac7c6b 00000000 c0712e28 00000000 00000000
    9f20: c0712e38 ce059f38 00000093 c0ac7c82 00000000 c0058994 00000000 c07130e8
    9f40: c07127b8 00000093 00000006 00000006 00000001 00000006 00000006 c079e4e8
    9f60: c07ab3bc c0844340 00000093 c0749508 c079e4f4 c0749c64 00000006 00000006
    9f80: c0749508 00000000 00000000 c0517e2c 00000000 00000000 00000000 00000000
    9fa0: 00000000 c0517e34 00000000 c000dfb8 00000000 00000000 00000000 00000000
    9fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
    9fe0: 00000000 00000000 00000000 00000000 00000013 00000000 ffffffff ffffffff
    (omap_aes_probe+0x1cc/0x584)
    (platform_drv_probe+0x18/0x48)
    (driver_probe_device+0xb0/0x200)
    (__driver_attach+0x68/0x8c)
    (bus_for_each_dev+0x50/0x88)
    (bus_add_driver+0xcc/0x1c8)
    (driver_register+0x9c/0xe0)
    (do_one_initcall+0x98/0x140)
    (kernel_init_freeable+0x16c/0x23c)
    (kernel_init+0x8/0x100)
    (ret_from_fork+0x14/0x3c)
    Code: e1811002 e5932020 e590300c e0833002 (e593c000)

    Let's fix the issue by adding omap34xx-hs.dtsi and omap36xx-hs.dtsi and make
    n900, n9 and n950 to use them. This way we have the aes, sham and timer12
    disabled for secure devices the same way legacy booting does based on the
    omap34xx_gp_hwmod_ocp_ifs and omap36xx_gp_hwmod_ocp_ifs arrays in
    omap_hwmod_3xxx_data.c.

    Reported-by: Sebastian Reichel
    Acked-By: Sebastian Reichel
    Tested-by: Aaro Koskinen
    Signed-off-by: Tony Lindgren

    Tony Lindgren
     

19 Oct, 2013

1 commit