Hi Mike,
On 22 October 2013 11:20, Chander Kashyap chander.kash...@linaro.org wrote:
On 16 October 2013 11:10, Chander Kashyap chander.kash...@linaro.org wrote:
On 26 September 2013 14:36, Chander Kashyap chander.kash...@linaro.org
wrote:
Fixes cpll control and lock register offset values
From: Tarek Dakhran t.dakh...@samsung.com
The EXYNOS5410 clocks are statically listed and registered
using the Samsung specific common clock helper functions.
Signed-off-by: Tarek Dakhran t.dakh...@samsung.com
Signed-off-by: Vyacheslav Tyrtov v.tyr...@samsung.com
---
The series of patches represent support of Exynos 5410 SoC
The Exynos 5410 is the first Samsung SoC based on bigLITTLE architecture
Patches allow all 8 CPU cores (4 x A7 and 4 x A15) to run at the same time
Patches add new platform description, support of clock controller,
dual cluster support
From: Tarek Dakhran t.dakh...@samsung.com
EXYNOS5410 is SoC in Samsung's Exynos5 SoC series.
Add initial support for this SoC.
Signed-off-by: Tarek Dakhran t.dakh...@samsung.com
Reviewed-by: Tomasz Figa t.f...@samsung.com
Signed-off-by: Vyacheslav Tyrtov v.tyr...@samsung.com
---
From: Tarek Dakhran t.dakh...@samsung.com
Add initial device tree nodes for EXYNOS5410 SoC and SMDK5410 board.
Signed-off-by: Tarek Dakhran t.dakh...@samsung.com
Reviewed-by: Tomasz Figa t.f...@samsung.com
Signed-off-by: Vyacheslav Tyrtov v.tyr...@samsung.com
---
arch/arm/boot/dts/Makefile
On Tue, Nov 26, 2013 at 10:54:57AM +0530, Padma Venkat wrote:
- snd_soc_dai_init_dma_data(dai, i2s-dma_playback,
i2s-dma_capture);
+ samsung_asoc_init_dma_data(dai, i2s-dma_playback,
i2s-dma_capture);
we have to initialize the dma data for i2s secondary dai also
otherwise
On Tue, Nov 26, 2013 at 10:55:17AM +0530, Padma Venkat wrote:
I tested this patch set on smdk5420 i2s. During playback audio playing
fast and there is underrun error like below.
underrun!!! (at least 0.061 ms long)
underrun!!! (at least 0.043 ms long)
This sounds like it's setting the
Hi Mark,
On Tue, Nov 26, 2013 at 3:53 PM, Mark Brown broo...@kernel.org wrote:
On Tue, Nov 26, 2013 at 10:55:17AM +0530, Padma Venkat wrote:
I tested this patch set on smdk5420 i2s. During playback audio playing
fast and there is underrun error like below.
underrun!!! (at least 0.061 ms
On 26 November 2013 09:56, Naveen Krishna Chatradhi
ch.nav...@samsung.com wrote:
This patch adds new compatible to support HSI2C module on Exynos5260
HSI2C module on Exynos5260 needs to be reset during during initialization.
Signed-off-by: Naveen Krishna Chatradhi ch.nav...@samsung.com
[snip]
Hello Sachin,
On 26 November 2013 16:59, Sachin Kamat sachin.ka...@linaro.org wrote:
On 26 November 2013 09:56, Naveen Krishna Chatradhi
ch.nav...@samsung.com wrote:
This patch adds new compatible to support HSI2C module on Exynos5260
HSI2C module on Exynos5260 needs to be reset during during
On Tue, Nov 26, 2013 at 04:18:41PM +0530, Padma Venkat wrote:
I tried this on linux-samsung tree by applying all the patches from
you and Lars.
Can you use -next plus the posted patches please in case there's
something been misplaced, it'll help if we're working from the same code
base?
I
Hi Doug,
Thanks for reviewing the patch series.
On Tue, Nov 26, 2013 at 4:14 AM, Doug Anderson diand...@chromium.org wrote:
Hi Leela Krishna,
On Mon, Nov 18, 2013 at 1:49 AM, Leela Krishna Amudala
l.kris...@samsung.com wrote:
Add device tree support for exynos5250 and 5420 SoCs and use
On 26-11-2013 02:07, Amit Kachhap wrote:
On 10/4/13, Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com wrote:
Menu for Samsung thermal support is visible on all Samsung
platforms while thermal drivers are currently available only
for EXYNOS SoCs. Fix it by replacing PLAT_SAMSUNG dependency
On 2013-11-15 04:52, Sachin Kamat wrote:
+ Tomi
Hi Olof,
On 15 November 2013 02:39, Olof Johansson o...@lixom.net wrote:
commit 7e0be9f9f7cba3356f75b86737dbe3a005da067e ('video: exynos_mipi_dsim:
Use the generic PHY driver') resulted in a warning about an unused
variable:
On 25 November 2013 19:41, Viresh Kumar viresh.ku...@linaro.org wrote:
Currently we have implemented PM notifiers to disable/enable -target()
routines
functionality during suspend/resume.
Now we have support present in cpufreq core, lets use it.
Signed-off-by: Viresh Kumar
On Tue, Nov 26, 2013 at 12:58:08PM +0400, Vyacheslav Tyrtov wrote:
From: Tarek Dakhran t.dakh...@samsung.com
Add EDCS(Exynos Dual Cluster Support) for Samsung Exynos5410 SoC.
This enables all 8 cores, 4 x A7 and 4 x A15 run at the same time.
Signed-off-by: Tarek Dakhran
On 11/25/2013 03:36 PM, Doug Anderson wrote:
On modern SoCs the watchdog timer is parented on a clock that doesn't
change every time we have a cpufreq change. That means we don't need
to constantly adjust the watchdog timer, so avoid registering for and
dealing with cpufreq transitions unless
The existing watchdog timeout worked OK but didn't deal with
rounding in an ideal way when dividing out all of its clocks.
Specifically if you had a timeout of 32 seconds and an input clock of
, you'd end up setting a timeout of 31.9998 seconds and
reporting a timeout of 31 seconds.
On 11/26/2013 10:30 AM, Doug Anderson wrote:
The existing watchdog timeout worked OK but didn't deal with
rounding in an ideal way when dividing out all of its clocks.
Specifically if you had a timeout of 32 seconds and an input clock of
, you'd end up setting a timeout of 31.9998
On Tuesday, November 26, 2013 07:56:19 AM Viresh Kumar wrote:
On 26 November 2013 04:59, Rafael J. Wysocki r...@rjwysocki.net wrote:
@@ -1259,6 +1262,8 @@ int dpm_suspend(pm_message_t state)
might_sleep();
+ cpufreq_suspend();
+
mutex_lock(dpm_list_mtx);
Guenter,
On Tue, Nov 26, 2013 at 10:48 AM, Guenter Roeck li...@roeck-us.net wrote:
On 11/26/2013 10:30 AM, Doug Anderson wrote:
The existing watchdog timeout worked OK but didn't deal with
rounding in an ideal way when dividing out all of its clocks.
Specifically if you had a timeout of 32
On 11/26/2013 01:34 PM, Doug Anderson wrote:
Guenter,
On Tue, Nov 26, 2013 at 10:48 AM, Guenter Roeck li...@roeck-us.net wrote:
On 11/26/2013 10:30 AM, Doug Anderson wrote:
The existing watchdog timeout worked OK but didn't deal with
rounding in an ideal way when dividing out all of its
On 11/26/2013 04:57 PM, Doug Anderson wrote:
The existing watchdog timeout worked OK but didn't deal with
rounding in an ideal way when dividing out all of its clocks.
Specifically if you had a timeout of 32 seconds and an input clock of
, you'd end up setting a timeout of 31.9998
On Tuesday, November 26, 2013 09:23:15 PM Rafael J. Wysocki wrote:
On Tuesday, November 26, 2013 07:56:19 AM Viresh Kumar wrote:
On 26 November 2013 04:59, Rafael J. Wysocki r...@rjwysocki.net wrote:
@@ -1259,6 +1262,8 @@ int dpm_suspend(pm_message_t state)
might_sleep();
+
The existing watchdog timeout worked OK but didn't deal with
rounding in an ideal way when dividing out all of its clocks.
Specifically if you had a timeout of 32 seconds and an input clock of
, you'd end up setting a timeout of 31.9998 seconds and
reporting a timeout of 31 seconds.
Guenter,
On Tue, Nov 26, 2013 at 4:10 PM, Guenter Roeck li...@roeck-us.net wrote:
On 11/26/2013 01:34 PM, Doug Anderson wrote:
Guenter,
On Tue, Nov 26, 2013 at 10:48 AM, Guenter Roeck li...@roeck-us.net
wrote:
On 11/26/2013 10:30 AM, Doug Anderson wrote:
The existing watchdog timeout
On 27 November 2013 07:12, Rafael J. Wysocki r...@rjwysocki.net wrote:
Anyway, if you did what I asked you to do and put the cpufreq suspend/resume
into dpm_suspend/resume_noirq(), I'd probably take this for 3.13. However,
since you've decided to put those things somewhere else thus making the
On 27 November 2013 01:53, Rafael J. Wysocki r...@rjwysocki.net wrote:
On Tuesday, November 26, 2013 07:56:19 AM Viresh Kumar wrote:
On 26 November 2013 04:59, Rafael J. Wysocki r...@rjwysocki.net wrote:
This appears to be racy. Is it really racy, or just seemingly?
Why does it look racy
This patch adds cpufreq callbacks to dpm_{suspend|resume}_noirq() for handling
suspend/resume of cpufreq governors.
There are multiple problems that are fixed by this patch:
- Nishanth Menon (TI) found an interesting problem on his platform, OMAP. His
board
wasn't working well with
ARM_PATCH_PHYS_VIRT and AUTO_ZRELADDR is enabled by default for Exynos
platforms.
Introduction of this config as default will enable phy-to-virt and
virt-to-phy translation function at boot and module loading time
and enforce dynamic reallocation of memory.
This config is mutually exclusive to
Hi Kukjin,
Hi Kukjin,
The TMU device tree node definition for Exynos4x12 family of SoCs.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
Reviewed-by: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com
Reviewed-by: Tomasz Figa t.f...@samsung.com
---
Changes for v2:
-
Hi Kukjin,
Hi Kukjin,
This patch enables support for TMU at Exynos4412 based Trats2 board.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
Reviewed-by: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com
Reviewed-by: Tomasz Figa t.f...@samsung.com
---
Changes for v2:
-
On 2013年11月27日 11:07, Viresh Kumar wrote:
On 27 November 2013 07:12, Rafael J. Wysocki r...@rjwysocki.net wrote:
Anyway, if you did what I asked you to do and put the cpufreq suspend/resume
into dpm_suspend/resume_noirq(), I'd probably take this for 3.13. However,
since you've decided to put
33 matches
Mail list logo
