platform/kernel/linux-exynos.git
5 years agoASoC: samsung: i2s: Add widgets and routes for DPCM support 44/197844/5
Sylwester Nawrocki [Tue, 12 Feb 2019 18:03:24 +0000 (19:03 +0100)]
ASoC: samsung: i2s: Add widgets and routes for DPCM support

This patch adds DAPM widgets required to model the internal mixer
of the I2S controller merging audio streams from the primary and
from the secondary PCM interface.

Change-Id: I3cb7b1b17f0c6891f6edb638db97ca6a482cec4b
Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Signed-off-by: Mark Brown <broonie@kernel.org>
5 years agoASoC: samsung: i2s: Move clk supplier data to common driver data structure 43/197843/5
Sylwester Nawrocki [Tue, 12 Feb 2019 18:03:23 +0000 (19:03 +0100)]
ASoC: samsung: i2s: Move clk supplier data to common driver data structure

Having the clocks provider data in struct samsung_i2s_priv, i.e. per the I2S
controller instance, rather than per CPU DAI better models the hardware and
simplifies the code a little. The clock provider is common for both DAIs.

Change-Id: I76db45001d8303263405b2cc40526e4101f35d16
Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Signed-off-by: Mark Brown <broonie@kernel.org>
5 years agoASoC: samsung: i2s: Restore support for the secondary PCM 42/197842/5
Sylwester Nawrocki [Tue, 12 Feb 2019 18:03:22 +0000 (19:03 +0100)]
ASoC: samsung: i2s: Restore support for the secondary PCM

This patch introduces again registration of additional platform device as
we still need it for registering the secondary dmaengine PCM component.

This patch in most part is a revert of changes done in commit
be2c92eb64023e ("ASoC: samsung: i2s: Remove virtual device for secondary DAI")

Change-Id: Ib7a47c83511403b32e04c41edf8148d77481abb3
Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Signed-off-by: Mark Brown <broonie@kernel.org>
5 years agoASoC: samsung: i2s: Convert to single component with multiple DAIs 41/197841/5
Sylwester Nawrocki [Thu, 7 Feb 2019 17:00:13 +0000 (18:00 +0100)]
ASoC: samsung: i2s: Convert to single component with multiple DAIs

This patch includes minimal changes as a prerequisite for adding support
for the Exynos secondary I2S interface as second DAI of the I2S component.
Doing it that way allows to avoid problems as indicated in commmit
6b01e0365b1689 ("ASoC: samsung: i2s: disable secondary DAI until it gets fixed")

The samsung_i2s_get_pri_dai() helper added in this patch is temporary and
will be removed in one of subsequent patches.

Change-Id: I5cb8ff7cb13a144bc6944752081b93a847080f94
Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Signed-off-by: Mark Brown <broonie@kernel.org>
5 years agoASoC: samsung: dmaengine: Allow to specify custom DMA device 39/197839/5
Sylwester Nawrocki [Thu, 7 Feb 2019 17:00:11 +0000 (18:00 +0100)]
ASoC: samsung: dmaengine: Allow to specify custom DMA device

The additional function argument will allow to select proper DMA device
for requesting DMA channel for the secondary CPU DAI.

Change-Id: I3848594e393bcf55770020857ee5f2d0271b779b
Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Signed-off-by: Mark Brown <broonie@kernel.org>
5 years agoASoC: dmaengine: Extend use of chan_names provided in custom DMA config 38/197838/5
Sylwester Nawrocki [Thu, 7 Feb 2019 17:00:10 +0000 (18:00 +0100)]
ASoC: dmaengine: Extend use of chan_names provided in custom DMA config

There are currently two ways to specify custom DMA channel names:
 - through the SND_DMAENGINE_PCM_FLAG_CUSTOM_CHANNEL_NAME flag and
   snd_dmaengine_dai_dma_data data structure,
 - through chan_names field of struct snd_dmaengine_pcm_config.

In order to replace the DAI DMA data method with the custom DMA config
one on non-DT platforms the dmaengine_pcm_new() function is extended
to also consider channel names specified in the custom DMA config.
If both config->chan_names and dma_data->chan_name are provided
the former will be used.

Change-Id: I6a325754971c7d4daf3141f3cfeede9280d9941c
Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Signed-off-by: Mark Brown <broonie@kernel.org>
5 years agoASoC: dmaengine: Improve of_node test in dmaengine_pcm_request_chan_of() 37/197837/5
Sylwester Nawrocki [Thu, 7 Feb 2019 17:00:09 +0000 (18:00 +0100)]
ASoC: dmaengine: Improve of_node test in dmaengine_pcm_request_chan_of()

Currently when of_node of the "PCM" device is null
dmaengine_pcm_request_chan_of() function will bail out, including cases
when custom DMA device is intended to be used.  To have the channels
properly requested when custom DMA device is provided extend the of_node
test to also consider dma_dev->of_node.

Change-Id: Icac9da759fdefa367492f5d0ad0ff031a7b0bb62
Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Signed-off-by: Mark Brown <broonie@kernel.org>
5 years agoASoC: samsung: i2s: Fix prescaler setting for the secondary DAI 40/197840/5
Sylwester Nawrocki [Thu, 7 Feb 2019 17:00:12 +0000 (18:00 +0100)]
ASoC: samsung: i2s: Fix prescaler setting for the secondary DAI

Make sure i2s->rclk_srcrate is properly initialized also during
playback through the secondary DAI.

Change-Id: Ic27fe0b834379a95485668137eee1e7d22d93952
Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Signed-off-by: Mark Brown <broonie@kernel.org>
5 years agoASoC: samsung: Prevent clk_get_rate() calls in atomic context 33/200633/2
Sylwester Nawrocki [Thu, 7 Feb 2019 14:20:41 +0000 (15:20 +0100)]
ASoC: samsung: Prevent clk_get_rate() calls in atomic context

This patch moves clk_get_rate() call from trigger() to hw_params()
callback to avoid calling sleeping clk API from atomic context
and prevent deadlock as indicated below.

Before this change clk_get_rate() was being called with same
spinlock held as the one passed to the clk API when registering
clocks exposed by the I2S driver.

[   82.109780] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:908
[   82.117009] in_atomic(): 1, irqs_disabled(): 128, pid: 1554, name: speaker-test
[   82.124235] 3 locks held by speaker-test/1554:
[   82.128653]  #0: cc8c5328 (snd_pcm_link_rwlock){...-}, at: snd_pcm_stream_lock_irq+0x20/0x38
[   82.137058]  #1: ec9eda17 (&(&substream->self_group.lock)->rlock){..-.}, at: snd_pcm_ioctl+0x900/0x1268
[   82.146417]  #2: 6ac279bf (&(&pri_dai->spinlock)->rlock){..-.}, at: i2s_trigger+0x64/0x6d4
[   82.154650] irq event stamp: 8144
[   82.157949] hardirqs last  enabled at (8143): [<c0a0f574>] _raw_read_unlock_irq+0x24/0x5c
[   82.166089] hardirqs last disabled at (8144): [<c0a0f6a8>] _raw_read_lock_irq+0x18/0x58
[   82.174063] softirqs last  enabled at (8004): [<c01024e4>] __do_softirq+0x3a4/0x66c
[   82.181688] softirqs last disabled at (7997): [<c012d730>] irq_exit+0x140/0x168
[   82.188964] Preemption disabled at:
[   82.188967] [<00000000>]   (null)
[   82.195728] CPU: 6 PID: 1554 Comm: speaker-test Not tainted 5.0.0-rc5-00192-ga6e6caca8f03 #191
[   82.204302] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[   82.210376] [<c0111a54>] (unwind_backtrace) from [<c010d8f4>] (show_stack+0x10/0x14)
[   82.218084] [<c010d8f4>] (show_stack) from [<c09ef004>] (dump_stack+0x90/0xc8)
[   82.225278] [<c09ef004>] (dump_stack) from [<c0152980>] (___might_sleep+0x22c/0x2c8)
[   82.232990] [<c0152980>] (___might_sleep) from [<c0a0a2e4>] (__mutex_lock+0x28/0xa3c)
[   82.240788] [<c0a0a2e4>] (__mutex_lock) from [<c0a0ad80>] (mutex_lock_nested+0x1c/0x24)
[   82.248763] [<c0a0ad80>] (mutex_lock_nested) from [<c04923dc>] (clk_prepare_lock+0x78/0xec)
[   82.257079] [<c04923dc>] (clk_prepare_lock) from [<c049538c>] (clk_core_get_rate+0xc/0x5c)
[   82.265309] [<c049538c>] (clk_core_get_rate) from [<c0766b18>] (i2s_trigger+0x490/0x6d4)
[   82.273369] [<c0766b18>] (i2s_trigger) from [<c074fec4>] (soc_pcm_trigger+0x100/0x140)
[   82.281254] [<c074fec4>] (soc_pcm_trigger) from [<c07378a0>] (snd_pcm_do_start+0x2c/0x30)
[   82.289400] [<c07378a0>] (snd_pcm_do_start) from [<c07376cc>] (snd_pcm_action_single+0x38/0x78)
[   82.298065] [<c07376cc>] (snd_pcm_action_single) from [<c073a450>] (snd_pcm_ioctl+0x910/0x1268)
[   82.306734] [<c073a450>] (snd_pcm_ioctl) from [<c0292344>] (do_vfs_ioctl+0x90/0x9ec)
[   82.314443] [<c0292344>] (do_vfs_ioctl) from [<c0292cd4>] (ksys_ioctl+0x34/0x60)
[   82.321808] [<c0292cd4>] (ksys_ioctl) from [<c0101000>] (ret_fast_syscall+0x0/0x28)
[   82.329431] Exception stack(0xeb875fa8 to 0xeb875ff0)
[   82.334459] 5fa0:                   00033c18 b6e31000 00000004 00004142 00033d80 00033d80
[   82.342605] 5fc0: 00033c18 b6e31000 00008000 00000036 00008000 00000000 beea38a8 00008000
[   82.350748] 5fe0: b6e3142c beea384c b6da9a30 b6c9212c
[   82.355789]
[   82.357245] ======================================================
[   82.363397] WARNING: possible circular locking dependency detected
[   82.369551] 5.0.0-rc5-00192-ga6e6caca8f03 #191 Tainted: G        W
[   82.376395] ------------------------------------------------------
[   82.382548] speaker-test/1554 is trying to acquire lock:
[   82.387834] 6d2007f4 (prepare_lock){+.+.}, at: clk_prepare_lock+0x78/0xec
[   82.394593]
[   82.394593] but task is already holding lock:
[   82.400398] 6ac279bf (&(&pri_dai->spinlock)->rlock){..-.}, at: i2s_trigger+0x64/0x6d4
[   82.408197]
[   82.408197] which lock already depends on the new lock.
[   82.416343]
[   82.416343] the existing dependency chain (in reverse order) is:
[   82.423795]
[   82.423795] -> #1 (&(&pri_dai->spinlock)->rlock){..-.}:
[   82.430472]        clk_mux_set_parent+0x34/0xb8
[   82.434975]        clk_core_set_parent_nolock+0x1c4/0x52c
[   82.440347]        clk_set_parent+0x38/0x6c
[   82.444509]        of_clk_set_defaults+0xc8/0x308
[   82.449186]        of_clk_add_provider+0x84/0xd0
[   82.453779]        samsung_i2s_probe+0x408/0x5f8
[   82.458376]        platform_drv_probe+0x48/0x98
[   82.462879]        really_probe+0x224/0x3f4
[   82.467037]        driver_probe_device+0x70/0x1c4
[   82.471716]        bus_for_each_drv+0x44/0x8c
[   82.476049]        __device_attach+0xa0/0x138
[   82.480382]        bus_probe_device+0x88/0x90
[   82.484715]        deferred_probe_work_func+0x6c/0xbc
[   82.489741]        process_one_work+0x200/0x740
[   82.494246]        worker_thread+0x2c/0x4c8
[   82.498408]        kthread+0x128/0x164
[   82.502131]        ret_from_fork+0x14/0x20
[   82.506204]          (null)
[   82.508976]
[   82.508976] -> #0 (prepare_lock){+.+.}:
[   82.514264]        __mutex_lock+0x60/0xa3c
[   82.518336]        mutex_lock_nested+0x1c/0x24
[   82.522756]        clk_prepare_lock+0x78/0xec
[   82.527088]        clk_core_get_rate+0xc/0x5c
[   82.531421]        i2s_trigger+0x490/0x6d4
[   82.535494]        soc_pcm_trigger+0x100/0x140
[   82.539913]        snd_pcm_do_start+0x2c/0x30
[   82.544246]        snd_pcm_action_single+0x38/0x78
[   82.549012]        snd_pcm_ioctl+0x910/0x1268
[   82.553345]        do_vfs_ioctl+0x90/0x9ec
[   82.557417]        ksys_ioctl+0x34/0x60
[   82.561229]        ret_fast_syscall+0x0/0x28
[   82.565477]        0xbeea384c
[   82.568421]
[   82.568421] other info that might help us debug this:
[   82.568421]
[   82.576394]  Possible unsafe locking scenario:
[   82.576394]
[   82.582285]        CPU0                    CPU1
[   82.586792]        ----                    ----
[   82.591297]   lock(&(&pri_dai->spinlock)->rlock);
[   82.595977]                                lock(prepare_lock);
[   82.601782]                                lock(&(&pri_dai->spinlock)->rlock);
[   82.608975]   lock(prepare_lock);
[   82.612268]
[   82.612268]  *** DEADLOCK ***

Fixes: 647d04f8e07a ("ASoC: samsung: i2s: Ensure the RCLK rate is properly determined")
Change-Id: I1b8100d4e65a1d9964aa92d2ac56965a01359791
Reported-by: Krzysztof Kozłowski <krzk@kernel.org>
Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
5 years agoASoC: Revert "LOCAL / temporary workaround for i2s/prepare_lock deadlock" 32/200632/2
Sylwester Nawrocki [Wed, 27 Feb 2019 09:54:37 +0000 (10:54 +0100)]
ASoC: Revert "LOCAL / temporary workaround for i2s/prepare_lock deadlock"

This reverts commit a146d53312cc7151d7aa5d517b808d2d1fdfd6c1.

Revert temporarily in order to apply patches from the mainline
cleanly.

Change-Id: I2cce77968974c36d8ccbe4b2df75b77113e6d5bf
Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
5 years agogpu/drm: Fix lock held when returning to user space. 82/200682/1
Tetsuo Handa [Thu, 10 Jan 2019 10:19:31 +0000 (19:19 +0900)]
gpu/drm: Fix lock held when returning to user space.

We need to call drm_modeset_acquire_fini() when drm_atomic_state_alloc()
failed or call drm_modeset_acquire_init() after drm_atomic_state_alloc()
succeeded.

Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Reported-by: syzbot <syzbot+6ea337c427f5083ebdf2@syzkaller.appspotmail.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Link: https://patchwork.freedesktop.org/patch/msgid/1547115571-21219-1-git-send-email-penguin-kernel@I-love.SAKURA.ne.jp
[hoegeun.kwon: this patch from the mainline 4089e272ac61 and it has been
 modified to be able to backport linux-v4.14.]
Change-Id: Iaa0d6e104054abc11181c43bdb6283a8bd30eb19
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>
5 years agoARM: configs: tizen_odroid: Increase CMA size to 256 MB 55/200655/1
Sylwester Nawrocki [Wed, 27 Feb 2019 13:50:08 +0000 (14:50 +0100)]
ARM: configs: tizen_odroid: Increase CMA size to 256 MB

This change is required for video decoding through gst-omx plugin.

Change-Id: I1b13280bb94bb0314c7f5c7bd1d8a4f77d829a36
Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
5 years agobase/firmware retry firmware load after rootfs mount 63/200163/2
Christoph Manszewski [Fri, 15 Feb 2019 14:50:00 +0000 (15:50 +0100)]
base/firmware retry firmware load after rootfs mount

Return -EPROBE_DEFER for request_firmware() until root filesystem is
mounted. In case of request_firmware_nowait() create a list of deferred
firmware load requests, and retry firmware load after root filesytem is
mounted.

This allows to have wifi drivers build into the kernel, but
the firmware files shipped on the root filesystem.

Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Signed-off-by: Christoph Manszewski <c.manszewski@samsung.com>
Change-Id: I40c0a2a98ca9b1a95fb743a848d2366250cae839

5 years agoRevert "[LOCAL] base/firmware: return -EPROBE_DEFER until rootfs is available" 62/200162/2
Christoph Manszewski [Fri, 15 Feb 2019 14:35:26 +0000 (15:35 +0100)]
Revert "[LOCAL] base/firmware: return -EPROBE_DEFER until rootfs is available"

This reverts commit 1733ede82e9e964a3d5234ef61979ca523e7ba5a.

Signed-off-by: Christoph Manszewski <c.manszewski@samsung.com>
Change-Id: I30441cbd9b4933cab7e1cb6e80d767e4fca65f41

5 years agoARM: dts: Disable UHS-I modes for SD card on Odroid XU3/XU4/HC1 98/200398/3
Marek Szyprowski [Fri, 22 Feb 2019 15:16:31 +0000 (16:16 +0100)]
ARM: dts: Disable UHS-I modes for SD card on Odroid XU3/XU4/HC1

Ultra High Speed DDR50+ modes doesn't work stable on the tested Odroid XU3
and XU4 boards, so disable them until the proper solution is developed.

This is equal to the revert of the following commits:

"ARM: dts: exynos: Update maximum frequency for SD card to 200MHz on Odroid XU3/XU4/HC1"
"ARM: dts: exynos: Add UHS-I bus speed support to Odroid XU3/XU4/HC1"

This reverts commit 6d92b6cece561306a707e40a264b802b51d4264c.
This reverts commit f3e8e10898d0efee73ad0108dec9f3a0947da752.

Tested-by: Kamil Konieczny <k.konieczny@partner.samsung.com>
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: I210c64cb5d34597132341caa6b98a01fa6a8397c

5 years agoARM64: defconfig: tm2: Sync with savedefconfig 91/200091/1
Junghoon Kim [Tue, 19 Feb 2019 05:16:33 +0000 (14:16 +0900)]
ARM64: defconfig: tm2: Sync with savedefconfig

Sync the tizen_tm2_defconfig with savedefconfig. Currently, whenever
rebasing the kernel tree, it requires to update the kernel version in
the defconfig file. This patch helps to avoid the above step.

Change-Id: I3fa02794b552411aa15363bcbd27f4e370d668f6
Signed-off-by: Junghoon Kim <jhoon20.kim@samsung.com>
5 years agoARM: defconfig: ordoid: Sync with savedefconfig 90/200090/1
Junghoon Kim [Tue, 19 Feb 2019 04:54:58 +0000 (13:54 +0900)]
ARM: defconfig: ordoid: Sync with savedefconfig

Sync the tizen_odroid_defconfig with savedefconfig. Whenever rebasing
the kernel tree, it requires to update the kernel version in the
defconfig file. This patch helps to avoid the above step.

Change-Id: I3bd1794ac58a4b0688134f416d33494a80764dcf
Signed-off-by: Junghoon Kim <jhoon20.kim@samsung.com>
5 years agoARM: dts: exynos4412-odroid-common: add mmc aliases to set fixed mmc index 90/199890/2
Seung-Woo Kim [Fri, 15 Feb 2019 08:26:11 +0000 (17:26 +0900)]
ARM: dts: exynos4412-odroid-common: add mmc aliases to set fixed mmc index

Add mmc aliases to set fixed mmc index to emmc and sdcard.

Change-Id: I2a826442e86222cd0c6542c962e2c4187dad6c76
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
5 years agommc: block: Support the fixed index for mmcblk with aliases nodes 89/199889/2
Jaehoon Chung [Tue, 29 Mar 2016 10:43:34 +0000 (19:43 +0900)]
mmc: block: Support the fixed index for mmcblk with aliases nodes

Now, index of mmcblk is allocated in accordance with probing time.
If want to use the mmcblk1 for some device, it can use alias.

aliases {
mmc0 = &mmc0; /* mmcblk0 for eMMC */
mmc1 = &mmc2; /* mmcblk1 for SD */
mmc2 = &mmc1; /* mmcblk2 for SDIO*/
};

If there are no corresponding values, it might be allocated with
existing scheme.

Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
[sw0312.kim: port to v4.14
 - apply to host index instead of name_idx because host index is used in this version
]
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
Change-Id: I44673d62e546ea0aeedd9cac314dbfd31fdcce66

5 years agoARM: pm: fix HYP/SVC mode mismatch when MCPM is used 89/199789/3
Marek Szyprowski [Wed, 13 Feb 2019 12:02:25 +0000 (13:02 +0100)]
ARM: pm: fix HYP/SVC mode mismatch when MCPM is used

MCPM does a soft reset of the CPUs and uses common cpu_resume() routine to
perform low-level platform initialization. This results in a try to install
HYP stubs for the second time for each CPU and results in false HYP/SVC
mode mismatch detection. The HYP stubs are already installed at the
beginning of the kernel initialization on the boot CPU (head.S) or in the
secondary_startup() for other CPUs. To fix this issue MCPM code should use
a cpu_resume() routine without HYP stubs installation.

This change fixes HYP/SVC mode mismatch on Samsung Exynos5422-based Odroid
XU3/XU4/HC1 boards.

Fixes: 3721924c8154 ("ARM: 8081/1: MCPM: provide infrastructure to allow for MCPM loopback")
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Acked-by: Nicolas Pitre <nico@linaro.org>
Tested-by: Anand Moon <linux.amoon@gmail.com>
Change-Id: I6f6225fd2a7e57e323010af616a6fdd4774a7222

5 years agoARM: exynos: Fix undefined instruction during Exynos5422 resume 88/199788/2
Marek Szyprowski [Thu, 14 Feb 2019 10:12:46 +0000 (11:12 +0100)]
ARM: exynos: Fix undefined instruction during Exynos5422 resume

During early system resume on Exynos5422 with performance counters enabled
the following kernel oops happens:

Internal error: Oops - undefined instruction: 0 [#1] PREEMPT SMP ARM
Modules linked in:
CPU: 0 PID: 1433 Comm: bash Tainted: G        W         5.0.0-rc5-next-20190208-00023-gd5fb5a8a13e6-dirty #5480
Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
PC is at reset_ctrl_regs+0x128/0x354
LR is at reset_ctrl_regs+0x124/0x354
pc : [<c0112814>]    lr : [<c0112810>]    psr: 600001d3
...
Flags: nZCv  IRQs off  FIQs off  Mode SVC_32  ISA ARM  Segment none
Control: 10c5387d  Table: 4451006a  DAC: 00000051
Process bash (pid: 1433, stack limit = 0xb7e0e22f)
...
[<c0112814>] (reset_ctrl_regs) from [<c0112ad0>] (dbg_cpu_pm_notify+0x1c/0x24)
[<c0112ad0>] (dbg_cpu_pm_notify) from [<c014c840>] (notifier_call_chain+0x44/0x84)
[<c014c840>] (notifier_call_chain) from [<c014cbc0>] (__atomic_notifier_call_chain+0x7c/0x128)
[<c014cbc0>] (__atomic_notifier_call_chain) from [<c01ffaac>] (cpu_pm_notify+0x30/0x54)
[<c01ffaac>] (cpu_pm_notify) from [<c055116c>] (syscore_resume+0x98/0x3f4)
[<c055116c>] (syscore_resume) from [<c0189350>] (suspend_devices_and_enter+0x97c/0xe74)
[<c0189350>] (suspend_devices_and_enter) from [<c0189fb8>] (pm_suspend+0x770/0xc04)
[<c0189fb8>] (pm_suspend) from [<c0187740>] (state_store+0x6c/0xcc)
[<c0187740>] (state_store) from [<c09fa698>] (kobj_attr_store+0x14/0x20)
[<c09fa698>] (kobj_attr_store) from [<c030159c>] (sysfs_kf_write+0x4c/0x50)
[<c030159c>] (sysfs_kf_write) from [<c0300620>] (kernfs_fop_write+0xfc/0x1e0)
[<c0300620>] (kernfs_fop_write) from [<c0282be8>] (__vfs_write+0x2c/0x160)
[<c0282be8>] (__vfs_write) from [<c0282ea4>] (vfs_write+0xa4/0x16c)
[<c0282ea4>] (vfs_write) from [<c0283080>] (ksys_write+0x40/0x8c)
[<c0283080>] (ksys_write) from [<c0101000>] (ret_fast_syscall+0x0/0x28)
...
---[ end trace 03fc9866185939bf ]---

Undefined instruction is triggered during CP14 reset, because bits: #16
(Secure privileged invasive debug disabled) and #17 (Secure privileged
noninvasive debug disable) are set in DSCR. Those bits depend on SPNIDEN
and SPIDEN lines, which are provided by Secure JTAG hardware block. That
block in turn is powered from cluster 0 (big/Eagle), but the Exynos5422
boots on cluster 1 (LITTLE/KFC).

To fix this issue it is enough to turn on the power on the cluster 0 for
a while. This lets the Secure JTAG block to propagate the needed signals
to LITTLE/KFC cores and change their DSCR.

Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: I0fa6618740853169bd96efeb33975f0289ac3706

5 years agoclocksource: exynos_mct: Clear timer interrupt when shutdown 87/199787/2
Stuart Menefy [Sun, 10 Feb 2019 22:51:14 +0000 (22:51 +0000)]
clocksource: exynos_mct: Clear timer interrupt when shutdown

When shutting down the timer, ensure that after we have stopped the
timer any pending interrupts are cleared. This fixes a problem when
suspending, as interrupts are disabled before the timer is stopped,
so the timer interrupt may still be asserted, preventing the system
entering a low power state when the wfi is executed.

Signed-off-by: Stuart Menefy <stuart.menefy@mathembedded.com>
[pending patch for mainline]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: I2068bbadeb5e778bb81f772693e30a47e64dd77c

5 years agoclocksource: exynos_mct: Move one-shot check from tick clear to ISR 86/199786/2
Stuart Menefy [Sun, 10 Feb 2019 22:51:13 +0000 (22:51 +0000)]
clocksource: exynos_mct: Move one-shot check from tick clear to ISR

When a timer tick occurs and the clock is in one-shot mode, the timer
needs to be stopped to prevent it triggering subsequent interrupts.
Currently this code is in exynos4_mct_tick_clear(), but as it is
only needed when an ISR occurs move it into exynos4_mct_tick_isr(),
leaving exynos4_mct_tick_clear() just doing what its name suggests it
should.

Signed-off-by: Stuart Menefy <stuart.menefy@mathembedded.com>
[pending patch for mainline]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: I1004b6947a338d27dc629f4174607663dedc1f33

5 years agoARM: exynos: Fix timeout when booting secondary CPUs 85/199785/2
Stuart Menefy [Mon, 28 Jan 2019 23:06:45 +0000 (23:06 +0000)]
ARM: exynos: Fix timeout when booting secondary CPUs

Without this fix the loop waiting for the timeout exits, but the
subsequent test to see if the timeout occurred fails.

Signed-off-by: Stuart Menefy <stuart.menefy@mathembedded.com>
Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
[backport of mainline commit 4bdf2f3f20a9de9b07f97907820c42f3a49ba63d]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: If43a148b759fa015abd46fdfb60d64fdfe3baf5f

5 years agoarm: Use common outgoing-CPU-notification code 84/199784/2
Paul E. McKenney [Mon, 4 Feb 2019 15:01:55 +0000 (16:01 +0100)]
arm: Use common outgoing-CPU-notification code

This commit removes the open-coded CPU-offline notification with new
common code.  In particular, this change avoids calling scheduler code
using RCU from an offline CPU that RCU is ignoring.  This is a minimal
change.  A more intrusive change might invoke the cpu_check_up_prepare()
and cpu_set_state_online() functions at CPU-online time, which would
allow onlining throw an error if the CPU did not go offline properly.

Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Cc: linux-arm-kernel@lists.infradead.org
Cc: Russell King <linux@arm.linux.org.uk>
[commit rejected in mainline, but needed on Exynos platform to fix
suspicious RCU usage during suspend/resume]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: I26ba637d48fc3264e1b79507cfd0cb82bb5e6390

5 years agocpufreq: dt: Implement online/offline() callbacks 83/199783/2
Viresh Kumar [Tue, 12 Feb 2019 07:06:47 +0000 (12:36 +0530)]
cpufreq: dt: Implement online/offline() callbacks

Implement the light-weight tear down and bring up helpers to reduce the
amount of work to do on CPU offline/online operation.

Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
[pending patch for mainline]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: I02a01f0f4d5c24102bcc58089937c371cc126b65

5 years agocpufreq: Allow light-weight tear down and bring up of CPUs 82/199782/2
Viresh Kumar [Tue, 12 Feb 2019 07:06:46 +0000 (12:36 +0530)]
cpufreq: Allow light-weight tear down and bring up of CPUs

The cpufreq core doesn't remove the cpufreq policy anymore on CPU
offline operation, rather that happens when the CPU device gets
unregistered from the kernel. This allows faster recovery when the CPU
comes back online. This is also very useful during system wide
suspend/resume where we offline all non-boot CPUs during suspend and
then bring them back on resume.

This commit takes the same idea a step ahead to allow drivers to do
light weight tear-down and bring-up during CPU offline and online
operations.

A new set of callbacks is introduced, online/offline(). online() gets
called when the first CPU of an inactive policy is brought up and
offline() gets called when all the CPUs of a policy are offlined.

The existing init/exit() callback get called on policy
creation/destruction. They also get called instead of online/offline()
callbacks if the online/offline() callbacks aren't provided.

This also moves around some code to get executed only for the new-policy
case going forward.

Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
[pending patch for mainline]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: I27bd475cac802ffae345308fc145490966eda456

5 years agodevfreq: Suspend all devices on system shutdown 81/199781/2
Marek Szyprowski [Fri, 25 Jan 2019 13:49:53 +0000 (14:49 +0100)]
devfreq: Suspend all devices on system shutdown

This way devfreq core ensures that all its devices will be set to safe
operation points before reboot operation. There are board on which some
aggressive power saving operation points are behind the capabilities of
the bootloader to properly reset the hardware and boot the board. This
way one can avoid board crash early after reboot.

Similar pattern is used in CPUfreq subsystem.

Reported-by: Markus Reichl <m.reichl@fivetechno.de>
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: I45467c8e02f7fedf90d1dfd5080e6143a8cb69f7

5 years agortc: s3c: Use generic helper to get driver data 80/199780/2
Marek Szyprowski [Fri, 18 Jan 2019 13:28:37 +0000 (14:28 +0100)]
rtc: s3c: Use generic helper to get driver data

Replace of_match_node() with of_device_get_match_data(), which removes a
few lines of code from the driver.

Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
[backport of mainline commit 64704c92fd19c599f20433aae1372a7ccab79a57]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: I9e3a1662233334925ca9ace34609468dc8bc0a14

5 years agortc: s3c: Rewrite clock handling 79/199779/2
Marek Szyprowski [Mon, 21 Jan 2019 11:09:30 +0000 (12:09 +0100)]
rtc: s3c: Rewrite clock handling

s3c_rtc_enable/disable_clk() functions were designed to be called multiple
times without reference counting, because they were initially only used in
alarm setting/clearing functions, which can be called both when alarm is
already set or not. Later however, calls to those functions have been added to
other places in the driver - like time and /proc reading callbacks, what
results in broken alarm if any of such events happens after the alarm has
been set. Fix this by simplifying s3c_rtc_enable/disable_clk() functions
to rely on proper reference counting in clock core and move alarm enable
counter to s3c_rtc_setaie() function.

Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
[backport of mainline commit 5a5b614ba61cc2a89ad0dffc63d913a1a6ba1f9f]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: Ib72a76ea0567ece0b7b5b706f2ee3b6cca850150

5 years agortc: s3c-rtc: Avoid using broken ALMYEAR register 78/199778/2
Marek Szyprowski [Tue, 13 Nov 2018 11:32:50 +0000 (12:32 +0100)]
rtc: s3c-rtc: Avoid using broken ALMYEAR register

(RTC,ALM)YEAR registers of Exynos built-in RTC device contains 3 BCD
characters. s3c-rtc driver uses only 2 lower of them and supports years
from 2000..2099 range. The third BCD value is typically set to 0, but it
looks that handling of it is broken in the hardware. It sometimes
defaults to a random (even non-BCD) value. This is not an issue
for handling RTCYEAR register, because bcd2bin() properly handles only
8bit values (2 BCD characters, the third one is skipped). The problem
is however with ALMYEAR register and proper RTC alarm operation. When
YEAREN bit is set for the configured alarm, RTC hardware triggers alarm
only when ALMYEAR and RTCYEAR matches. This usually doesn't happen
because of the random noise on the third BCD character.

Fix this by simply skipping setting ALMYEAR register in alarm
configuration. This workaround fixes broken alarm operation on Exynos
built-in rtc device. My tests revealed that the issue happens on the
following Exynos series: 3250, 4210, 4412, 5250 and 5410.

Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
[backport of mainline commit 50c8aec4212a966817e868056efc9bfbb73337c0]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: I057ae196eeaa9a2c0fee5fcf4c66625783cdfc21

5 years agoarm64: configs: tizen_tm2_defconfig: enable syscon-reboot-mode config 03/199703/4
Seung-Woo Kim [Thu, 14 Feb 2019 06:17:00 +0000 (15:17 +0900)]
arm64: configs: tizen_tm2_defconfig: enable syscon-reboot-mode config

To support reboot-mode, enable syscon-reboot-mode config option.

Change-Id: I27e2da1f29aa5fa271b0914fd62e38470f47b403
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
5 years agoarm64: dts: exynos5433-tm2: add syscon-reboot-mode 02/199702/4
Seung-Woo Kim [Thu, 14 Feb 2019 06:15:50 +0000 (15:15 +0900)]
arm64: dts: exynos5433-tm2: add syscon-reboot-mode

Add syscon-reboot-mode dt node to support reboot mode. TM2
bootloader uses INFORM3 register to check reboot mode of kernel.

Change-Id: I2d5ee09c005f14d4fa7c274fecade920385712e3
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
5 years agoARM: configs: tizen_odroid: enable syscon-reboot-mode config 01/199701/3
Seung-Woo Kim [Thu, 14 Feb 2019 06:14:54 +0000 (15:14 +0900)]
ARM: configs: tizen_odroid: enable syscon-reboot-mode config

To support reboot-mode, enable syscon-reboot-mode config option.

Change-Id: I4fe5074f4eeaec4d27d686e5bea4eaf5820fd640
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
5 years agoARM: dts: trats2: add syscon-reboot-mode 00/199700/3
Seung-Woo Kim [Thu, 14 Feb 2019 06:12:28 +0000 (15:12 +0900)]
ARM: dts: trats2: add syscon-reboot-mode

Add syscon-reboot-mode dt node to support reboot mode. Trats2 uses
INFORM3 register with offset 0x80c not like odroid families.
In trats2's case, when we released the tizen-2.X with linux-3.10
kernel, it had used the INFORM3 register. That's why trats2 uses
the INFORM3 register for reboot-mode.

Change-Id: Ib7134020b493a83cc7661fe966ea40128f4f8dcc
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
5 years agoARM: dts: odroid: add syscon-reboot-mode 99/199699/3
Seung-Woo Kim [Thu, 14 Feb 2019 06:09:46 +0000 (15:09 +0900)]
ARM: dts: odroid: add syscon-reboot-mode

Add the syscon-reboot-mode dt node to support reboot mode.
Odroid families use INFORM2 register with offset 0x808 to let
bootloader recognize reboot mode.

Change-Id: I9876bfce4fc519026c62c53f10e1ef2107cfc256
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
5 years agoARM/ARM64: dts: exynos: add simple-mfd compatible to pmu dt-node 98/199698/3
Seung-Woo Kim [Thu, 14 Feb 2019 06:07:30 +0000 (15:07 +0900)]
ARM/ARM64: dts: exynos: add simple-mfd compatible to pmu dt-node

To support syscon-reboot-mode with exynos-pmu, simple-mfd
compatible is required.

Reference: Documentation/devicetree/bindings/power/reset/syscon-reboot-mode.txt
Reference: Documentation/devicetree/bindings/mfd/mfd.txt

Change-Id: I81e78cf5c7f4b3373c181886820b323dadab3d0f
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
5 years agosoc: exynos: add reboot-mode header 97/199697/3
Seung-Woo Kim [Thu, 14 Feb 2019 06:03:19 +0000 (15:03 +0900)]
soc: exynos: add reboot-mode header

Exynos platform uses a SYSCON mapped pmu register store
the reboot mode magic value for bootloader to use when
system reboot.

Add the shared header describing the values firmware expects
for different boot modes.

Change-Id: I83bfd3df79652ba55e158fc9e0a56724597ef67d
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
5 years agoLOCAL / ARM: SAMSUNG: set chip product id as system_serial
Seung-Woo Kim [Tue, 18 Apr 2017 01:11:01 +0000 (10:11 +0900)]
LOCAL / ARM: SAMSUNG: set chip product id as system_serial

The Exynos SoC has 64bit chip product id and it is unique for
each chip. So it can be used as system_serial.

Change-Id: Id739b865a1e355a0209841ff2ca1802b5daeabb2
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
5 years agosoc: exynos: asv: Switch to MHz unit for frequency in ASV tables
Sylwester Nawrocki [Fri, 1 Feb 2019 16:03:22 +0000 (17:03 +0100)]
soc: exynos: asv: Switch to MHz unit for frequency in ASV tables

There is no need to store the frequencies in kHz units, MHz granularity
is enough and is also used for other SoCs. Remove leading zeros in the
first column of each table and update users accordingly.

Change-Id: I07b0e0395dc6f60d16a008daa27a0ca7a3dcab78
Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
5 years agosoc: samsung: asv: Drop unnecessary cpuid local variable
Sylwester Nawrocki [Wed, 30 Jan 2019 16:58:35 +0000 (17:58 +0100)]
soc: samsung: asv: Drop unnecessary cpuid local variable

Make the code more explicit by dropping the local variable and using
cpu->id directly.

Change-Id: Id97f57e15083e6928852988007d048e28b754285
Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
5 years agosoc: samsung: Split the ASV driver into common and SoC-specific part
Sylwester Nawrocki [Wed, 30 Jan 2019 16:55:49 +0000 (17:55 +0100)]
soc: samsung: Split the ASV driver into common and SoC-specific part

The exynos-asv driver is re-factored as a prerequisite for adding support
for other SoCs.

Change-Id: I252a2f51d101ad39b0469ee7f31f69cd9f0120b5
Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
5 years agopackaging: Change the kernel version of the spec files
Junghoon Kim [Fri, 8 Feb 2019 06:26:58 +0000 (15:26 +0900)]
packaging: Change the kernel version of the spec files

This patch changes the kernel version of the spec files to 4.14.99.

Change-Id: Ibb04f798717f8ff1e9f5e1c6691d6ec3e9dc56ff
Signed-off-by: Junghoon Kim <jhoon20.kim@samsung.com>
5 years agodrivers: power: opp: remove all OPPs registered from DT
Lukasz Luba [Tue, 29 Jan 2019 15:16:05 +0000 (16:16 +0100)]
drivers: power: opp: remove all OPPs registered from DT

Patch solves issue with OPPs registered from DT and not removed during
suspend. In suspend there was a warning:
[   18.152874] ------------[ cut here ]------------
[   18.152885] WARNING: CPU: 7 PID: 43 at drivers/base/power/opp/core.c:1367 dev_pm_opp_put_regulators+0xa8/0xb8
[   18.152889] Modules linked in:
[   18.152898] CPU: 7 PID: 43 Comm: cpuhp/7 Not tainted 4.14.85-00448-g64a9f12-dirty #6
[   18.152902] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[   18.152917] [<c01117b0>] (unwind_backtrace) from [<c010cf10>] (show_stack+0x20/0x24)
[   18.152927] [<c010cf10>] (show_stack) from [<c0c37310>] (dump_stack+0x7c/0x9c)
[   18.152938] [<c0c37310>] (dump_stack) from [<c012256c>] (__warn+0xe4/0x110)
[   18.152946] [<c012256c>] (__warn) from [<c01225c8>] (warn_slowpath_null+0x30/0x38)
[   18.152953] [<c01225c8>] (warn_slowpath_null) from [<c05755c4>] (dev_pm_opp_put_regulators+0xa8/0xb8)
[   18.152963] [<c05755c4>] (dev_pm_opp_put_regulators) from [<c0893e44>] (cpufreq_exit+0xa4/0xb0)
[   18.152971] [<c0893e44>] (cpufreq_exit) from [<c088f754>] (cpufreq_offline+0x118/0x238)
[   18.152977] [<c088f754>] (cpufreq_offline) from [<c088f930>] (cpuhp_cpufreq_offline+0x18/0x20)
[   18.152984] [<c088f930>] (cpuhp_cpufreq_offline) from [<c0122d18>] (cpuhp_invoke_callback+0xdc/0x964)
[   18.152992] [<c0122d18>] (cpuhp_invoke_callback) from [<c01245b8>] (cpuhp_thread_fun+0x114/0x2a4)
[   18.153002] [<c01245b8>] (cpuhp_thread_fun) from [<c0147298>] (smpboot_thread_fn+0x1cc/0x2f0)
[   18.153010] [<c0147298>] (smpboot_thread_fn) from [<c0142bb8>] (kthread+0x130/0x168)
[   18.153018] [<c0142bb8>] (kthread) from [<c0108e08>] (ret_from_fork+0x14/0x2c)
[   18.153023] ---[ end trace a7d94f69fabccd7c ]---

This fix introduces removing all OPPs and is similar to what is present in
current mainline.

Change-Id: I1abb9c5c887721163c24221ddcac90c35bdf8d67
Signed-off-by: Lukasz Luba <l.luba@partner.samsung.com>
5 years agoPM / devfreq: Fix handling of min/max_freq == 0
Matthias Kaehlcke [Fri, 3 Aug 2018 20:05:09 +0000 (13:05 -0700)]
PM / devfreq: Fix handling of min/max_freq == 0

Commit ab8f58ad72c4 ("PM / devfreq: Set min/max_freq when adding the
devfreq device") initializes df->min/max_freq with the min/max OPP when
the device is added. Later commit f1d981eaecf8 ("PM / devfreq: Use the
available min/max frequency") adds df->scaling_min/max_freq and the
following to the frequency adjustment code:

  max_freq = MIN(devfreq->scaling_max_freq, devfreq->max_freq);

With the current handling of min/max_freq this is incorrect:

Even though df->max_freq is now initialized to a value != 0 user space
can still set it to 0, in this case max_freq would be 0 instead of
df->scaling_max_freq as intended. In consequence the frequency adjustment
is not performed:

  if (max_freq && freq > max_freq) {
freq = max_freq;

To fix this set df->min/max freq to the min/max OPP in max/max_freq_store,
when the user passes a value of 0. This also prevents df->max_freq from
being set below the min OPP when df->min_freq is 0, and similar for
min_freq. Since it is now guaranteed that df->min/max_freq can't be 0 the
checks for this case can be removed.

Change-Id: I4092597dd0d81fd3937bf3a97a9e2639d542d030
Fixes: f1d981eaecf8 ("PM / devfreq: Use the available min/max frequency")
Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
Reviewed-by: Brian Norris <briannorris@chromium.org>
Reviewed-by: Chanwoo Choi <cw00.choi@samsung.com>
Signed-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>
[cw00.choi: Backported from mainline kernel]
Signed-off--by: Chanwoo Choi <cw00.choi@samsung.com>
5 years agoPM / devfreq: Drop custom MIN/MAX macros
Bjorn Andersson [Tue, 24 Apr 2018 19:46:39 +0000 (12:46 -0700)]
PM / devfreq: Drop custom MIN/MAX macros

Drop the custom MIN/MAX macros in favour of the standard min/max from
kernel.h

Change-Id: Ic519d8d2be7ec63e412221cdb55d85bad43f1be1
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Reviewed-by: Chanwoo Choi <cw00.choi@samsung.com>
Signed-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>
[cw00.choi: Backported from mainline kernel]
Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
5 years agoPM / devfreq: Fix devfreq_add_device() when drivers are built as modules.
Enric Balletbo i Serra [Wed, 4 Jul 2018 08:45:50 +0000 (10:45 +0200)]
PM / devfreq: Fix devfreq_add_device() when drivers are built as modules.

When the devfreq driver and the governor driver are built as modules,
the call to devfreq_add_device() or governor_store() fails because the
governor driver is not loaded at the time the devfreq driver loads. The
devfreq driver has a build dependency on the governor but also should
have a runtime dependency. We need to make sure that the governor driver
is loaded before the devfreq driver.

This patch fixes this bug by adding a try_then_request_governor()
function. First tries to find the governor, and then, if it is not found,
it requests the module and tries again.

Change-Id: I71cdbcc2867980714de984d0c0c2641f7eda8b46
Fixes: 1b5c1be2c88e (PM / devfreq: map devfreq drivers to governor using name)
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Reviewed-by: Chanwoo Choi <cw00.choi@samsung.com>
Signed-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>
[cw00.choi: Backported from mainline kernel]
Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
5 years agoPM / devfreq: use put_device() instead of kfree()
Arvind Yadav [Tue, 29 Jan 2019 05:49:02 +0000 (14:49 +0900)]
PM / devfreq: use put_device() instead of kfree()

Never directly free @dev after calling device_register() or
device_unregister(), even if device_register() returned an error.
Always use put_device() to give up the reference initialized.

Change-Id: I65b83e63daf44ff784753b2372890f07c6515a46
Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>
Reviewed-by: Chanwoo Choi <cw00.choi@samsung.com>
Signed-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>
[cw00.choi: Backported from mainline kernel]
Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
5 years agoPM / devfreq: exynos-ppmu: Delete an error message for a failed memory allocation...
Markus Elfring [Tue, 13 Feb 2018 21:10:42 +0000 (22:10 +0100)]
PM / devfreq: exynos-ppmu: Delete an error message for a failed memory allocation in exynos_ppmu_probe()

Omit an extra message for a memory allocation failure in this function.

This issue was detected by using the Coccinelle software.

Change-Id: I25ee724ab3da80f54f339c4ed54bb7bf3c30dbc8
Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
Acked-by: Chanwoo Choi <cw00.choi@samsung.com>
Signed-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>
[cw00.choi: Backported from mainline kernel]
Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
5 years agodrivers: devfreq: exynos: use devm_pm_opp_add() in DMC
Lukasz Luba [Mon, 28 Jan 2019 11:23:48 +0000 (12:23 +0100)]
drivers: devfreq: exynos: use devm_pm_opp_add() in DMC

It change the exynos5-dmc dirver to use safe devm_pm_opp_add() function
for registering new OPPs. Thus, there device resource subsystem takes
care for removing OPPs and/or OPP table in case of deffer probe.

Change-Id: I6d5793e990ac585dca60b4b93018fec0d5e018b0
Signed-off-by: Lukasz Luba <l.luba@partner.samsung.com>
5 years agoinclude: pm_opp: define devm_* functions for notification chain
Lukasz Luba [Wed, 23 Jan 2019 20:31:47 +0000 (21:31 +0100)]
include: pm_opp: define devm_* functions for notification chain

This patch adds needed function declarations for OPP PM notification
chain registration. The prototype of function devm_pm_opp_register_notifier()
or unregister and needed inline empty definitions in case of lack of config.

Change-Id: Ied2f7e0c59a591767fb29a25f356d31bea452e26
Signed-off-by: Lukasz Luba <l.luba@partner.samsung.com>
5 years agodrivers: base: opp: add devm_* for registration of notification chain
Lukasz Luba [Wed, 23 Jan 2019 20:30:36 +0000 (21:30 +0100)]
drivers: base: opp: add devm_* for registration of notification chain

Add safe function devm_pm_opp_register_notifier() for registering
notification chain for OPP changes. The function is used in case of
deffer probe, when the device is cleaned and probe function is called
agian.

Change-Id: I188bbfaddc821489c26cb908abb05ccece831dc3
Signed-off-by: Lukasz Luba <l.luba@partner.samsung.com>
5 years agoinclude: pm_opp: define new function devm_pm_opp_add()
Lukasz Luba [Wed, 23 Jan 2019 18:14:41 +0000 (19:14 +0100)]
include: pm_opp: define new function devm_pm_opp_add()

Add new function declaration devm_pm_opp_add() in OPP PM subsystem.
It provides safe mechanism for registering OPPs in case of deffer probe.
The patch adds also inline empty functions in case of lack the config.
There is also declaration for devm_pm_opp_remove functions.

Change-Id: I03f14038b03f51fab2674f1cce5df78af37105c2
Signed-off-by: Lukasz Luba <l.luba@partner.samsung.com>
5 years agodrivers: base: opp: add devres support and devm_* functions
Lukasz Luba [Wed, 23 Jan 2019 17:36:00 +0000 (18:36 +0100)]
drivers: base: opp: add devres support and devm_* functions

The patch adds basic support for resource tracking in OPP subsystem.
From now, adding a new OPP might be done using devm_pm_opp_add() which
is safe in case of deffer probe.
When the deffer probe is used and the driver does not remove explicitly
the OPP table, it causes warnings for the next try.
With devm_pm_opp_add() the resources are freed and the next deffer probe
is safe.
There is also simple wrapper for dev_pm_opp_remove().

Change-Id: I0b8282e9faf59b34e958853a451f2e7c9a13c18b
Signed-off-by: Lukasz Luba <l.luba@partner.samsung.com>
5 years agodrivers: base: opp: add allocate_opp_table() used by devres.c
Lukasz Luba [Wed, 23 Jan 2019 18:12:38 +0000 (19:12 +0100)]
drivers: base: opp: add allocate_opp_table() used by devres.c

The patch adds needed function for devres.c which implements
family of devm_* safe function. It is used for resource tracking
in case of deffer probe, when the driver probe function is called
a few times. The allocated OPP table must be freed and OPPs removed.

Change-Id: I9f098ea8a00bbef03ba680c4efe3b2fdf2e076d2
Signed-off-by: Lukasz Luba <l.luba@partner.samsung.com>
5 years agomfd: sec-core: read irq registers
Joonyoung Shim [Tue, 22 Nov 2016 06:47:52 +0000 (15:47 +0900)]
mfd: sec-core: read irq registers

On Odroid-XU3 case, this needs to succeed suspend/resume from second
time.

Signed-off-by: Joonyoung Shim <jy0922.shim@samsung.com>
Change-Id: I6ae92bb1116bb3ccfdbae4769258001cedd43d44

5 years agoARM: EXYNOS: firmware: add workaround code for suspend/resume
Joonyoung Shim [Thu, 17 Nov 2016 07:43:31 +0000 (16:43 +0900)]
ARM: EXYNOS: firmware: add workaround code for suspend/resume

This comes from S.LSI kernel.

Signed-off-by: Joonyoung Shim <jy0922.shim@samsung.com>
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: Id5b57259de9ad09d5ad712ed19ad47713f045dea

5 years agoARM: exynos: Remove no longer needed s3c_pm_check_*() calls
Bartlomiej Zolnierkiewicz [Mon, 15 Oct 2018 13:48:27 +0000 (15:48 +0200)]
ARM: exynos: Remove no longer needed s3c_pm_check_*() calls

Since commit 6862fdf2201a ("ARM: samsung: Limit SAMSUNG_PM_CHECK
config option to non-Exynos platforms") s3c_pm_check_*() calls
are redundant and can be removed.

Signed-off-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
[backport of mainline commit ]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: Idc96a5a0d48eca57c6f7efed96e11789cec0481e

5 years agoARM: exynos: Fix imprecise abort during Exynos5422 suspend to RAM
Krzysztof Kozlowski [Tue, 24 Jul 2018 16:49:46 +0000 (18:49 +0200)]
ARM: exynos: Fix imprecise abort during Exynos5422 suspend to RAM

Suspend to RAM on Odroid XU3/XU4/HC1 family (Exynos5422) causes
imprecise abort:

PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.003 seconds) done.
OOM killer disabled.
Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
wake enabled for irq 139
Disabling non-boot CPUs ...
IRQ51 no longer affine to CPU1
IRQ52 no longer affine to CPU2
IRQ53 no longer affine to CPU3
IRQ54 no longer affine to CPU4
IRQ55 no longer affine to CPU5
IRQ56 no longer affine to CPU6
cpu cpu4: Dropping the link to regulator.40
IRQ57 no longer affine to CPU7
Unhandled fault: external abort on non-linefetch (0x1008) at 0xf081a028
Internal error: : 1008 [#1] PREEMPT SMP ARM

with last call trace in exynos_suspend_enter().

The abort is caused by writing to register in secure part of sysram.
Boards booted under secure firmware (e.g. Hardkernel Odroid boards)
should access non-secure sysram.

Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
[backport of mainline commit e0b35c1ab5ac5f0453d1093770e119bd8d63d85c]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: Iaa947452e284d9df9b917e77ece381475ad717da

5 years agoARM: exynos: Store Exynos5420 register state in one variable
Krzysztof Kozlowski [Tue, 24 Jul 2018 16:49:44 +0000 (18:49 +0200)]
ARM: exynos: Store Exynos5420 register state in one variable

Instead of keeping two static variables put them into one struct which
later can grow.  This will reduce number of file-scope symbols.

Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
[backport of mainline commit 687b5ae2e6c6682a2b0bda3b31a884ed564f9194]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: I6717640c3d0b6d00e2d17a4bca300a42ba4ea192

5 years agoclk: samsung: exynos5420: Define CLK_SECKEY gate clock only or Exynos5420
Joonyoung Shim [Mon, 24 Sep 2018 11:00:56 +0000 (13:00 +0200)]
clk: samsung: exynos5420: Define CLK_SECKEY gate clock only or Exynos5420

The bit of GATE_BUS_PERIS1 for CLK_SECKEY is just reserved on
exynos5422/5800, not exynos5420. Define gate clk for exynos5420 to
handle the bit only on exynos5420.

Signed-off-by: Joonyoung Shim <jy0922.shim@samsung.com>
[m.szyprow: rewrote commit subject]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Signed-off-by: Sylwester Nawrocki <snawrocki@kernel.org>
[backport of mainline commit d32dd2a1a0f80edad158c9a1ba5f47650d9504a0]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: Ibe07b14ac8bc88d18e76c9e2968ff7c08b5c3b67

5 years agoARM: dts: exynos: Add pin configuration for SD write protect on Odroid XU3/XU4/HC1
Anand Moon [Thu, 27 Sep 2018 14:07:36 +0000 (14:07 +0000)]
ARM: dts: exynos: Add pin configuration for SD write protect on Odroid XU3/XU4/HC1

Add SD card write-protect pin configuration to be sure that it will be
properly pulled down to indicate write access.

Suggested-by: Krzysztof Kozlowski <krzk@kernel.org>
Signed-off-by: Anand Moon <linux.amoon@gmail.com>
Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
[backport of mainline commit 6135ee70cb1314681772645242beee46fcf5d185]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: Ic23dfd37330417d7b0724247354f1aed1a84b9de

5 years agoARM: dts: exynos: Update maximum frequency for eMMC to 200MHz on Odroid XU3/XU4
Anand Moon [Thu, 27 Sep 2018 14:07:37 +0000 (14:07 +0000)]
ARM: dts: exynos: Update maximum frequency for eMMC to 200MHz on Odroid XU3/XU4

Set the eMMC max-frequency to 200MHz for optimal performance on Odroid
XU3/XU4 family of boards.

Signed-off-by: Anand Moon <linux.amoon@gmail.com>
Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
[backport of mainline commit 4289c86c4cd7a848590e1e2c3e0e3274136b6848]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: Ia7470eccf05871c498d9270d49855c3dc71228f2

5 years agoARM: dts: exynos: Update maximum frequency for SD card to 200MHz on Odroid XU3/XU4/HC1
Anand Moon [Thu, 27 Sep 2018 14:07:35 +0000 (14:07 +0000)]
ARM: dts: exynos: Update maximum frequency for SD card to 200MHz on Odroid XU3/XU4/HC1

Set the SD max-frequency to 200MHz for optimal performance on Odroid
XU3/XU4/HC1 family of boards.

Signed-off-by: Anand Moon <linux.amoon@gmail.com>
Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
[backport of mainline commit c60b3f77f497d2720f7b841e78acfcf24fee071a]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: I46d7d0ba4e8558ca1e9d54754538c9a988180bfb

5 years agoARM: dts: exynos: Fix LDO13 min values on Odroid XU3/XU4/HC1
Anand Moon [Thu, 27 Sep 2018 14:07:34 +0000 (14:07 +0000)]
ARM: dts: exynos: Fix LDO13 min values on Odroid XU3/XU4/HC1

From Odroid XU3/XU4/HC1 schematics the LDO13 regulator for SD2, can be
set on 1.8V or 2.8V so the minimal value should be fixed to 1.8V.  This
is necessary to support UHS-I tuning (otherwise card won't be detected
during boot).

Signed-off-by: Anand Moon <linux.amoon@gmail.com>
Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
[backport of mainline commit 8fe325fa9d065aa54db4914fdaccab2169fd67a8]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: Ife4ea8f5f221de8be59bcba2985b099a8775cea4

5 years agoARM: dts: exynos: Add UHS-I bus speed support to Odroid XU3/XU4/HC1
Anand Moon [Thu, 27 Sep 2018 14:07:33 +0000 (14:07 +0000)]
ARM: dts: exynos: Add UHS-I bus speed support to Odroid XU3/XU4/HC1

Add support for UHS-I bus speed tuning for SDR50, DDR50 and SDR104 to
Odroid XU3/XU4/HC1 family boards.

Signed-off-by: Anand Moon <linux.amoon@gmail.com>
Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
[backport of mainline commit 25e5566e2b6e3ea0768505f75db887d7176150ce]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: Ib2422e135cc46ca597a555fd4466cc01b8f504f5

5 years agoARM: dts: exynos: Add compatible for s2mps11 clocks node on Exynos542x
Krzysztof Kozlowski [Wed, 25 Jul 2018 15:55:16 +0000 (17:55 +0200)]
ARM: dts: exynos: Add compatible for s2mps11 clocks node on Exynos542x

The bindings for s2mps11/s5m8767 clocks driver require a compatible for
clocks node.  Parent MFD sec-core driver will also use it when
instantiating children.

The compatible is not needed for proper working because device will be
anyway created by parent MFD device.  Add it for correctness.

Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
[backport of mainline commit 3f9d8677b73bbf62f7e53a165a88f953d1dca926]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: I0ef950609cec279ff9c70242352dcba414e9ec1d

5 years agoARM: dts: exynos: Add LDO28 regulator on Exynos5422 Odroid boards
Krzysztof Kozlowski [Mon, 6 Aug 2018 16:09:33 +0000 (18:09 +0200)]
ARM: dts: exynos: Add LDO28 regulator on Exynos5422 Odroid boards

The LDO28 is used only on Odroid XU3 for Display Port.  Define it so DTS
will describe entire hardware.

Depending on bootloader behavior this might affect the Display Port
because none of drivers are enabling it. By default it is off in S2MPS11
PMIC reset values.  However it could be enabled by bootloader so in such
case kernel will later disable it as unused regulator.

Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
Tested-by: Marek Szyprowski <m.szyprowski@samsung.com>
[backport of mainline commit 8be3e7f0785c2258479aab26c926ed9be6b9a799]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: I646826a349ca66544cafcf7749a1b27416073017

5 years agoARM: dts: exynos: Disable unused PMIC regulators on Exynos5422 Odroid boards
Krzysztof Kozlowski [Mon, 6 Aug 2018 16:09:32 +0000 (18:09 +0200)]
ARM: dts: exynos: Disable unused PMIC regulators on Exynos5422 Odroid boards

Disable unused PMIC regulators on Exynos5422 Odroid boards to reduce
energy used. According to schematics:
1. LDO12, LDO16 and LDO24 are not connected,
2. LDO26 is not used on Odroid HC1.

Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
[backport of mainline commit b5124e4507939e6a254968091148759de37947bb]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: I1dc3fe5991857c6bb54691212f7c624362235360

5 years agoARM: dts: exynos: Add unused PMIC regulators on Exynos5422 Odroid boards
Krzysztof Kozlowski [Mon, 6 Aug 2018 16:09:31 +0000 (18:09 +0200)]
ARM: dts: exynos: Add unused PMIC regulators on Exynos5422 Odroid boards

Define LDO14, LDO20-22, LDO25 and LOD29-38 unused regulators to
describe the hardware.

Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
[backport of mainline commit 8e82954979fc41426c924a9bee93d435b5639cda]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: I8089ac54336ae49ea791964364ec2c69c7be9639

5 years agoARM: dts: exynos: Add missing used PMIC regulators on Exynos5422 Odroid boards
Krzysztof Kozlowski [Mon, 6 Aug 2018 16:09:30 +0000 (18:09 +0200)]
ARM: dts: exynos: Add missing used PMIC regulators on Exynos5422 Odroid boards

Define LDO2, LDO23 and LDO27 critical board regulators to describe the
hardware.

Suggested-by: Joonyoung Shim <jy0922.shim@samsung.com>
Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
[backport of mainline commit 95ac226222a6130982b9b2d924db2945b6338885]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: Ie54c2d746e66c4c630aa6d19b752f5957ebf3817

5 years agoARM: dts: exynos/s3c: Remove leading 0x and 0s from bindings notation
Mathieu Malaterre [Wed, 2 May 2018 20:11:52 +0000 (22:11 +0200)]
ARM: dts: exynos/s3c: Remove leading 0x and 0s from bindings notation

Improve the DTS files by removing all the leading "0x" and zeros to fix the
following dtc warnings:

    Warning (unit_address_format): Node /XXX unit name should not have leading "0x"
    Warning (unit_address_format): Node /XXX unit name should not have leading 0s

Converted using the following command:

    find arch/arm/boot/dts -type f \( -iname "*.dts" -o -iname "*.dtsi" \) -exec sed -i \
    -e "s/@\([0-9a-fA-FxX\.;:#]\+\)\s*{/@\L\1 {/g" -e "s/@0x\(.*\) {/@\1 \
    {/g" -e "s/@0\+\(.\+\) {/@\1 {/g" {} +

For simplicity, two sed expressions were used to solve each warnings separately.

To make the regex expression more robust a few other issues were resolved,
namely setting unit-address to lower case, and adding a whitespace before the
the opening curly brace: https://elinux.org/Device_Tree_Linux#Linux_conventions

This will solve also a side effect warning:

    Warning (simple_bus_reg): Node /XXX@<UPPER> simple-bus unit address format error, expected "<lower>"

This is a follow up to commit 4c9847b7375a ("dt-bindings: Remove leading 0x from bindings notation")

Reported-by: David Daney <ddaney@caviumnetworks.com>
Suggested-by: Rob Herring <robh@kernel.org>
Signed-off-by: Mathieu Malaterre <malat@debian.org>
[krzk: Rerun the command to include few more changes, adjust the commit msg]
Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
[backport of mainline commit edef4285afb072f8d8ddfbfa107e54c4b45c0547]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: Ia25a2a2ffee646520762552549ea59f57ded8f5b

5 years agoconfigs: Enable Odroid sound driver in tizen_odroid_defconfig
Sylwester Nawrocki [Mon, 7 Jan 2019 16:50:42 +0000 (17:50 +0100)]
configs: Enable Odroid sound driver in tizen_odroid_defconfig

Change-Id: If09b313516975bc2897e539164721089fe308ecd
Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
5 years agoASoC: core: Invoke pcm_new() for all DAI-link
Rohit kumar [Thu, 1 Nov 2018 12:38:49 +0000 (18:08 +0530)]
ASoC: core: Invoke pcm_new() for all DAI-link

Remove no_pcm check to invoke pcm_new() for backend dai-links
too. This fixes crash in hdmi codec driver during hdmi_codec_startup()
while accessing chmap_info struct. chmap_info struct memory is
allocated in pcm_new() of hdmi codec driver which is not invoked
in case of DPCM when hdmi codec driver is part of backend dai-link.

Below is the crash stack:

[   61.635493] Unable to handle kernel NULL pointer dereference at virtual address 00000018
..
[   61.666696]   CM = 0, WnR = 1
[   61.669778] user pgtable: 4k pages, 39-bit VAs, pgd = ffffffc0d6633000
[   61.676526] [0000000000000018] *pgd=0000000153fc8003, *pud=0000000153fc8003, *pmd=0000000000000000
[   61.685793] Internal error: Oops: 96000046 [#1] PREEMPT SMP
[   61.722955] CPU: 7 PID: 2238 Comm: aplay Not tainted 4.14.72 #21
..
[   61.740269] PC is at hdmi_codec_startup+0x124/0x164
[   61.745308] LR is at hdmi_codec_startup+0xe4/0x164

Change-Id: I1335d13ffb7f0fd1ba10884ff23b81b6b51a3889
Signed-off-by: Rohit kumar <rohitkr@codeaurora.org>
5 years agoASoC: Use proper DT compatible string for Hardkernel Odroid boards
Sylwester Nawrocki [Wed, 7 Mar 2018 17:46:25 +0000 (18:46 +0100)]
ASoC: Use proper DT compatible string for Hardkernel Odroid boards

The Odroid boards are manufactured by Hardkernel, not Samsung. New compatible
string entries are added, with "hardkernel," instead of "samsung," vendor
prefix. Support for the old compatible strings is going to be removed after
some time.

Change-Id: I16c4892514b8399f635fa32fbe43a3dcf2f4c05a
Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Mark Brown <broonie@kernel.org>
5 years agoASoC: samsung: Use snd_soc_of_put_dai_link_codecs() in odroid.c
Sylwester Nawrocki [Wed, 14 Mar 2018 16:41:15 +0000 (17:41 +0100)]
ASoC: samsung: Use snd_soc_of_put_dai_link_codecs() in odroid.c

Now when a helper for unreferencing device nodes is available
we can get rid of the local implementation.

Change-Id: I12314edbf367f8d64c95cfb39d69f77fb5edce62
Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Signed-off-by: Mark Brown <broonie@kernel.org>
5 years agoASoC: Add snd_soc_of_put_dai_link_codecs() helper function
Sylwester Nawrocki [Fri, 9 Mar 2018 17:48:54 +0000 (18:48 +0100)]
ASoC: Add snd_soc_of_put_dai_link_codecs() helper function

The code for dereferencing device nodes in the 'codecs' array is moved
to a separate function so we can avoid open coding that in drivers.

Change-Id: I08f51d2a0ee3a6c412fb430ba97fe0fb1d011e5c
Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
5 years agoASoC: samsung: odroid: Drop sample rates that cannot be supported from hw_params()
Sylwester Nawrocki [Wed, 14 Mar 2018 16:41:14 +0000 (17:41 +0100)]
ASoC: samsung: odroid: Drop sample rates that cannot be supported from hw_params()

The I2S controller can handle sample rates only up to 96000 and the CPU DAI
has already related constraint set so drop the impossible 176400, 192000
switch cases.

Change-Id: I704632e1e943f9c67170913a55763291aaa31f77
Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Signed-off-by: Mark Brown <broonie@kernel.org>
5 years agoarm: config: exynos: enable DMC driver
Lukasz Luba [Fri, 11 Jan 2019 17:12:14 +0000 (18:12 +0100)]
arm: config: exynos: enable DMC driver

Enable driver for Dynamic Controller in Exynos SoCs.

Change-Id: Ic87339161b10a3a71a40b47af1d4789c997ef5a1
Signed-off-by: Lukasz Luba <l.luba@partner.samsung.com>
5 years agoARM: dts: exynos5420: change speed and parent of NoC clock
Lukasz Luba [Tue, 15 Jan 2019 17:59:24 +0000 (18:59 +0100)]
ARM: dts: exynos5420: change speed and parent of NoC clock

This patch changes speed to 400MHz and parent clock of NoC bus.
The old parent, which was set by bootloader, had speed 533MHz.
When the exynos-bus driver tried to change the frequency to 400MHz,
in low level the clock divider set val 2 and the actual frequency of
the bus was 266MHz. For the rest OPPs the same situation apply.
Having the right parent, meaning: PLL ratios declared and possible divider
values equal the OPPs values, if crucial for the buses.

This bus is used for data transport between GPU and DRAM. The performance
can be checked by fixing the freq of the bus (not by the ondemand governor)
and fixing the freq of GPU, then running some openGL benchmarks.

Change-Id: Ied8d9f50c7444a809670234ff62dc409f1f42a5f
Signed-off-by: Lukasz Luba <l.luba@partner.samsung.com>
5 years agoclk: samsung: Export Exynos5420 CLK_MOUT_WCORE NoC clock
Lukasz Luba [Tue, 15 Jan 2019 17:55:49 +0000 (18:55 +0100)]
clk: samsung: Export Exynos5420 CLK_MOUT_WCORE NoC clock

Patch adds ID for clock needed for changing parent of the main NoC clock.

Change-Id: I7ecc64ce7b09d0e7654bf9830e73a8328e269164
Signed-off-by: Lukasz Luba <l.luba@partner.samsung.com>
5 years agoclk: samsung: add new CLK_MOUT_WCORE for NoC in Exynos5420 SoC
Lukasz Luba [Tue, 15 Jan 2019 17:54:26 +0000 (18:54 +0100)]
clk: samsung: add new CLK_MOUT_WCORE for NoC in Exynos5420 SoC

New clock ID (CLK_MOUT_WCORE) is needed for changing parent of the main
NoC bus clock.

Change-Id: I21dbd629d0f4529f94ca0c07982cddcef63f7cc4
Signed-off-by: Lukasz Luba <l.luba@partner.samsung.com>
5 years agoarm: config: tizen: enable userspace governor in devfreq
Lukasz Luba [Tue, 22 Jan 2019 11:46:53 +0000 (12:46 +0100)]
arm: config: tizen: enable userspace governor in devfreq

Userspace governor provides feature of easy frequency change and is
needed by some drivers, like exynos5-dmc.

Change-Id: Iaa6ba575a0f13376b9ebc51ff4bc06ed96ead35b
Signed-off-by: Lukasz Luba <l.luba@partner.samsung.com>
5 years agoarm: config: tizen: enable DMC driver in tizen_odroid
Lukasz Luba [Tue, 22 Jan 2019 10:38:02 +0000 (11:38 +0100)]
arm: config: tizen: enable DMC driver in tizen_odroid

Enable driver for Dynamic Memory Controller in Exynos SoCs.

Change-Id: Iffb91a7c032d11c9bc9030716e1f546833af467f
Signed-off-by: Lukasz Luba <l.luba@partner.samsung.com>
5 years agodrivers: devfreq: events: add Exynos PPMU new events
Lukasz Luba [Fri, 11 Jan 2019 17:43:31 +0000 (18:43 +0100)]
drivers: devfreq: events: add Exynos PPMU new events

Define new performance events supported by Exynos5422 SoC counters.
The counters are built-in in Dynamic Memory Controller and provide
information regarding memory utilization.

Change-Id: Ia5feaed119cdbbdf570f8a5b3efcf231c500a2c8
Signed-off-by: Lukasz Luba <l.luba@partner.samsung.com>
5 years agoarm: DT: exynos: add exynos5422 DMC device
Lukasz Luba [Fri, 11 Jan 2019 17:07:45 +0000 (18:07 +0100)]
arm: DT: exynos: add exynos5422 DMC device

The patch adds a new file with Dynamic Controller device and
accosiated performance counters. It provides definition of used clocks
and register sets.

Change-Id: I71d31db1f4c4f2be174adc735662f4c35f4dcf7d
Signed-off-by: Lukasz Luba <l.luba@partner.samsung.com>
5 years agodrivers: devfreq: exynos5: add DMC driver
Lukasz Luba [Fri, 11 Jan 2019 17:00:39 +0000 (18:00 +0100)]
drivers: devfreq: exynos5: add DMC driver

This patch adds driver for Exynos5 Dynamic Memory Controller.
The driver provides support for DVFS in DMC and DRAM.
It also supports changing timings of DRAM running with different
frequency.

Change-Id: I98a630d1f0e6639bb160e0465302ae8f3800ef92
Signed-off-by: Lukasz Luba <l.luba@partner.samsung.com>
5 years agoclk: samsung: add new clocks for Exynos5422 SoC
Lukasz Luba [Fri, 11 Jan 2019 18:09:33 +0000 (19:09 +0100)]
clk: samsung: add new clocks for Exynos5422 SoC

This patch provides support for clocks needed for Dynamic Memory Controller
in Exynos5422. It also defines new PLL rates for BPLL which is used
for DMC.

Change-Id: I85d151a19a176ef5ea8057b49b0afbfb778fe5a9
Signed-off-by: Lukasz Luba <l.luba@partner.samsung.com>
5 years agoclk: samsung: add needed IDs for DMC clocks in Exynos5420
Lukasz Luba [Fri, 11 Jan 2019 18:07:38 +0000 (19:07 +0100)]
clk: samsung: add needed IDs for DMC clocks in Exynos5420

Define new IDs for clocks used by Dynamic Memory Controller in
Exynos5422 SoC.

Change-Id: Ic73d88601fa2c4631088300b930abefa25816158
Signed-off-by: Lukasz Luba <l.luba@partner.samsung.com>
5 years agoLOCAL / PCI: workaround for PCI issues in system suspend/resume on TM2
Marek Szyprowski [Fri, 7 Dec 2018 14:55:12 +0000 (15:55 +0100)]
LOCAL / PCI: workaround for PCI issues in system suspend/resume on TM2

Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: I31e72d43c2bc80c88049ec441aef4786839a1ff3

5 years agoLOCAL / PCI: exynos: add simple suspend/resume methods
Marek Szyprowski [Fri, 7 Dec 2018 11:21:14 +0000 (12:21 +0100)]
LOCAL / PCI: exynos: add simple suspend/resume methods

Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: I255983c0cbd6ee19b39c9c229d21139a46dc22f4

5 years agoarm64: dts: exynos: Add sleep state for the sleep relevant pins
Marek Szyprowski [Fri, 30 Nov 2018 09:30:17 +0000 (10:30 +0100)]
arm64: dts: exynos: Add sleep state for the sleep relevant pins

Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: Ia3f96901af60d5a81f7c559b0111bb3ed1c2024b

5 years agoarm64: dts: exynos: Enable all PCIe regulators
Marek Szyprowski [Tue, 20 Nov 2018 14:25:47 +0000 (15:25 +0100)]
arm64: dts: exynos: Enable all PCIe regulators

According to schematic diagram, a part of PCIe is using
VDD10_MIPI2L_1.0V_AP. Enable it always for now.

Suggested-by: Jaehoon Chung <jh80.chung@samsung.com>
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: I6a2742809237898419e417c983acb4d79eb6401f

5 years agopinctrl: samsung: use NOIRQ phase for suspend/resume
Marek Szyprowski [Mon, 3 Dec 2018 14:43:20 +0000 (15:43 +0100)]
pinctrl: samsung: use NOIRQ phase for suspend/resume

Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: Ibf8a51e77403bab519afa99ce826f060ec1f523e

5 years agommc: dw_mmc-exynos: fix potential external abort in resume_noirq()
Marek Szyprowski [Tue, 12 Jun 2018 10:55:23 +0000 (12:55 +0200)]
mmc: dw_mmc-exynos: fix potential external abort in resume_noirq()

dw_mci_exynos_resume_noirq() performs DWMMC register access without
ensuring that respective clocks are enabled. This might cause external
abort on some systems (observed on Exynos5433 based boards). Fix this
by forcing a PM runtime active state before register access. Using
SET_NOIRQ_SYSTEM_SLEEP_PM_OPS allows also to cleanup conditional code
a bit.

Suggested-by: Ulf Hansson <ulf.hansson@linaro.org>
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Change-Id: I172ee95730a0f45b0a2f4dea002c59928f3b1e63

5 years agoserial: samsung: Enable baud clock for UART reset procedure in resume
Marek Szyprowski [Tue, 11 Sep 2018 06:49:39 +0000 (08:49 +0200)]
serial: samsung: Enable baud clock for UART reset procedure in resume

Ensure that baud clock is also enabled for UART reset in driver resume.
On Exynos5433 SoC this is needed to avoid external abort in UART register
writes.

Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: I2987842ea1b38582bdbceb9ffab3ed1a3b1cbfd2

5 years agoclk: samsung: exynos5433: add workaround for NOIRQ sleep
Marek Szyprowski [Wed, 19 Sep 2018 09:36:55 +0000 (11:36 +0200)]
clk: samsung: exynos5433: add workaround for NOIRQ sleep

Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: I53b8969337a3464eb5cd5d877ce877670895836a

5 years agoclk: samsung: exynos5433: Keep sclk_uart clocks enabled in suspend
Marek Szyprowski [Fri, 11 May 2018 06:50:36 +0000 (08:50 +0200)]
clk: samsung: exynos5433: Keep sclk_uart clocks enabled in suspend

All sclk_uart clocks in TOP CMU have to be kept enabled for suspend/resume
cycle, otherwise TM2(e) boards hangs before entering the suspend mode.

Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: I198880bcee0688c9e33b1e4056b8b60819303945

5 years agoclk: samsung: exynos5433: Add suspend state for TOP, CPIF & PERIC CMUs
Marek Szyprowski [Wed, 29 Aug 2018 16:00:13 +0000 (18:00 +0200)]
clk: samsung: exynos5433: Add suspend state for TOP, CPIF & PERIC CMUs

Before entering system suspend, one has to ensure that some clocks from
TOP, CPIF and PERIC CMUs are enabled. This is needed by the firmware
to properly perform system suspend operation. Instead of adding more and
more clocks with CRITICAL flag, simply enable those clocks directly in
respective CMU registers using 'suspend_regs' feature.

Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
Change-Id: I1dab71d4834fcbd13634411d44ecb11775c46cde

5 years agoclk: samsung: Use NOIRQ stage for Exynos5433 clocks suspend/resume
Marek Szyprowski [Wed, 29 Aug 2018 16:00:12 +0000 (18:00 +0200)]
clk: samsung: Use NOIRQ stage for Exynos5433 clocks suspend/resume

SoC clock drivers should suspend after every other drivers in the system,
which are using clocks and resume before them. The last stage for calling
suspend device callbacks is NOIRQ stage and there exists driver, which use
that state (dwmmc-exynos), so Exynos5433 clocks driver should also use it.
During the same stage, clocks driver will be always suspended after its
clients as a direct result of proper device probe order (deferred probe
reorders the suspend call sequence).

Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Acked-by: Chanwoo Choi <cw00.choi@samsung.com>
Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
Change-Id: I3e15407b8d3ec2d10d706b21321ce098b14a0d50