On Mon, November 25, 2013, Olof Johansson wrote:
Hi,
On Sun, Nov 24, 2013 at 4:07 AM, randy lxr1...@hotmail.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After pull the merge of 3.13-rc1, the dw_mmc-exynos will make the boot
stock.In 3.13, it is just stocked udev in 3.13
From: Ricardo Ribalda ricardo.riba...@gmail.com
vb2_fop_release does not held the lock although it is modifying the
queue-owner field.
This could lead to race conditions on the vb2_perform_io function
when multiple applications are accessing the video device via
read/write API:
[ 308.297741]
Мы отвоевываем людям зрение http://goo.gl/2m4NKq
From: Mark Brown broo...@linaro.org
Ensure that unused I2C controllers are not activated, causing problems due
to inappropriate pinmuxing or similar, by marking the controllers as
disabled by default and requiring boards to explicitly enable those that
are in use.
Signed-off-by: Mark Brown
From: Mark Brown broo...@linaro.org
Make it easier to notice the common file for ChromeOS devices based on
the Exynos5250 by giving it the exynos5250 prefix that the boards have.
Signed-off-by: Mark Brown broo...@linaro.org
Acked-by: Tomasz Figa t.f...@samsung.com
---
From: Mark Brown broo...@linaro.org
Rather than requiring each board to explicitly disable the SPI controllers
it is not using instead require boards to enable those that they are using.
This is less work overall since normally at most one of the controllers is
in use and avoids issues caused by
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
于 2013年11月25日 16:33, Seungwon Jeon 写道:
On Mon, November 25, 2013, Olof Johansson wrote:
Hi,
On Sun, Nov 24, 2013 at 4:07 AM, randy lxr1...@hotmail.com
wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
After pull the merge of 3.13-rc1,
The Frequency lock value should be higher or same than the booting frequency,
which is set by the bootloader. To eliminate possible inconsistency
in frequency, we save and restore frequency during suspend resume
and disable CPUFREQ activity. This should be considered in hibernation also.
This patch adds cpufreq callbacks to dpm_{suspend|resume}() for handling
suspend/resume of cpufreq governors. This is required for early suspend and late
resume of governors and cpufreq core.
There are multiple problems that are fixed by this patch:
- Nishanth Menon (TI) found an interesting
Multiple platforms need to set CPU to a particular frequency before suspending
system. And so they need a common infrastructure which is provided by this
patch. Those platforms just need to initialize their -suspend() pointers with
the generic routine.
Signed-off-by: Viresh Kumar
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 viresh.ku...@linaro.org
---
drivers/cpufreq/tegra-cpufreq.c | 54
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 viresh.ku...@linaro.org
---
drivers/cpufreq/exynos-cpufreq.c | 97
Earlier cpufreq suspend/resume callbacks into drivers were getting called only
for the boot CPU, as by the time callbacks were called non-boot CPUs were
already removed. Because we might still need driver specific actions on
suspend/resume, its better to use earlier infrastructure from the early
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 viresh.ku...@linaro.org
---
drivers/cpufreq/s5pv210-cpufreq.c | 49
This patchset adds cpufreq callbacks to dpm_{suspend|resume}() for handling
suspend/resume of cpufreq governors and core. This is required for early suspend
and late resume of governors and cpufreq core.
There are multiple problems that are fixed by this patch:
- Nishanth Menon (TI) found an
On Wed, Nov 20, 2013 at 1:02 AM, Kyungmin Park kmp...@infradead.org wrote:
On Wed, Nov 20, 2013 at 4:16 AM, Stephen Warren swar...@wwwdotorg.org wrote:
I think that last point should be addressed by having a driver that owns
the GPIO set it to the desired output level, and the implementation
On Wed, Nov 20, 2013 at 3:00 PM, Tomasz Figa t.f...@samsung.com wrote:
Stephen:
Is the lifetime of the string returned by
of_property_read_string_index() really so short that you must copy the
string? I'd be tempted just to store the pointer, although perhaps you
need to get() the node so
Hi,
Could you please apply this patch?
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung RD Institute Poland
Samsung Electronics
On Friday, October 04, 2013 02:36:42 PM Bartlomiej Zolnierkiewicz wrote:
Menu for Samsung thermal support is visible on all Samsung
platforms while thermal
Hi,
Could you please also apply this patch?
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung RD Institute Poland
Samsung Electronics
On Friday, October 04, 2013 02:38:25 PM Bartlomiej Zolnierkiewicz wrote:
There is little sense in having separate config option for
registering EXYNOS TMU
On Tue, Nov 05, 2013 at 05:13:21PM +0100, Kamil Debski wrote:
Change the used phy driver to the new Exynos USB phy driver that uses the
generic phy framework.
Signed-off-by: Kamil Debski k.deb...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
On 25/11/2013 16:34, Linus Walleij wrote:
On Wed, Nov 20, 2013 at 1:02 AM, Kyungmin Park kmp...@infradead.org wrote:
On Wed, Nov 20, 2013 at 4:16 AM, Stephen Warren swar...@wwwdotorg.org wrote:
I think that last point should be addressed by having a driver that owns
the GPIO set it to the
On 11/25/2013 08:11 AM, Viresh Kumar wrote:
This patchset adds cpufreq callbacks to dpm_{suspend|resume}() for handling
suspend/resume of cpufreq governors and core. This is required for early
suspend
and late resume of governors and cpufreq core.
There are multiple problems that are fixed
Hi Leela Krishna,
On Mon, Nov 18, 2013 at 1:49 AM, Leela Krishna Amudala
l.kris...@samsung.com wrote:
This patch adds pmusysreg node to exynos5250 and exynos5420 dtsi files to
handle PMU register accesses in a centralized way using syscon driver
Signed-off-by: Leela Krishna Amudala
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 syscon regmap
interface
to configure AUTOMATIC_WDT_RESET_DISABLE and MASK_WDT_RESET_REQUEST registers
of PMU
to mask/unmask
Leela Krishna,
On Mon, Nov 18, 2013 at 1:49 AM, Leela Krishna Amudala
l.kris...@samsung.com wrote:
In Exynos5 series SoCs, PMU has registers to enable/disable mask/unmask
watchdog timer which is not the case with s3c series SoCs so, there is a
need to have different compatible names for
On Monday, November 25, 2013 07:41:41 PM Viresh Kumar wrote:
This patch adds cpufreq callbacks to dpm_{suspend|resume}() for handling
suspend/resume of cpufreq governors. This is required for early suspend and
late resume of governors and cpufreq core.
There are multiple problems that are
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 we've actually got
CPU_FREQ_S3C24XX defined.
On 11/25/2013 02:55 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
Guenter,
On Mon, Nov 25, 2013 at 3:23 PM, Guenter Roeck li...@roeck-us.net wrote:
On 11/25/2013 02:55 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
On Monday 25 of November 2013 15:23:27 Guenter Roeck wrote:
On 11/25/2013 02:55 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
Tomasz Figa wrote:
Hi Bart,
On Thursday 21 of November 2013 13:06:06 Bartlomiej Zolnierkiewicz wrote:
Current CONFIG_NR_CPUS value (2) is too small for:
- EXYNOS4412 (4 cores)
- EXYNOS5440 (4 cores)
- EXYNOS5410 (8 cores)
- EXYNOS5420 (8 cores)
Set CONFIG_NR_CPUS to 8 so it is
On Monday 25 of November 2013 15:28:29 Doug Anderson wrote:
Guenter,
On Mon, Nov 25, 2013 at 3:23 PM, Guenter Roeck li...@roeck-us.net wrote:
On 11/25/2013 02:55 PM, Doug Anderson wrote:
On modern SoCs the watchdog timer is parented on a clock that doesn't
change every time we have a
Naveen,
On Mon, Nov 18, 2013 at 10:18 PM, Naveen Krishna Chatradhi
ch.nav...@samsung.com wrote:
For Exynos4 and Exynos5 SoCs from Samsung the i2c clock is based
on a fixed 66 MHz peripheral clock, and therefore is completely
independent of the cpu frequency.
Thus, registering for a CPU freq
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 we've actually got
CONFIG_ARM_S3C24XX_CPUFREQ
On Monday 25 of November 2013 15:36:43 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
On Monday 25 of November 2013 14:44:01 Doug Anderson wrote:
+
struct s3c2410_wdt {
struct device *dev;
struct clk *clock;
@@ -94,7 +107,49 @@ struct s3c2410_wdt {
unsigned long wtdat_save;
struct watchdog_device
On Tuesday 26 of November 2013 00:08:31 Ben Dooks wrote:
On Mon, Nov 25, 2013 at 02:55:37PM -0800, 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
On Mon, Nov 25, 2013 at 02:55:37PM -0800, 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
On Monday 25 of November 2013 22:01:42 Kevin Bracey wrote:
On 25/11/2013 16:34, Linus Walleij wrote:
On Wed, Nov 20, 2013 at 1:02 AM, Kyungmin Park kmp...@infradead.org wrote:
On Wed, Nov 20, 2013 at 4:16 AM, Stephen Warren swar...@wwwdotorg.org
wrote:
I think that last point should be
On Monday 25 of November 2013 15:46:12 Linus Walleij wrote:
On Wed, Nov 20, 2013 at 3:00 PM, Tomasz Figa t.f...@samsung.com wrote:
Stephen:
Is the lifetime of the string returned by
of_property_read_string_index() really so short that you must copy the
string? I'd be tempted just to store
On Sunday 24 of November 2013 22:18:46 Olof Johansson wrote:
Hi,
On Sun, Nov 24, 2013 at 4:07 AM, randy lxr1...@hotmail.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After pull the merge of 3.13-rc1, the dw_mmc-exynos will make the boot
stock.In 3.13, it is just stocked
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
于 2013年11月26日 08:41, Tomasz Figa 写道:
On Sunday 24 of November 2013 22:18:46 Olof Johansson wrote:
Hi,
On Sun, Nov 24, 2013 at 4:07 AM, randy lxr1...@hotmail.com
wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
After pull the merge of
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);
pm_transition = state;
async_error = 0;
Shouldn't it do
Hello Doug,
On 26 November 2013 05:11, Doug Anderson diand...@chromium.org wrote:
Naveen,
On Mon, Nov 18, 2013 at 10:18 PM, Naveen Krishna Chatradhi
ch.nav...@samsung.com wrote:
For Exynos4 and Exynos5 SoCs from Samsung the i2c clock is based
on a fixed 66 MHz peripheral clock, and
On Monday 25 November 2013 07:41 PM, Viresh Kumar wrote:
diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
index dc196bb..6d93f91 100644
--- a/include/linux/cpufreq.h
+++ b/include/linux/cpufreq.h
@@ -255,6 +255,9 @@ struct cpufreq_driver {
int cpufreq_register_driver(struct
For Exynos4 and Exynos5 SoCs from Samsung the i2c clock is based
on a fixed 66 MHz peripheral clock, and therefore is completely
independent of the cpu frequency.
Thus, registering for a CPU freq notifier is very wasteful.
This patch modifes the code such that, i2c bus registers to
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
---
Changes since v1:
Rebasing on linux-i2c for-next
fifo_depth of the HSI2C is not constant
Exynos5420 and Exynos5250 supports fifo_depth of 64bytes
Exynos5260 supports fifo_depth of 16bytes
This patch configures the fifo_depth based on HSI2C modules version.
Signed-off-by: Naveen Krishna Chatradhi ich.nav...@samsung.com
[For finding out the
Hi, Randy,
It seems a problem that controller didn't find the clock source.
Also you can see the below message. Did you check the clock source?
[1.125000] s3c-sdhci 1255.sdhci: failed to get io clock
Actually, need to prevent the null pointer dereference for clock in dw-mmc.c
And If
Hi Mark,
On Tue, Nov 12, 2013 at 7:18 PM, Mark Brown broo...@kernel.org wrote:
From: Mark Brown broo...@linaro.org
In preparation for using the dmaengine helpers in ASoC rather than the
dmaengine wrappers for the Samsung API wrap the configuration of dma_data.
The dmaengine code expects
Hi Mark,
On Tue, Nov 12, 2013 at 7:18 PM, Mark Brown broo...@kernel.org wrote:
From: Mark Brown broo...@linaro.org
Since all Exynos platforms have been converted to dmaengine and many of
the older platforms are in the process of conversion they do not need to
use the legacy s3c-dma APIs for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks Jaehoon,
I have noticed that before it, but in dw_mmc driver, I won't meet this
problem.
As you can seen in dts, I have defined a clock source.
Or the clock source what I choose is not correct?
I don't know how to debug this, I don't know much
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
with ARCH_EXYNOS one.
Signed-off-by:
On 11/25/13, Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com wrote:
Hi,
Could you please also apply this patch?
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung RD Institute Poland
Samsung Electronics
On Friday, October 04, 2013 02:38:25 PM Bartlomiej Zolnierkiewicz wrote:
There
On 2013年11月25日 22:11, Viresh Kumar wrote:
This patchset adds cpufreq callbacks to dpm_{suspend|resume}() for handling
suspend/resume of cpufreq governors and core. This is required for early
suspend
and late resume of governors and cpufreq core.
There are multiple problems that are fixed
55 matches
Mail list logo
