27 Jul, 2020

2 commits


08 Jan, 2020

1 commit


05 Jun, 2019

1 commit

  • Based on 1 normalized pattern(s):

    this program is free software you can redistribute it and or modify
    it under the terms of the gnu general public license as published by
    the free software foundation version 2 of the license this program
    is distributed in the hope that it will be useful but without any
    warranty without even the implied warranty of merchantability or
    fitness for a particular purpose see the gnu general public license
    for more details you should have received a copy of the gnu general
    public license along with this program if not see http www gnu org
    licenses

    extracted by the scancode license scanner the SPDX license identifier

    GPL-2.0-only

    has been chosen to replace the boilerplate/reference in 15 file(s).

    Signed-off-by: Thomas Gleixner
    Reviewed-by: Alexios Zavras
    Reviewed-by: Richard Fontana
    Reviewed-by: Allison Randal
    Cc: linux-spdx@vger.kernel.org
    Link: https://lkml.kernel.org/r/20190530000437.052642892@linutronix.de
    Signed-off-by: Greg Kroah-Hartman

    Thomas Gleixner
     

17 Aug, 2017

1 commit

  • Now that we have a custom printf format specifier, convert users of
    full_name to use %pOF instead. This is preparation to remove storing
    of the full path string for each node.

    Signed-off-by: Rob Herring
    Acked-by: Alexandre Belloni
    Acked-by: Roger Quadros
    Cc: Nicolas Ferre
    Cc: Alexandre Belloni
    Cc: Tony Lindgren
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: linux-omap@vger.kernel.org
    Signed-off-by: Arnd Bergmann

    Rob Herring
     

20 Oct, 2014

1 commit


29 Apr, 2014

5 commits

  • Currently, the mvebu-devbus Device Tree binding makes defining the
    timing parameters mandatory.

    However, in practice, when converting Orion5x platforms to the Device
    Tree, we may not necessarily have easy access to the hardware
    platforms to fetch those values which were not defined in old-style
    board files: all these platforms rely on the bootloader setting the
    timing parameters correctly.

    In order to facilitate the migration to the Device Tree of this
    platform, this commit relaxes the mvebu-devbus Device Tree binding by
    introducing a 'devbus,keep-config' boolean property, which, if
    defined, will ignore all timing parameters passed in the Device Tree,
    and simply rely on the timing values already defined by the
    bootloader.

    Signed-off-by: Thomas Petazzoni
    Acked-by: Sebastian Hesselbarth
    Tested-by: Ezequiel Garcia
    Link: https://lkml.kernel.org/r/1398202002-28530-10-git-send-email-thomas.petazzoni@free-electrons.com
    Signed-off-by: Jason Cooper

    Thomas Petazzoni
     
  • This commit adds support for the Orion5x family of Marvell processors
    into the mvebu-devbus driver. It differs from the already supported
    Armada 370/XP by:

    * Having a single register (instead of two) for doing all the timing
    configuration.

    * Having a few less timing configuration parameters.

    For this reason, a separate compatible string "marvell,orion-devbus"
    is introduced.

    Signed-off-by: Thomas Petazzoni
    Acked-by: Sebastian Hesselbarth
    Tested-by: Ezequiel Garcia
    Link: https://lkml.kernel.org/r/1398202002-28530-9-git-send-email-thomas.petazzoni@free-electrons.com
    Signed-off-by: Jason Cooper

    Thomas Petazzoni
     
  • The mvebu-devbus driver currently only supports the Armada 370/XP
    family, but it can also cover the Orion5x family. However, the Orion5x
    family has a different organization of the registers.

    Therefore, in preparation to the introduction of Orion5x support, we
    separate into two functions the code that 1/ retrieves the timing
    parameters from the Device Tree and 2/ applies those timings
    parameters into the hardware registers.

    Signed-off-by: Thomas Petazzoni
    Acked-by: Sebastian Hesselbarth
    Tested-by: Ezequiel Garcia
    Link: https://lkml.kernel.org/r/1398202002-28530-8-git-send-email-thomas.petazzoni@free-electrons.com
    Signed-off-by: Jason Cooper

    Thomas Petazzoni
     
  • As noted by Sebastian Hesselbarth, the definitions in mvebu-devbus.c
    are not bit definition, but rather shift values, so a _SHIFT prefix
    would make more sense. This commit therefore replaces the *_BIT
    definitions by *_SHIFT definitions.

    Signed-off-by: Thomas Petazzoni
    Acked-by: Sebastian Hesselbarth
    Tested-by: Ezequiel Garcia
    Link: https://lkml.kernel.org/r/1398202002-28530-7-git-send-email-thomas.petazzoni@free-electrons.com
    Signed-off-by: Jason Cooper

    Thomas Petazzoni
     
  • The mvebu-devbus driver currently only supports the Armada 370/XP
    family, but it can also cover the Orion5x family. However, the Orion5x
    family has a different organization of the register. Therefore, in
    preparation to the introduction of Orion5x support, we rename the
    Armada 370/XP specific definitions to have an ARMADA_ prefix.

    Signed-off-by: Thomas Petazzoni
    Acked-by: Sebastian Hesselbarth
    Tested-by: Ezequiel Garcia
    Link: https://lkml.kernel.org/r/1398202002-28530-6-git-send-email-thomas.petazzoni@free-electrons.com
    Signed-off-by: Jason Cooper

    Thomas Petazzoni
     

17 Apr, 2014

1 commit

  • According to the Armada 370 and Armada XP datasheets, the part of the
    Device Bus register that configure the bus width should contain 0 for
    a 8 bits bus width, and 1 for a 16 bits bus width (other values are
    unsupported/reserved).

    However, the current conversion done in the driver to convert from a
    bus width in bits to the value expected by the register leads to
    setting the register to 1 for a 8 bits bus, and 2 for a 16 bits bus.

    This mistake was compensated by a mistake in the existing Device Tree
    files for Armada 370/XP platforms: they were declaring a 8 bits bus
    width, while the hardware in fact uses a 16 bits bus width.

    This commit fixes that by adjusting the conversion logic.

    This patch fixes a bug that was introduced in
    3edad321b1bd2e6c8b5f38146c115c8982438f06 ('drivers: memory: Introduce
    Marvell EBU Device Bus driver'), which was merged in v3.11.

    Signed-off-by: Thomas Petazzoni
    Link: https://lkml.kernel.org/r/1397489361-5833-2-git-send-email-thomas.petazzoni@free-electrons.com
    Fixes: 3edad321b1bd ('drivers: memory: Introduce Marvell EBU Device Bus driver')
    Cc: stable@vger.kernel.org # v3.11+
    Acked-by: Ezequiel Garcia
    Acked-by: Gregory CLEMENT
    Signed-off-by: Jason Cooper

    Thomas Petazzoni
     

13 Aug, 2013

1 commit

  • This variable is not being used anywhere and it's only forgotten
    garbage that should have been removed in the previous commit:

    commit 9b6e4c0a58e24c28bd757c9365824a37e80b751c
    Author: Ezequiel Garcia
    Date: Fri Jul 26 10:17:38 2013 -0300

    memory: mvebu-devbus: Remove address decoding window workaround

    Signed-off-by: Ezequiel Garcia
    Signed-off-by: Jason Cooper

    Ezequiel Garcia
     

06 Aug, 2013

1 commit

  • Now that mbus device tree binding has been introduced, remove the address
    decoding window management from this driver.
    A suitable 'ranges' entry should be added to the devbus-compatible node in
    the device tree, as described by the mbus binding documentation.

    Acked-by: Greg Kroah-Hartman
    Signed-off-by: Ezequiel Garcia
    Tested-by: Andrew Lunn
    Tested-by: Sebastian Hesselbarth
    Signed-off-by: Jason Cooper

    Ezequiel Garcia
     

22 May, 2013

1 commit

  • Marvell EBU SoCs such as Armada 370/XP, Orion5x (88f5xxx) and
    Discovery (mv78xx0) supports a Device Bus controller to access several
    kinds of memories and I/O devices (NOR, NAND, SRAM, FPGA).

    This commit adds a driver to handle this controller. So far only
    Armada 370, Armada XP and Discovery SoCs are supported.

    The driver must be registered through a device tree node;
    as explained in the binding document.

    For each child node in the device tree, this driver will:
    * set timing parameters
    * register a child device
    * setup an address decoding window, using the mbus driver

    Keep in mind the address decoding window setup is only a temporary hack.
    This code will be removed from this devbus driver as soon as a proper device
    tree binding for the mbus driver is added.

    Signed-off-by: Ezequiel Garcia
    Acked-by: Arnd Bergmann
    Acked-by: Jason Cooper
    Signed-off-by: Greg Kroah-Hartman

    Ezequiel Garcia