19 Jun, 2015

1 commit

  • The crypto SRAM, used by the armada 370 cpuidle code to workaround a bug
    in the BootROM code, requires the crypto clk to be up and running.
    Flag the crypto clk as IGNORE_UNUSED until we add the proper
    infrastructure to define the crypto SRAM in the DT and reference the crypto
    clk in this SRAM node.

    Reported-by: Kevin Hilman
    Signed-off-by: Boris Brezillon
    Tested-by: Kevin Hilman
    Signed-off-by: Michael Turquette

    Boris Brezillon
     

04 Jun, 2015

1 commit

  • Even if not documented in the datasheet, the Armada 370 SoC can actually
    gate the CESA (crypto engine) clock.
    Add an entry in the gating_desc table to be able to reference the CESA
    gateclk in the crypto node.

    Signed-off-by: Boris Brezillon
    Acked-by: Gregory CLEMENT
    Signed-off-by: Michael Turquette

    Boris Brezillon
     

09 Sep, 2014

1 commit

  • This commit activates the SSCG deviation correction for the Armada
    370. It uses the optional function introduced by the commit "clk:
    mvebu: Fix clk frequency value if SSCG is enabled".

    Without this fix the deviation measured on a Mirabox was of a few
    second each hour, whereas with this fix it was reduced at around
    50ppm (around 4s per day).

    Signed-off-by: Gregory CLEMENT
    Tested-by: Leigh Brown
    Link: https://lkml.kernel.org/r/1409645719-20003-3-git-send-email-gregory.clement@free-electrons.com
    Signed-off-by: Jason Cooper

    Gregory CLEMENT
     

07 Feb, 2014

1 commit

  • Init order of CLK_OF_DECLARE'd drivers depends on compile order.
    Unfortunately, clk_of_init does not allow drivers to return errors,
    e.g. -EPROBE_DEFER if parent clocks have not been registered, yet.

    To avoid init order woes for MVEBU clock drivers, we take care of
    proper init order ourselves. This patch joins core-clk and gating-clk
    init to maintain proper init order.

    Signed-off-by: Sebastian Hesselbarth
    Tested-by: Ezequiel Garcia
    Signed-off-by: Jason Cooper

    Sebastian Hesselbarth
     

07 Oct, 2013

1 commit

  • This patch fixes the tclk frequency array for the Armada-370 SoC.
    This bug has been introduced by commit 6b72333d
    ("clk: mvebu: add Armada 370 SoC-centric clock init").

    A wrong tclk frequency affects the following drivers: mvsdio, mvneta,
    i2c-mv64xxx and mvebu-devbus. This list may be incomplete.

    About the mvneta Ethernet driver, note that the tclk frequency is used
    to compute the Rx time coalescence. Then, this bug harms the coalescence
    configuration and also degrades the networking performances with the
    default values.

    Signed-off-by: Simon Guinot
    Cc: Andrew Lunn
    Cc: Gregory CLEMENT
    Cc: Sebastian Hesselbarth
    Acked-by: Jason Cooper
    Cc: stable@vger.kernel.org
    Signed-off-by: Michael Turquette

    Simon Guinot
     

28 Aug, 2013

1 commit


30 May, 2013

1 commit