Add dev_pm_opp_get_turbo_mode_setting() helper for getting turbo
mode setting for a given opp.
Cc: Tomasz Figa tomasz.f...@gmail.com
Cc: Michael Turquette mturque...@baylibre.com
Cc: Javier Martinez Canillas jav...@dowhile0.org
Cc: Thomas Abraham thomas...@samsung.com
Cc: Viresh Kumar
Turbo modes should be marked with CPUFREQ_BOOST_FREQ flag in
the frequency table entry.
Cc: Tomasz Figa tomasz.f...@gmail.com
Cc: Michael Turquette mturque...@baylibre.com
Cc: Javier Martinez Canillas jav...@dowhile0.org
Cc: Thomas Abraham thomas...@samsung.com
Cc: Viresh Kumar
Hi,
This patch series removes the use of Exynos4x12 specific support
from cpufreq-exynos driver and enables the use of cpufreq-dt driver
for this platform.
In order to preserve support for Exynos4x12 'boost' mode cpufreq-dt
driver is made aware of cpufreq 'boost' mode infrastructure. Once
it is
The new CPU clock type allows the use of generic CPUfreq driver.
Switch Exynos4x12 to using generic cpufreq driver.
This patch also takes care of making ARM_EXYNOS_CPU_FREQ_BOOST_SW
config option depend on cpufreq-dt driver instead of exynos-cpufreq
one and fixes the minor issue present with the
For Exynos4x12 platforms, add CPU operating points (using
opp-v2 bindings) and CPU regulator supply properties for
migrating from Exynos specific cpufreq driver to using
generic cpufreq driver.
Based on the earlier work by Thomas Abraham.
Cc: Kukjin Kim kgene@samsung.com
Cc: Doug Anderson
Exynos4x12 based platforms have switched over to use generic
cpufreq driver for cpufreq functionality. So the Exynos
specific cpufreq support for these platforms can be removed.
Also once Exynos4x12 based platforms support have been removed
the shared exynos-cpufreq driver is no longer needed
Add turbo modes (from opp-v2 bindings) support using
existing cpufreq 'boost' mode infrastructure:
- add boost_supported field to struct cpufreq_dt_platform_data
- set dt_cpufreq_driver.boost_supported in dt_cpufreq_probe()
Cc: Tomasz Figa tomasz.f...@gmail.com
Cc: Michael Turquette
With the addition of the new Samsung specific cpu-clock type, the
arm clock can be represented as a cpu-clock type. Add the CPU clock
configuration data and instantiate the CPU clock type for Exynos4x12.
Based on the earlier work by Thomas Abraham.
Cc: Tomasz Figa tomasz.f...@gmail.com
Cc:
On 09/07/15 02:23, Krzysztof Kozlowski wrote:
drivers/clk/samsung/clk-exynos4.c | 2 ++
1 file changed, 2 insertions(+)
Patch looks good to me.
Reviewed-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Hi Tomasz and Sylwester,
Any comments on this version of
Hi,
The i2c drivers also do not have to set 'owner' field because
i2c_register_driver() will do it instead.
'owner' is removed from i2c drivers, which I was able to compile
with allyesconfig (arm, arm64, i386, x86_64, ppc64).
Only compile-tested.
The coccinelle script which generated the patch
i2c_driver does not need to set an owner because i2c_register_driver()
will set it.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
The coccinelle script which generated the patch was sent here:
http://www.spinics.net/lists/kernel/msg2029903.html
---
drivers/mfd/88pm800.c
platform_driver does not need to set an owner because
platform_driver_register() will set it.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
The coccinelle script which generated the patch was sent here:
http://www.spinics.net/lists/kernel/msg2029903.html
---
Hi,
The i2c drivers also do not have to set 'owner' field because
i2c_register_driver() will do it instead.
'owner' is removed from i2c drivers, which I was able to compile
with allyesconfig (arm, arm64, i386, x86_64, ppc64).
Only compile-tested.
The coccinelle script which generated the patch
On 07/10/2015 07:56 AM, Gustavo Padovan wrote:
2015-07-09 Joonyoung Shim jy0922.s...@samsung.com:
+Cc Andrzej,
On 07/07/2015 02:41 AM, Daniel Vetter wrote:
On Mon, Jul 06, 2015 at 11:20:13AM -0300, Gustavo Padovan wrote:
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
struct
On 10.07.2015 00:43, Bartlomiej Zolnierkiewicz wrote:
Add dev_pm_opp_get_turbo_mode_setting() helper for getting turbo
mode setting for a given opp.
Cc: Tomasz Figa tomasz.f...@gmail.com
Cc: Michael Turquette mturque...@baylibre.com
Cc: Javier Martinez Canillas jav...@dowhile0.org
Cc:
On 10.07.2015 00:43, Bartlomiej Zolnierkiewicz wrote:
Turbo modes should be marked with CPUFREQ_BOOST_FREQ flag in
the frequency table entry.
Cc: Tomasz Figa tomasz.f...@gmail.com
Cc: Michael Turquette mturque...@baylibre.com
Cc: Javier Martinez Canillas jav...@dowhile0.org
Cc: Thomas
+Cc Andrzej,
On 07/07/2015 02:41 AM, Daniel Vetter wrote:
On Mon, Jul 06, 2015 at 11:20:13AM -0300, Gustavo Padovan wrote:
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
struct drm_crtc already stores the enabled state of the crtc
thus we don't need to replicate enabled in
Hello,
Hans, did you have a chance to look at these patches? I have tested them
with the vivid driver but it would be good if you could run them through
your standard testing procedure as well. Andrew has updated the patches in
his tree but some ack from you would be welcome...
On 07/09/2015 01:48 PM, Jan Kara wrote:
Hello,
Hans, did you have a chance to look at these patches? I have tested them
with the vivid driver but it would be good if you could run them through
your standard testing procedure as well. Andrew has updated the patches in
his tree but some
On 01-07-15, 15:10, Bartlomiej Zolnierkiewicz wrote:
This patch series removes the use of Exynos5250 specific support
from cpufreq-exynos driver and enables the use of cpufreq-dt driver
for this platform.
This patch series has been tested on Exynos5250 based Arndale board.
Changes since
2015-07-09 Joonyoung Shim jy0922.s...@samsung.com:
+Cc Andrzej,
On 07/07/2015 02:41 AM, Daniel Vetter wrote:
On Mon, Jul 06, 2015 at 11:20:13AM -0300, Gustavo Padovan wrote:
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
struct drm_crtc already stores the enabled state of the
Most of the code is called by drm core framework, so it is already synchronized.
The only async function is irq routine which only calls drm framework so it
does not need to be synchronized.
Signed-off-by: Andrzej Hajda a.ha...@samsung.com
---
drivers/gpu/drm/exynos/exynos_hdmi.c | 27
The patch removes intermediate struct for HDMIv14 register configuration,
instead registry values are calculated on the fly.
Signed-off-by: Andrzej Hajda a.ha...@samsung.com
---
drivers/gpu/drm/exynos/exynos_hdmi.c | 427 +--
1 file changed, 109 insertions(+), 318
s5p_hdmi_platform_data were used before device tree introduction.
As HDMI driver is DT only we can drop this struct completely.
Signed-off-by: Andrzej Hajda a.ha...@samsung.com
---
drivers/gpu/drm/exynos/exynos_hdmi.c | 36 +---
1 file changed, 5 insertions(+), 31
The patch removes intermediate struct for HDMIv13 register configuration,
instead registry values are calculated on the fly.
Signed-off-by: Andrzej Hajda a.ha...@samsung.com
---
drivers/gpu/drm/exynos/exynos_hdmi.c | 280 +--
1 file changed, 101 insertions(+), 179
The patch removes redundant fields from hdmi_conf_regs. Their values
can be calculated from current_mode. This patch is the first step to remove
whole hdmi_conf_regs structure.
Signed-off-by: Andrzej Hajda a.ha...@samsung.com
---
drivers/gpu/drm/exynos/exynos_hdmi.c | 68
Hi Inki, Joonyoung,
These patches removes obsolete and old structures, to simplify further
development. They should not change behavior of the driver.
The patchset is based on exynos-drm-next plus my HDMI related fixes [1].
The patchset was tested on Universal and Odroid U3.
[1]:
The patch replaces duplicated driver data fields in private context with
pointer to driver data. It also simplifies driver data lookup code.
Signed-off-by: Andrzej Hajda a.ha...@samsung.com
---
drivers/gpu/drm/exynos/exynos_hdmi.c | 49 +++-
1 file changed, 20
GPIO is tested only in hdmi_detect, so there is no reason to set it in
other places and to preserve its value in context.
Signed-off-by: Andrzej Hajda a.ha...@samsung.com
---
drivers/gpu/drm/exynos/exynos_hdmi.c | 13 +++--
1 file changed, 3 insertions(+), 10 deletions(-)
diff --git
Hello Bartlomiej,
On Thu, Jul 9, 2015 at 8:43 AM, Bartlomiej Zolnierkiewicz
b.zolnier...@samsung.com wrote:
Hi,
This patch series removes the use of Exynos4x12 specific support
from cpufreq-exynos driver and enables the use of cpufreq-dt driver
for this platform.
In order to preserve
30 matches
Mail list logo
