summaryrefslogtreecommitdiffstats
path: root/drivers/soc/tegra/fuse/fuse-tegra30.c
diff options
context:
space:
mode:
authorOlof Johansson <olof@lixom.net>2018-01-04 22:52:06 -0800
committerOlof Johansson <olof@lixom.net>2018-01-04 22:52:06 -0800
commit3864a53e14591c2df710d28dbe8ba1914a9689ed (patch)
treeca23160506fbb9594d9d84a5ec262a0955f16863 /drivers/soc/tegra/fuse/fuse-tegra30.c
parent33f0624c6a4d808d3a04beac40638375d789ed2e (diff)
parent91c719f5ec6671f7b63762d78897af5583dd7693 (diff)
downloadtalos-obmc-linux-3864a53e14591c2df710d28dbe8ba1914a9689ed.tar.gz
talos-obmc-linux-3864a53e14591c2df710d28dbe8ba1914a9689ed.zip
Merge tag 'renesas-soc2-for-v4.16' of https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas into next/soc
Second Round of Renesas ARM Based SoC Updates for v4.16 * rcar-sysc: Keep wakeup sources active during system suspend Geert Uytterhoeven says "If an R-Car SYSC slave device is part of the CPG/MSTP or CPG/MSSR Clock Domain and to be used as a wakeup source, it must be kept active during system suspend. Currently this is handled in device-specific drivers by explicitly increasing the use count of the module clock when the device is configured as a wakeup source. However, the proper way to prevent the device from being stopped is to inform this requirement to the genpd core, by setting the GENPD_FLAG_ACTIVE_WAKEUP flag. Note that this will only affect devices configured as wakeup sources." * tag 'renesas-soc2-for-v4.16' of https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas: soc: renesas: rcar-sysc: Keep wakeup sources active during system suspend Signed-off-by: Olof Johansson <olof@lixom.net>
Diffstat (limited to 'drivers/soc/tegra/fuse/fuse-tegra30.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud