Hi Nishanth, Viresh
If I may add my 2 cents.
On Tue, May 13, 2014 at 10:40 PM, Viresh Kumar
viresh.ku...@linaro.org wrote:
On 14 May 2014 06:32, Thomas Abraham ta.oma...@gmail.com wrote:
[...]
+#ifdef CONFIG_CPU_FREQ_BOOST_SW
+ if (of_find_property(dev-of_node, boost-frequency,
From: avnd kiran avnd.ki...@samsung.com
Latest MFC v6 firmware requires tile mode and loop filter
setting to be done as part of Init buffer command, in sync
with v7. Since there are two versions of v6 firmware with
different interfaces, it is differenciated using the version
number read back from
Hi Viresh, Tomas,
On 14 May 2014 06:41, Thomas Abraham ta.oma...@gmail.com wrote:
From: Thomas Abraham thomas...@samsung.com
Lookup for the optional boost-frequency property in cpu0 node and if
available, enable support for boost mode frequencies. The
frequencies usable in boost mode
On 14 May 2014 11:47, Lukasz Majewski l.majew...@samsung.com wrote:
I think that you can rely solely on the CPU_FREQ_BOOST_SW flag if the
original author of cpufreq-cpu0.c don't mind.
We don't have to. struct cpufreq_driver: boost_supported is always available.
Just update it without any ugly
On 14 May 2014 11:39, Lukasz Majewski l.majew...@samsung.com wrote:
I agree with Nishanth here, that point 1 (as described by Viresh at
[*]) is a more scalable approach.
The only reason why I wanted all that to be done at OPP level was to
ensure if somebody else also needs it apart from
From: Pawel Osciak posc...@chromium.org
Currently, we allocate private codec buffers on STREAMON, which may fail
if we are out of memory. We don't check for failure though, which will
make us crash with the codec accessing random memory.
We shouldn't be failing STREAMON with out of memory errors
To support MIPI DSI command mode interface, the panel should generates
Tearing Effect synchronization signal between MCU and FB to display
video images.
And the display controller should trigger to transfer video image at
this signal.
So the panel receives the TE IRQ, then calls this handler
This patch adds helper functions to convert cmdmode
to drm_display_mode
Signed-off-by: YoungJun Cho yj44@samsung.com
Acked-by: Inki Dae inki@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/gpu/drm/drm_modes.c | 59 +++
This patch adds DT bindings for command mode display timing.
Signed-off-by: YoungJun Cho yj44@samsung.com
Acked-by: Inki Dae inki@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
.../bindings/video/cmdmode-display-timing.txt | 64
1 file
This patch adds relevant to exynos5420 compatible for exynos5420 SoC support.
Signed-off-by: YoungJun Cho yj44@samsung.com
Acked-by: Inki Dae inki@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
.../devicetree/bindings/video/exynos_dsim.txt |4 +++-
1 file
There could be the case that the page flip operation isn't finished correctly
with some abnormal condition such as panel reset. So this patch replaces
wait_event() with wait_event_timeout() to avoid waiting for page flip completion
infinitely.
Signed-off-by: YoungJun Cho yj44@samsung.com
This configuration could be used in MIPI DSI command mode also.
Signed-off-by: YoungJun Cho yj44@samsung.com
Acked-by: Inki Dae inki@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/gpu/drm/exynos/exynos_drm_dsi.c |5 +++--
1 file changed, 3 insertions(+), 2
This patch adds DT bindings for s6e3fa0 panel.
The bindings describes panel resources, display timings and cpu mode timings.
Signed-off-by: YoungJun Cho yj44@samsung.com
Acked-by: Inki Dae inki@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
The offset of register DSIM_PLLTMR_REG in Exynos5420 is different
from the one in Exynos4 SoC.
In case of Exynos5420 SoC, there is no frequency band bit in DSIM_PLLCTRL_REG,
and it uses DSIM_PHYCTRL_REG and DSIM_PHYTIMING*_REG instead.
So this patch adds driver data to distinguish it.
This patch adds sysreg device node, and sysreg property to fimd device node
which is required to use I80 interface.
Signed-off-by: YoungJun Cho yj44@samsung.com
Acked-by: Inki Dae inki@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
arch/arm/boot/dts/exynos5.dtsi |6
This patch is based on videomode and display_timing relevant codes.
To support command mode panel, it does not need to guide its timing
information to the display controller like video mode panel,
but it requires signal timings to transfer video data.
So this patch adds cmdmode struct,
Hi,
This series is for the Exynos DRM driver to support MIPI DSI command mode
display and based on exynos-drm-next branch.
The previous patches,
RFC: http://www.spinics.net/lists/dri-devel/msg58898.html
Patches 1 and 2 fix trivial bugs.
Patches 3 and 4 introduce command mode and command mode
This patch adds common part of dsi node.
Signed-off-by: YoungJun Cho yj44@samsung.com
Acked-by: Inki Dae inki@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
arch/arm/boot/dts/exynos5420.dtsi | 14 ++
1 file changed, 14 insertions(+)
diff --git
This patch adds sysreg property to fimd device node which is required
to use I80 interface.
Signed-off-by: YoungJun Cho yj44@samsung.com
Acked-by: Inki Dae inki@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
arch/arm/boot/dts/exynos4.dtsi |1 +
1 file changed, 1
This patch adds MIPI-DSI command mode based S6E3FA0 AMOLED LCD Panel driver.
Signed-off-by: YoungJun Cho yj44@samsung.com
Acked-by: Inki Dae inki@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/gpu/drm/panel/Kconfig |7 +
To support command mode interface, the DSI host calls this handler
to notify the panel tearing effect synchronization signal to the
CRTC device manager to trigger to transfer video image.
Signed-off-by: YoungJun Cho yj44@samsung.com
Acked-by: Inki Dae inki@samsung.com
Acked-by: Kyungmin
This patch adds mipi-phy node for MIPI-DSI device.
Signed-off-by: YoungJun Cho yj44@samsung.com
Acked-by: Inki Dae inki@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
arch/arm/boot/dts/exynos5420.dtsi |6 ++
1 file changed, 6 insertions(+)
diff --git
To support MIPI DSI command mode interface, FIMD should do followings:
- Sets LCD block configuration for I80 interface.
- Uses lcd_sys as an IRQ resource and sets relevant IRQ configuration.
- Implements trigger feature which transfers image date if there is
page flip request, and implements TE
This patch adds relevant to exynos5 compatible for exynos5 SoCs.
Signed-off-by: YoungJun Cho yj44@samsung.com
Acked-by: Inki Dae inki@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
.../devicetree/bindings/arm/samsung/sysreg.txt |1 +
1 file changed, 1
In case of using MIPI command mode interface panel,
the relevant registers should be set.
So this patch adds relevant DT bindings.
Signed-off-by: YoungJun Cho yj44@samsung.com
Acked-by: Inki Dae inki@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
MFCv6 encoder needs specific minimum number of buffers to
be queued in the CAPTURE plane. This minimum number will
be known only when the sequence header is generated.
So we used to allow STREAMON on the CAPTURE plane only after
sequence header is generated and checked with the minimum
buffer
Update the MPEG4 decoder scratch buffer size as per the
new v6 firmware. This updation is increasing the size and so
is backward compatible with older v6 firmwares.
Signed-off-by: Arun Kumar K arun...@samsung.com
---
drivers/media/platform/s5p-mfc/regs-mfc-v6.h |3 +--
1 file changed, 1
This patchset adds MFCv8 support to the s5p-mfc driver.
MFCv8 has the same operation sequence as that of v6+, but
there is some shuffling of the registers happened. So to
re-use the exisiting code, register access uses context
variables instead of macros.
The patchset modifies opr_v6 file to use
Renaming the IS_MFCV7 macro to IS_MFCV7_PLUS for the
addition of MFCv8 support which reuses the v7 code.
Signed-off-by: Arun Kumar K arun...@samsung.com
---
drivers/media/platform/s5p-mfc/s5p_mfc_common.h |2 +-
drivers/media/platform/s5p-mfc/s5p_mfc_enc.c|2 +-
From: Kiran AVND avnd.ki...@samsung.com
This patch adds core support for v8 encoder. This
patch also adds register definitions and buffer size
requirements for H264 VP8 encoding, needed for new
firmware version v8 for MFC
Signed-off-by: Kiran AVND avnd.ki...@samsung.com
Signed-off-by: Pawel
From: Kiran AVND avnd.ki...@samsung.com
This patch adds variant data and core support for
V8 decoder. This patch also adds the register definition
file for new firmware version v8 for MFC.
Signed-off-by: Kiran AVND avnd.ki...@samsung.com
Signed-off-by: Pawel Osciak posc...@chromium.org
Hi Tomasz,
On 05/14/2014 01:28 AM, Tomasz Figa wrote:
Hi Chanwoo,
On 13.05.2014 13:49, Chanwoo Choi wrote:
Hi Tomasz,
On 04/26/2014 09:39 AM, Tomasz Figa wrote:
Hi Chanwoo,
On 25.04.2014 03:16, Chanwoo Choi wrote:
From: Tomasz Figa t.f...@samsung.com
This patch add new the clock
This patchset adds a source_change event to the v4l2-events.
This can be used for notifying the userspace about runtime
format changes happening on video nodes / pads like resolution
change in video decoder.
Changes from v4
--
- Addressed comments from Hans
This event indicates that the video device has encountered
a source parameter change during runtime. This can typically be a
resolution change detected by a video decoder OR a format change
detected by an input connector.
This needs to be nofified to the userspace and the application may
be
From: Pawel Osciak posc...@chromium.org
When a resolution change point is reached, queue an event to signal the
userspace that a new set of buffers is required before decoding can
continue.
Signed-off-by: Pawel Osciak posc...@chromium.org
Signed-off-by: Arun Kumar K arun...@samsung.com
---
On 05/14/2014 08:29 AM, Arun Kumar K wrote:
MFCv6 encoder needs specific minimum number of buffers to
be queued in the CAPTURE plane. This minimum number will
be known only when the sequence header is generated.
So we used to allow STREAMON on the CAPTURE plane only after
sequence header is
On 05/14/2014 08:59 AM, Arun Kumar K wrote:
This patchset adds a source_change event to the v4l2-events.
This can be used for notifying the userspace about runtime
format changes happening on video nodes / pads like resolution
change in video decoder.
Looks good. I'll merge this after the
Hi Thomas,
-config ARM_EXYNOS_CPU_FREQ_BOOST_SW
- bool EXYNOS Frequency Overclocking - Software
- depends on ARM_EXYNOS_CPUFREQ
- select CPU_FREQ_BOOST_SW
- select EXYNOS_THERMAL
- help
- This driver supports software managed overclocking (BOOST).
- It
Add machine-dependent MCPM call-backs for Exynos5420. These are used
to power up/down the secondary CPUs during boot, shutdown, s2r and
switching.
Signed-off-by: Thomas Abraham thomas...@samsung.com
Signed-off-by: Inderpal Singh inderpa...@samsung.com
Signed-off-by: Andrew Bresticker
Hi Nicolas,
[...]
1) can't create /sys/devices/system/cpu/cpu//online: nonexistent directory
What do you get if you do:
$ ls -d /sys/devices/system/cpu/cpu?/online
ls: /sys/devices/system/cpu/cpu//online: No such file or directory
?
2) sleep: invalid number '.0026736'
A sufficiently
On 9 May 2014 14:04, Chander Kashyap chander.kash...@linaro.org wrote:
On 9 May 2014 13:47, Tomasz Figa t.f...@samsung.com wrote:
Hi Chander,
On 09.05.2014 09:50, Chander Kashyap wrote:
On 5 May 2014 09:37, Chander Kashyap chander.kash...@linaro.org wrote:
On 25 April 2014 11:14, Chander
In order to support cpuidle through mcpm, suspend and powered-up
callbacks are required in mcpm platform code.
Hence populate the same callbacks.
Signed-off-by: Chander Kashyap chander.kash...@linaro.org
Signed-off-by: Chander Kashyap k.chan...@samsung.com
---
Changes in v5:
1. Add
The address of cpu power registers in pmu is based on cpu number
offsets. This function calculate the same. This is essentially
required in case of multi-cluster SoC's e.g Exynos5420.
Signed-off-by: Chander Kashyap chander.kash...@linaro.org
Signed-off-by: Chander Kashyap k.chan...@samsung.com
Exynos5420 is a big-little Soc from Samsung. It has 4 A15 and 4 A7 cores.
This patchset adds cpuidle support for Exynos5420 SoC based on
generic big.little cpuidle driver.
Tested on SMDK5420.
This patch set depends on:
1. [PATCH 0/5] MCPM backend for Exynos5420
Exynos5420 is big.Little Soc. It uses cpuidle-big-litle generic cpuidle driver.
Hence do not allow exynos cpuidle driver registration for Exynos5420.
Signed-off-by: Chander Kashyap chander.kash...@linaro.org
Signed-off-by: Chander Kashyap k.chan...@samsung.com
Acked-by: Daniel Lezcano
Add samsung,exynos5420 compatible string to initialize generic
big-little cpuidle driver for Exynos5420.
Signed-off-by: Chander Kashyap chander.kash...@linaro.org
Signed-off-by: Chander Kashyap k.chan...@samsung.com
Acked-by: Daniel Lezcano daniel.lezc...@linaro.org
---
Changes in v4: None
This driver will be used by many big.Little Soc's. As of now it does
string matching of hardcoded compatible string to init the driver. This
comparison list will keep on growing with addition of new SoC's.
Hence add of_device_id structure to collect the compatible strings of
SoC's using this
Add support to select generic big-little cpuidle driver for Samsung Exynos
series SoC's. This is required for Exynos big-little SoC's eg, Exynos5420.
Signed-off-by: Chander Kashyap chander.kash...@linaro.org
Signed-off-by: Chander Kashyap k.chan...@samsung.com
---
Changes in v4:
1. Typo
Hi Hans,
On 05/14/14 12:39, Hans Verkuil wrote:
On 05/14/2014 08:29 AM, Arun Kumar K wrote:
MFCv6 encoder needs specific minimum number of buffers to
be queued in the CAPTURE plane. This minimum number will
be known only when the sequence header is generated.
So we used to allow STREAMON on
Hi Arun,
On 14/05/14 08:59, Arun Kumar K wrote:
This event indicates that the video device has encountered
a source parameter change during runtime. This can typically be a
resolution change detected by a video decoder OR a format change
detected by an input connector.
This needs to be
On 14/05/14 08:59, Arun Kumar K wrote:
From: Pawel Osciak posc...@chromium.org
When a resolution change point is reached, queue an event to signal the
userspace that a new set of buffers is required before decoding can
continue.
Signed-off-by: Pawel Osciak posc...@chromium.org
On Wed, May 14, 2014 at 11:23:33AM +0530, Shaik Ameer Basha wrote:
.../devicetree/bindings/iommu/samsung,sysmmu.txt |5 +
1 file changed, 5 insertions(+)
Applied, thanks.
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to
Hi,
Thank you for this patch.
From: Arun Kumar K [mailto:arunkk.sams...@gmail.com] On Behalf Of Arun
Kumar K
Sent: Wednesday, May 14, 2014 9:00 AM
To: linux-me...@vger.kernel.org; linux-samsung-soc@vger.kernel.org
Cc: k.deb...@samsung.com; s.nawro...@samsung.com; hverk...@xs4all.nl;
On 05/14/2014 10:03 AM, Chander Kashyap wrote:
Exynos5420 is a big-little Soc from Samsung. It has 4 A15 and 4 A7 cores.
This patchset adds cpuidle support for Exynos5420 SoC based on
generic big.little cpuidle driver.
Hi Chander,
just a side question. I am not succeeding to have both
Hi Daniel,
On 14 May 2014 15:26, Daniel Lezcano daniel.lezc...@linaro.org wrote:
On 05/14/2014 10:03 AM, Chander Kashyap wrote:
Exynos5420 is a big-little Soc from Samsung. It has 4 A15 and 4 A7 cores.
This patchset adds cpuidle support for Exynos5420 SoC based on
generic big.little cpuidle
On Wed, May 14, 2014 at 08:49:06AM +0530, Tushar Behera wrote:
Adding missing pm ops so that audio playback works across
suspend and resume cycle.
Applied, thanks.
signature.asc
Description: Digital signature
On 9 May 2014 15:39, Yuvaraj Kumar C D yuvaraj...@gmail.com wrote:
From: Andrew Bresticker abres...@chromium.org
The RPMB partition should only be accessed through the RPMB ioctls
and not through read()/write(). This patch makes mmc_blk_open()
reject open attempts to the RPMB partition in
exynos_drm_init() does probing of various drivers like dp_panel,
hdmi, fimd, mixer, etc in an order and finally binds them together.
Some of the drm devices (Eg: dp_panel) try to do regulator_get()
and enable few supplies during their probe.
Chances are that, these devices may get probed before
On Wednesday 14 May 2014 11:23:33 Shaik Ameer Basha wrote:
The current dt binding for Exynos System MMU can be changed, if found
incompatible with the support for Generic IOMMU Binding.
This patch adds a note to the binding documentation stating the same.
Signed-off-by: Shaik Ameer Basha
On Wednesday 14 May 2014 06:41:15 Thomas Abraham wrote:
From: Thomas Abraham thomas...@samsung.com
Remove the platform device instantiation for Exynos specific cpufreq
driver and add the platform device for cpufreq-cpu0 driver.
Signed-off-by: Thomas Abraham thomas...@samsung.com
---
On Wednesday 14 May 2014 06:41:08 Thomas Abraham wrote:
The patch series removes the use of Exynos specific cpufreq driver and enables
the use of cpufreq-cpu0 driver for Exynos4210, Exynos4x12 and Exynos5250 based
platforms. This is being done for few reasons.
(a) The Exynos cpufreq driver
On Wednesday 14 May 2014 13:33:55 Chander Kashyap wrote:
diff --git a/drivers/cpuidle/cpuidle-big_little.c
b/drivers/cpuidle/cpuidle-big_little.c
index 4cd02bd..344d79fa 100644
--- a/drivers/cpuidle/cpuidle-big_little.c
+++ b/drivers/cpuidle/cpuidle-big_little.c
@@ -165,6 +165,7 @@ static
On 14 May 2014 18:20, Arnd Bergmann a...@arndb.de wrote:
Could we please come up with a way to probe this from DT in the cpufreq-cpu0
driver itself, so we don't have to add a device in every platform using it?
Its followed that way because DT Maintainers had strong objections
to creating
On 14 May 2014 18:21, Arnd Bergmann a...@arndb.de wrote:
Thanks a lot for your continued effort. Looks great overall, but I have one
comment about the general way the cpu0 cpufreq driver works, not specific
to the exynos implementation. See my reply to patch 4.
I hope you meant 7 here instead
Am Mittwoch, 14. Mai 2014, 18:35:29 schrieb Viresh Kumar:
On 14 May 2014 18:20, Arnd Bergmann a...@arndb.de wrote:
Could we please come up with a way to probe this from DT in the
cpufreq-cpu0 driver itself, so we don't have to add a device in every
platform using it?
Its followed that way
On 14 May 2014 18:41, Heiko Stübner he...@sntech.de wrote:
Am Mittwoch, 14. Mai 2014, 18:35:29 schrieb Viresh Kumar:
On 14 May 2014 18:20, Arnd Bergmann a...@arndb.de wrote:
Could we please come up with a way to probe this from DT in the
cpufreq-cpu0 driver itself, so we don't have to add a
On Wednesday 14 May 2014 18:37:13 Viresh Kumar wrote:
On 14 May 2014 18:21, Arnd Bergmann a...@arndb.de wrote:
Thanks a lot for your continued effort. Looks great overall, but I have one
comment about the general way the cpu0 cpufreq driver works, not specific
to the exynos implementation.
On Wed, May 14, 2014 at 7:32 AM, Nishanth Menon n...@ti.com wrote:
On Tue, May 13, 2014 at 8:03 PM, Thomas Abraham ta.oma...@gmail.com wrote:
From: Thomas Abraham thomas...@samsung.com
Add a new optional boost-frequency binding for specifying the frequencies
usable in boost mode.
Cc:
On Wednesday 14 May 2014 18:44:46 Viresh Kumar wrote:
On 14 May 2014 18:41, Heiko Stübner he...@sntech.de wrote:
Am Mittwoch, 14. Mai 2014, 18:35:29 schrieb Viresh Kumar:
On 14 May 2014 18:20, Arnd Bergmann a...@arndb.de wrote:
Could we please come up with a way to probe this from DT in
On Wed, May 14, 2014 at 9:20 AM, Viresh Kumar viresh.ku...@linaro.org wrote:
On 14 May 2014 06:41, Thomas Abraham ta.oma...@gmail.com wrote:
From: Thomas Abraham thomas...@samsung.com
Access to samsung clock lock is required to support newer samsung specific
clock types. So change the scope
On Wed, 14 May 2014, Abhilash Kesavan wrote:
Hi Nicolas,
[...]
1) can't create /sys/devices/system/cpu/cpu//online: nonexistent directory
What do you get if you do:
$ ls -d /sys/devices/system/cpu/cpu?/online
ls: /sys/devices/system/cpu/cpu//online: No such file or directory
Hi Nicolas,
On Wed, May 14, 2014 at 7:03 PM, Nicolas Pitre nicolas.pi...@linaro.org wrote:
On Wed, 14 May 2014, Abhilash Kesavan wrote:
Hi Nicolas,
[...]
1) can't create /sys/devices/system/cpu/cpu//online: nonexistent directory
What do you get if you do:
$ ls -d
Hi Lukasz, Viresh,
On Wed, May 14, 2014 at 11:50 AM, Viresh Kumar viresh.ku...@linaro.org wrote:
On 14 May 2014 11:47, Lukasz Majewski l.majew...@samsung.com wrote:
I think that you can rely solely on the CPU_FREQ_BOOST_SW flag if the
original author of cpufreq-cpu0.c don't mind.
We don't
Hi Chanwoo
On 14.05.2014 08:57, Chanwoo Choi wrote:
On 05/14/2014 01:28 AM, Tomasz Figa wrote:
On 13.05.2014 13:49, Chanwoo Choi wrote:
On 04/26/2014 09:39 AM, Tomasz Figa wrote:
On 25.04.2014 03:16, Chanwoo Choi wrote:
+/* GATE_BLOCK */
+GATE(CLK_BLOCK_LCD, block_lcd, div_aclk_160,
On Wed, May 14, 2014 at 8:18 AM, Arnd Bergmann a...@arndb.de wrote:
On Wednesday 14 May 2014 18:44:46 Viresh Kumar wrote:
On 14 May 2014 18:41, Heiko Stübner he...@sntech.de wrote:
Am Mittwoch, 14. Mai 2014, 18:35:29 schrieb Viresh Kumar:
On 14 May 2014 18:20, Arnd Bergmann a...@arndb.de
On Wed, May 14, 2014 at 9:10 AM, Viresh Kumar viresh.ku...@linaro.org wrote:
On 14 May 2014 06:32, Thomas Abraham ta.oma...@gmail.com wrote:
From: Thomas Abraham thomas...@samsung.com
Commit 6f19efc0 (cpufreq: Add boost frequency support in core) adds
support for CPU boost mode. This patch
On Wed, May 14, 2014 at 11:54 AM, Viresh Kumar viresh.ku...@linaro.org wrote:
On 14 May 2014 11:39, Lukasz Majewski l.majew...@samsung.com wrote:
I agree with Nishanth here, that point 1 (as described by Viresh at
[*]) is a more scalable approach.
The only reason why I wanted all that to be
On 14 May 2014 19:13, Thomas Abraham ta.oma...@gmail.com wrote:
Okay, so you are suggesting that Kconfig entry used to select
cpufreq-cpu0 should also enable CPU_FREQ_BOOST_SW config as well.
I never said that... That should be enabled by your defconfig instead.
What I said was, don't put code
Hi Lukasz,
On Wed, May 14, 2014 at 12:50 PM, Lukasz Majewski
l.majew...@samsung.com wrote:
Hi Thomas,
-config ARM_EXYNOS_CPU_FREQ_BOOST_SW
- bool EXYNOS Frequency Overclocking - Software
- depends on ARM_EXYNOS_CPUFREQ
- select CPU_FREQ_BOOST_SW
- select EXYNOS_THERMAL
-
On 14 May 2014 19:16, Thomas Abraham ta.oma...@gmail.com wrote:
On Wed, May 14, 2014 at 9:10 AM, Viresh Kumar viresh.ku...@linaro.org wrote:
Why is this present outside of above if {} ? as boost_freqs is guaranteed to
be NULL without that.
Just to reduce indentation by one tab. No technical
Add required fixed-regulator for VBUS supply for USB 3.0
controller phy.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
arch/arm/boot/dts/exynos5420-peach-pit.dts | 46
1 file changed, 46 insertions(+)
diff --git
From: Vivek gautam gautam.vi...@samsung.com
Add required fixed-regulator for VBUS supply for USB 3.0
controller phy.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
arch/arm/boot/dts/exynos5800-peach-pi.dts | 46 +
1 file changed, 46 insertions(+)
diff
Add required fixed-regulator for VBUS supply for USB 3.0
controller phy.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
arch/arm/boot/dts/exynos5420-smdk5420.dts | 46 +
1 file changed, 46 insertions(+)
diff --git
Add required fixed-regulator for VBUS supply for USB 3.0
controller phy.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
arch/arm/boot/dts/exynos5250-snow.dts | 22 ++
1 file changed, 22 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5250-snow.dts
Add device tree node for new usbdrd-phy driver, which
is based on generic phy framework.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Reviewed-by: Tomasz Figa t.f...@samsung.com
---
arch/arm/boot/dts/exynos5250.dtsi |9 +
1 file changed, 9 insertions(+)
diff --git
Add device tree nodes for DWC3 controller present on
Exynos 5420 SoC, to enable support for USB 3.0.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Reviewed-by: Tomasz Figa t.f...@samsung.com
---
arch/arm/boot/dts/exynos5420.dtsi | 34 ++
1 file changed,
Removing the dt node for older usb3 phy driver from Exynos5250
device tree and updating the dt node for DWC3 controller to
use new phy driver based on generic phy framework.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Reviewed-by: Tomasz Figa t.f...@samsung.com
---
Add device tree nodes for USB 3.0 PHY present alongwith
USB 3.0 controller Exynos 5420 SoC. This phy driver is
based on generic phy framework.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Reviewed-by: Tomasz Figa t.f...@samsung.com
---
arch/arm/boot/dts/exynos5420.dtsi | 20
From: Vivek gautam gautam.vi...@samsung.com
Based on 'for-next' branch of Kgene's linux-samsung tree;
along with dts patches for USB 2.0 phy[1], and Exynos5800 [2].
Also based on the latest USB 3.0 DRD phy driver patches posted [3].
Changes from v5:
- Added node reference names for new boards.
On Wed, May 14, 2014 at 6:41 PM, Heiko Stübner he...@sntech.de wrote:
Am Mittwoch, 14. Mai 2014, 18:35:29 schrieb Viresh Kumar:
On 14 May 2014 18:20, Arnd Bergmann a...@arndb.de wrote:
Could we please come up with a way to probe this from DT in the
cpufreq-cpu0 driver itself, so we don't
On Wed, May 14, 2014 at 02:04:51PM +0100, Arnd Bergmann wrote:
On Wednesday 14 May 2014 13:33:55 Chander Kashyap wrote:
diff --git a/drivers/cpuidle/cpuidle-big_little.c
b/drivers/cpuidle/cpuidle-big_little.c
index 4cd02bd..344d79fa 100644
--- a/drivers/cpuidle/cpuidle-big_little.c
On Wed, May 14, 2014 at 6:20 PM, Arnd Bergmann a...@arndb.de wrote:
On Wednesday 14 May 2014 06:41:15 Thomas Abraham wrote:
From: Thomas Abraham thomas...@samsung.com
Remove the platform device instantiation for Exynos specific cpufreq
driver and add the platform device for cpufreq-cpu0
On 14/05/14 15:03, Thomas Abraham wrote:
On Wed, May 14, 2014 at 6:41 PM, Heiko Stübner he...@sntech.de wrote:
Am Mittwoch, 14. Mai 2014, 18:35:29 schrieb Viresh Kumar:
On 14 May 2014 18:20, Arnd Bergmann a...@arndb.de wrote:
Could we please come up with a way to probe this from DT in the
Hi Pawel, Hans,
I think we talked some time ago on IRC about this patch.
If I remember correctly, the conclusion was that it would be better to use
a specific pixel formats for this kind of out codec output.
Akin to:
V4L2_PIX_FMT_H264 'H264' H264 video elementary stream
On Wed, May 14, 2014 at 7:20 PM, Viresh Kumar viresh.ku...@linaro.org wrote:
On 14 May 2014 19:13, Thomas Abraham ta.oma...@gmail.com wrote:
Okay, so you are suggesting that Kconfig entry used to select
cpufreq-cpu0 should also enable CPU_FREQ_BOOST_SW config as well.
I never said that...
On 14 May 2014 19:48, Thomas Abraham ta.oma...@gmail.com wrote:
Okay, I get the point about #ifdef in cpufreq-cpu0. What about your
earlier comment about the new Kconfig entry (Get rid of this.. just
not required.)? The new Kconfig entry would be needed in that case.
The only place you used
On 05/14/2014 01:24 AM, Viresh Kumar wrote:
On 14 May 2014 11:39, Lukasz Majewski l.majew...@samsung.com wrote:
I agree with Nishanth here, that point 1 (as described by Viresh at
[*]) is a more scalable approach.
The only reason why I wanted all that to be done at OPP level was to
ensure
On Wednesday 14 May 2014 08:45:23 Rob Herring wrote:
On Wed, May 14, 2014 at 8:18 AM, Arnd Bergmann a...@arndb.de wrote:
On Wednesday 14 May 2014 18:44:46 Viresh Kumar wrote:
On 14 May 2014 18:41, Heiko Stübner he...@sntech.de wrote:
Am Mittwoch, 14. Mai 2014, 18:35:29 schrieb Viresh
On Tue, May 13, 2014 at 10:19:33PM +0530, Ajay kumar wrote:
On Tue, May 13, 2014 at 1:35 PM, Thierry Reding
thierry.red...@gmail.com wrote:
On Fri, May 09, 2014 at 08:23:01PM +0530, Ajay Kumar wrote:
implement basic panel controls as a drm_bridge so that
the existing bridges can make use
On 14/05/14 02:03, Thomas Abraham wrote:
From: Thomas Abraham thomas...@samsung.com
Add a new optional boost-frequency binding for specifying the frequencies
usable in boost mode.
Cc: Nishanth Menon n...@ti.com
Cc: Lukasz Majewski l.majew...@samsung.com
Cc: Rob Herring robh...@kernel.org
Cc:
1 - 100 of 145 matches
Mail list logo
