Eric Lee / smarc-ti-linux-kernel

11 Mar, 2014

1 commit

06 Aug, 2013

1 commit

  • f9827dde2   mtd: refactor call to request_module ... Browse Code »

    This reduces the size of the stack frame when calling request_module().
    Performing the sprintf before the call is not needed.

    Signed-off-by: Kees Cook
    Acked-by: Rusty Russell
    Reviewed-by: James Hogan
    Signed-off-by: Artem Bityutskiy
    Signed-off-by: David Woodhouse

    Kees Cook
     

15 Mar, 2013

1 commit

  • b92021b09   CONFIG_SYMBOL_PREFIX: cleanup. ... Browse Code »

    We have CONFIG_SYMBOL_PREFIX, which three archs define to the string
    "_". But Al Viro broke this in "consolidate cond_syscall and
    SYSCALL_ALIAS declarations" (in linux-next), and he's not the first to
    do so.

    Using CONFIG_SYMBOL_PREFIX is awkward, since we usually just want to
    prefix it so something. So various places define helpers which are
    defined to nothing if CONFIG_SYMBOL_PREFIX isn't set:

    1) include/asm-generic/unistd.h defines __SYMBOL_PREFIX.
    2) include/asm-generic/vmlinux.lds.h defines VMLINUX_SYMBOL(sym)
    3) include/linux/export.h defines MODULE_SYMBOL_PREFIX.
    4) include/linux/kernel.h defines SYMBOL_PREFIX (which differs from #7)
    5) kernel/modsign_certificate.S defines ASM_SYMBOL(sym)
    6) scripts/modpost.c defines MODULE_SYMBOL_PREFIX
    7) scripts/Makefile.lib defines SYMBOL_PREFIX on the commandline if
    CONFIG_SYMBOL_PREFIX is set, so that we have a non-string version
    for pasting.

    (arch/h8300/include/asm/linkage.h defines SYMBOL_NAME(), too).

    Let's solve this properly:
    1) No more generic prefix, just CONFIG_HAVE_UNDERSCORE_SYMBOL_PREFIX.
    2) Make linux/export.h usable from asm.
    3) Define VMLINUX_SYMBOL() and VMLINUX_SYMBOL_STR().
    4) Make everyone use them.

    Signed-off-by: Rusty Russell
    Reviewed-by: James Hogan
    Tested-by: James Hogan (metag)

    Rusty Russell
     

20 May, 2010

1 commit

14 May, 2010

2 commits

10 May, 2010

1 commit

  • c4e773764   mtd: fix a huge latency problem in the MTD CFI and LPDDR flash drivers. ... Browse Code »

    The use of a memcpy() during a spinlock operation will cause very long
    thread context switch delays if the flash chip bandwidth is low and the
    data to be copied large, because a spinlock will disable preemption.

    For example: A flash with 6,5 MB/s bandwidth will cause under ubifs,
    which request sometimes 128 KiB (the flash erase size), a preemption delay of
    20 milliseconds. High priority threads will not be served during this
    time, regardless whether this threads access the flash or not. This behavior
    breaks real time.

    The patch changes all the use of spin_lock operations for xxxx->mutex
    into mutex operations, which is exact what the name says and means.

    I have checked the code of the drivers and there is no use of atomic
    pathes like interrupt or timers. The mtdoops facility will also not be used
    by this drivers. So it is dave to replace the spin_lock against mutex.

    There is no performance regression since the mutex is normally not
    acquired.

    Changelog:
    06.03.2010 First release
    26.03.2010 Fix mutex[1] issue and tested it for compile failure

    Signed-off-by: Stefani Seibold
    Signed-off-by: Artem Bityutskiy
    Signed-off-by: David Woodhouse

    Stefani Seibold
     

03 Aug, 2008

1 commit

12 Jul, 2008

1 commit

05 Jun, 2008

1 commit

  • 59018b6d2   MTD/JFFS2: remove CVS keywords ... Browse Code »

    Once upon a time, the MTD repository was using CVS.

    This patch therefore removes all usages of the no longer updated CVS
    keywords from the MTD code.

    This also includes code that printed them to the user.

    Signed-off-by: Adrian Bunk
    Signed-off-by: David Woodhouse

    Adrian Bunk
     

07 Feb, 2008

1 commit

30 Nov, 2006

1 commit

29 Nov, 2006

1 commit

22 May, 2006

1 commit

20 May, 2006

1 commit

18 May, 2006

1 commit

14 May, 2006

1 commit

  • 0f5ae3d2e   [MTD] Deal correctly with NOR chips which are smaller than the map window ... Browse Code »

    We used to calculate the number of chips to be zero, allocate an array
    of that size, then nasty things would happen when we attempt to access
    the first object in that zero-sized array.

    Now, if the number of _full_ chips that would fit into the map is zero,
    we allocate an array of one anyway, and then artificially reduce the
    total size of the resulting MTD device to fit in the map.

    Signed-off-by: David Woodhouse

    David Woodhouse
     

09 May, 2006

1 commit

07 Nov, 2005

2 commits

23 May, 2005

1 commit

  • 6170b4340   [MTD] Fix MTD device probing ... Browse Code »

    Try larger numbers of chips before smaller
    numbers of chips across the bus width.

    This means we'll avoid misdetecting a 2 x16 array as 1 x32 if the
    high 16-bits happen to read as zeros in the QRY area.

    Signed-off-by: Russell King
    Signed-off-by: Thomas Gleixner

    Russell King
     

17 Apr, 2005

1 commit

  • 1da177e4c   Linux-2.6.12-rc2 ... Browse Code »
    212

    Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds