14 Oct, 2015

1 commit


11 Mar, 2014

1 commit

  • None of these files are actually using any __init type directives
    and hence don't need to include . Most are just a
    left over from __devinit and __cpuinit removal, or simply due to
    code getting copied from one driver to the next.

    Cc: David Woodhouse
    Cc: Brian Norris
    Cc: linux-mtd@lists.infradead.org
    Signed-off-by: Paul Gortmaker
    [Brian: dropped one incorrect hunk]
    Signed-off-by: Brian Norris

    Paul Gortmaker
     

31 Aug, 2013

1 commit


06 Aug, 2013

1 commit

  • The driver core clears the driver data to NULL after device_release
    or on probe failure, since commit 0998d0631001288a5974afc0b2a5f568bcdecb4d
    (device-core: Ensure drvdata = NULL when no driver is bound).
    Thus, it is not needed to manually clear the device driver data to NULL.

    Signed-off-by: Jingoo Han
    Signed-off-by: Artem Bityutskiy
    Signed-off-by: David Woodhouse

    Jingoo Han
     

22 Nov, 2012

2 commits


27 Mar, 2012

1 commit

  • The first 3 arguments of 'mtd_device_parse_register()' are pointers,
    but many callers pass '0' instead of 'NULL'. Fix this globally. Thanks
    to coccinelle for making it easy to do with the following semantic patch:

    @@
    expression mtd, types, parser_data, parts, nr_parts;
    @@
    (
    -mtd_device_parse_register(mtd, 0, parser_data, parts, nr_parts)
    +mtd_device_parse_register(mtd, NULL, parser_data, parts, nr_parts)
    |
    -mtd_device_parse_register(mtd, types, 0, parts, nr_parts)
    +mtd_device_parse_register(mtd, types, NULL, parts, nr_parts)
    |
    -mtd_device_parse_register(mtd, types, parser_data, 0, nr_parts)
    +mtd_device_parse_register(mtd, types, parser_data, NULL, nr_parts)
    )

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

    Artem Bityutskiy
     

10 Jan, 2012

1 commit


11 Sep, 2011

2 commits


25 May, 2011

1 commit


11 Mar, 2011

1 commit

  • OMAP-L137/AM17x has limited number of dedicated EMIFA
    address pins, enough to interface directly to an SDRAM.
    If a device such as an asynchronous flash needs to be
    attached to the EMIFA, then either GPIO pins or a chip
    select may be used to control the flash device's upper
    address lines.

    This patch adds support for the NOR flash on the OMAP-L137/
    AM17x user interface daughter board using the latch-addr-flash
    MTD mapping driver which allows flashes to be partially
    physically addressed. The upper address lines are set by
    a board specific code which is a separate patch.

    Signed-off-by: David Griego
    Signed-off-by: Aleksey Makarov
    Signed-off-by: Sergei Shtylyov
    Signed-off-by: Savinay Dharmappa
    Signed-off-by: Artem Bityutskiy
    Signed-off-by: David Woodhouse

    David Griego