27 Mar, 2014

1 commit


11 Mar, 2014

5 commits

  • This patch adds softreset controller for STiH416 SOC, soft reset
    controller is based on system configuration registers which are mapped
    via regmap. This reset controller does not have any feedback or
    acknowledgement. With this patch a new device "st,stih416-softreset" is
    registered with system configuration registers based reset controller
    that controls the softreset state of the hardware such as Ethernet, IRB.

    Signed-off-by: Srinivas Kandagatla
    Acked-by: Philipp Zabel

    Srinivas Kandagatla
     
  • This patch adds softreset controller for STiH415 SOC, soft reset
    controller is based on system configuration registers which are mapped
    via regmap. This reset controller does not have any feedback or
    acknowledgement. With this patch a new device "st,stih415-softreset" is
    registered with system configuration registers based reset controller
    that controls the softreset state of the hardware such as Ethernet, IRB.

    Signed-off-by: Srinivas Kandagatla
    Acked-by: Philipp Zabel

    Srinivas Kandagatla
     
  • This patch adds a reset controller platform driver for the STiH416
    SoC. This initial version provides a compatible driver for the
    "st,stih416-powerdown" device, which registers a system configuration
    register based reset controller that controls the powerdown state of
    hardware such as the on-chip USB host controllers.

    Signed-off-by: Stephen Gallimore
    Signed-off-by: Srinivas Kandagatla
    Acked-by: Philipp Zabel

    Stephen Gallimore
     
  • This patch adds a reset controller platform driver for the STiH415
    SoC. This initial version provides a compatible driver for the
    "st,stih415-powerdown" device, which registers a system configuration
    register based reset controller that controls the powerdown state of
    hardware such as the on-chip USB host controllers.

    Signed-off-by: Stephen Gallimore
    Signed-off-by: Srinivas Kandagatla
    Acked-by: Philipp Zabel

    Stephen Gallimore
     
  • This patch adds a reset controller implementation for STMicroelectronics
    STi family SoCs; it allows a group of related reset like controls found
    in multiple system configuration registers to be represented by a single
    controller device. System configuration registers are accessed through
    the regmap framework and the mfd/syscon driver.

    The implementation optionally supports waiting for the reset action to
    be acknowledged in a separate status register and supports both
    active high and active low reset lines. These properties are common across
    all the reset channels in a specific reset controller instance, hence
    all channels in a paritcular controller are expected to behave in the
    same way.

    Signed-off-by: Stephen Gallimore
    Signed-off-by: Srinivas Kandagatla
    Acked-by: Philipp Zabel

    Stephen Gallimore
     

03 Feb, 2014

3 commits

  • In some cases, you might need to deassert from reset an hardware block that
    doesn't associated to a struct device (CPUs, timers, etc.).

    Add a small helper to retrieve the reset controller from the device tree
    without the need to pass a struct device.

    Signed-off-by: Maxime Ripard
    Signed-off-by: Philipp Zabel

    Maxime Ripard
     
  • Mark function of_reset_simple_xlate() as static in core.c
    because it is not used outside this file.
    Also, remove functions devm_reset_control_put() and
    devm_reset_control_match() because they are unused.

    This eliminates the following warnings in core.c:
    drivers/reset/core.c:46:5: warning: no previous prototype for ‘of_reset_simple_xlate’ [-Wmissing-prototypes]
    drivers/reset/core.c:262:6: warning: no previous prototype for ‘devm_reset_control_put’ [-Wmissing-prototypes]

    Signed-off-by: Rashika Kheria
    Reviewed-by: Josh Triplett
    Signed-off-by: Philipp Zabel

    Rashika Kheria
     
  • If the requested reset controller is not yet available, have reset_control_get
    and device_reset return -EPROBE_DEFER so the driver can decide to request
    probe deferral.

    Signed-off-by: Philipp Zabel
    Acked-by: Shawn Guo
    Reviewed-by: Stephen Warren

    Philipp Zabel
     

23 Nov, 2013

1 commit

  • The Allwinner A31 and most of the other Allwinner SoCs have an IP
    maintaining a few other IPs in the SoC in reset by default. Among these
    IPs are the A31's High Speed Timers, hence why we can't use the regular
    driver construct in every cases, and need to call the registering
    function directly during machine initialisation.

    Apart from this, the implementation is fairly straightforward, and could
    easily be moved to a generic MMIO-based reset controller driver if the
    need ever arise.

    Signed-off-by: Maxime Ripard
    Acked-by: Philipp Zabel

    Maxime Ripard
     

12 Apr, 2013

2 commits