Hi Tomasz,
On Sun, Nov 10, 2013 at 7:38 PM, Tomasz Figa tomasz.f...@gmail.com wrote:
Hi Vivek,
On Thursday 31 of October 2013 13:15:41 Vivek Gautam wrote:
Add a new driver for the USB 3.0 PHY on Exynos5 series of SoCs.
The new driver uses the generic PHY framework and will interact
with
On Wed, Nov 20, 2013 at 2:14 PM, Vivek Gautam gautamvivek1...@gmail.com wrote:
Hi Tomasz,
On Sun, Nov 10, 2013 at 7:38 PM, Tomasz Figa tomasz.f...@gmail.com wrote:
Hi Vivek,
On Thursday 31 of October 2013 13:15:41 Vivek Gautam wrote:
Add a new driver for the USB 3.0 PHY on Exynos5 series
Hi Kishon,
On Mon, Nov 11, 2013 at 4:41 PM, Kishon Vijay Abraham I kis...@ti.com wrote:
Hi,
sorry for the delayed response.
On Wednesday 06 November 2013 05:37 AM, Jingoo Han wrote:
On Wednesday, November 06, 2013 2:58 AM, Vivek Gautam wrote:
On Tue, Nov 5, 2013 at 5:33 PM, Jingoo Han
On Wednesday 20 November 2013 02:27 PM, Vivek Gautam wrote:
Hi Kishon,
On Mon, Nov 11, 2013 at 4:41 PM, Kishon Vijay Abraham I kis...@ti.com wrote:
Hi,
sorry for the delayed response.
On Wednesday 06 November 2013 05:37 AM, Jingoo Han wrote:
On Wednesday, November 06, 2013 2:58 AM,
On Wed, Nov 20, 2013 at 2:34 PM, Kishon Vijay Abraham I kis...@ti.com wrote:
On Wednesday 20 November 2013 02:27 PM, Vivek Gautam wrote:
Hi Kishon,
On Mon, Nov 11, 2013 at 4:41 PM, Kishon Vijay Abraham I kis...@ti.com
wrote:
Hi,
sorry for the delayed response.
On Wednesday 06 November
On Tue, Nov 19, 2013 at 10:30 PM, Jonghwan Choi jhbird.c...@gmail.com wrote:
Frequency lock should be considered in suspend/hibernation.
Signed-off-by: Jonghwan Choi jhbird.c...@samsung.com
Signed-off-by: MyungJoo Ham myungjoo@samsung.com
Applied in driver-update branch.
Do you want this
On Tue, Nov 19, 2013 at 10:30 PM, Jonghwan Choi jhbird.c...@gmail.com wrote:
Frequency lock should be considered in suspend/hibernation.
Signed-off-by: Jonghwan Choi jhbird.c...@samsung.com
Signed-off-by: MyungJoo Ham myungjoo@samsung.com
Cheers,
MyungJoo.
---
On Wed, Nov 20, 2013 at 7:08 AM, Sebastian Capella
sebastian.cape...@linaro.org wrote:
Quoting Bartlomiej Zolnierkiewicz (2013-11-19 06:50:05)
Hi,
Are you planning to add hibernation support to ARM?
If so then this should be stated somewhere in the patch description.
OTOH if you are not
On Mon, Oct 21, 2013 at 06:04:35AM +0900, Kukjin Kim wrote:
Applied this whole series.
This didn't seem to make it into -next or your tree, it'd be really
helpful to be able to merge into both ASoC and SPI so they can be used
for some framework work (I already have some patches for ASoC).
On Tue, Nov 19, 2013 at 05:07:04PM -0700, Stephen Warren wrote:
On 11/19/2013 05:02 PM, Kyungmin Park wrote:
Some pins are not connected (NC). At that cases, there's no drivers to
handle it. To reduce power leakage, it sets proper configuration with
values instead of reset values.
Hmm.
Hi Stephen,
On Tuesday 19 of November 2013 11:46:10 Stephen Warren wrote:
On 11/19/2013 10:15 AM, Tomasz Figa wrote:
This patch extends the range of settings configurable via pinfunc API
to cover pin value as well. This allows configuration of default values
of pins.
Shouldn't there be
Hi,
On 20.11.2013 03:23, Tomasz Figa wrote:
Hi,
On Thursday 07 of November 2013 12:12:45 Vyacheslav Tyrtov wrote:
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
Hi Stephen,
On Tuesday 19 of November 2013 12:10:01 Stephen Warren wrote:
On 11/19/2013 10:10 AM, Tomasz Figa wrote:
One of remaining limitations of current pinctrl-samsung driver was
the inability to parse multiple pinmux/pinconf group nodes grouped
inside a single device tree node. It
On Tuesday 19 of November 2013 10:59:39 Doug Anderson wrote:
On Tue, Nov 19, 2013 at 10:46 AM, Stephen Warren swar...@wwwdotorg.org
wrote:
On 11/19/2013 10:15 AM, Tomasz Figa wrote:
This patch extends the range of settings configurable via pinfunc API
to cover pin value as well. This
Hi,
On Wednesday 20 November 2013 03:02 PM, Vivek Gautam wrote:
On Wed, Nov 20, 2013 at 2:34 PM, Kishon Vijay Abraham I kis...@ti.com wrote:
On Wednesday 20 November 2013 02:27 PM, Vivek Gautam wrote:
Hi Kishon,
On Mon, Nov 11, 2013 at 4:41 PM, Kishon Vijay Abraham I kis...@ti.com
wrote:
These tables are all immutable, make them const to save 4416 bytes of RAM.
size arch/arm/mach-exynos/pmu.o
textdata bss
8484420 4 // before
5264 4 4 // after
Signed-off-by: Daniel Kurtz djku...@chromium.org
---
arch/arm/mach-exynos/pmu.c |
The restore functions do not modify the passed in struct sleep_save,
so that parameter can be const.
This allows us to pass in const struct. This allows us to use const
structs sleep_save to define system registers that will always be
restored to a constant value.
Signed-off-by: Daniel Kurtz
The clksrc tables are constant, they are not used to store register values
at suspend.
size arch/arm/mach-exynos/pm.o
textdata bss
1591 212 12// Before
1671 132 12// After
Signed-off-by: Daniel Kurtz djku...@chromium.org
---
arch/arm/mach-exynos/pm.c |
Add CLK_SET_RATE_PARENT flag to be able to change the frequency
to desired value.
Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
---
drivers/clk/samsung/clk-exynos5250.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/clk/samsung/clk-exynos5250.c
Use common clock framework (CCF) APIs to set the clock rates
instead of direct register manipulation. This now updates the
sysfs entry (cpuinfo_cur_freq) correctly which did not reflect
the correct value until now. While at it clean up the PLL s-div
parameter setting as it is handled by the PLL
Hello Wim Van Sebroeck,
Can you please review this series and take necessary action.
Best Wishes,
Leela Krishna.
On Mon, Nov 18, 2013 at 4:35 PM, Tomasz Figa t.f...@samsung.com wrote:
Hi Leela,
On Monday 18 of November 2013 15:19:46 Leela Krishna Amudala wrote:
This patchset does the
On 21 November 2013 10:14, Sachin Kamat sachin.ka...@linaro.org wrote:
Use common clock framework (CCF) APIs to set the clock rates
instead of direct register manipulation. This now updates the
sysfs entry (cpuinfo_cur_freq) correctly which did not reflect
the correct value until now. While at
22 matches
Mail list logo
