22 May, 2010

1 commit

  • .name, .match_table and .owner are duplicated in both of_platform_driver
    and device_driver. This patch is a removes the extra copies from struct
    of_platform_driver and converts all users to the device_driver members.

    This patch is a pretty mechanical change. The usage model doesn't change
    and if any drivers have been missed, or if anything has been fixed up
    incorrectly, then it will fail with a compile time error, and the fixup
    will be trivial. This patch looks big and scary because it touches so
    many files, but it should be pretty safe.

    Signed-off-by: Grant Likely
    Acked-by: Sean MacLennan

    Grant Likely
     

19 May, 2010

1 commit


22 Sep, 2009

1 commit


23 May, 2009

1 commit

  • Until now we have had a 1:1 mapping between storage device physical
    block size and the logical block sized used when addressing the device.
    With SATA 4KB drives coming out that will no longer be the case. The
    sector size will be 4KB but the logical block size will remain
    512-bytes. Hence we need to distinguish between the physical block size
    and the logical ditto.

    This patch renames hardsect_size to logical_block_size.

    Signed-off-by: Martin K. Petersen
    Signed-off-by: Jens Axboe

    Martin K. Petersen
     

22 Jul, 2008

2 commits

  • DDR2 memory DIMMs on the Axon could be accessed only as one partition
    when using file system drivers which are using the direct_access() method.
    This patch enables for such file system drivers to access Axon's DDR2 memory
    even if it is splitted in several partitions.

    Signed-off-by: Maxim Shchetynin
    Signed-off-by: Arnd Bergmann
    Signed-off-by: Benjamin Herrenschmidt

    Maxim Shchetynin
     
  • Axonram module registers one block device for each DDR2 DIMM found
    on a system. This means that each DDR2 DIMM becomes its own block device
    major number. This patch lets axonram module to register the only one
    block device for all DDR2 DIMMs which also spares kernel resources.

    Signed-off-by: Maxim Shchetynin
    Signed-off-by: Arnd Bergmann
    Signed-off-by: Benjamin Herrenschmidt

    Maxim Shchetynin
     

28 Apr, 2008

1 commit

  • Alter the block device ->direct_access() API to work with the new
    get_xip_mem() API (that requires both kaddr and pfn are returned).

    Some architectures will not do the right thing in their virt_to_page() for use
    by XIP (to translate from the kernel virtual address returned by
    direct_access(), to a user mappable pfn in XIP's page fault handler.

    However, we can't switch it to just return the pfn and not the kaddr, because
    we have no good way to get a kva from a pfn, and XIP requires the kva for its
    read(2) and write(2) handlers. So we have to return both.

    Signed-off-by: Jared Hulbert
    Signed-off-by: Nick Piggin
    Cc: Carsten Otte
    Cc: Heiko Carstens
    Cc: linux-mm@kvack.org
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Jared Hulbert
     

06 Dec, 2007

1 commit


12 Oct, 2007

1 commit


11 Oct, 2007

1 commit


25 Aug, 2007

2 commits


21 Jul, 2007

1 commit

  • The Axon bridge chip used on new Cell/B.E. based blade servers
    comes with a DDR2 memory controller that can be used to
    attach cheap memory modules, as opposed to the high-speed
    XDR memory that is used by the CPU itself.

    Since the memory controller does not participate in the
    cache coherency protocol, we can not use the memory direcly
    for Linux applications, but by providing a block device
    it can be used for swap space, temporary file storage and
    through the use of the direct_access block device operation
    for mapping into user addresses, when it is mounted with
    an appropriate file system.

    Signed-off-by: Maxim Shchetynin
    Signed-off-by: Arnd Bergmann

    Maxim Shchetynin