On śro, 2014-10-08 at 15:44 +0200, Javier Martinez Canillas wrote:
Regulators can run on different operating modes (opmodes). This allows
systems to choose the most efficient opmode for each regulator. The
regulator core defines a set of generic modes so each system can define
the opmode in
On Thu, Oct 09, 2014 at 02:43:02PM +0900, Alexandre Courbot wrote:
But there might be another issue, which is that calls to
drm_vblank_get() will return -EINVAL if invoked between drm_blank_off
and drm_blank_on. Is this really the desired behavior? Can it at least
happen? If so, how are
Hello Abhilash,
On Thu, Oct 9, 2014 at 4:37 AM, Abhilash Kesavan
kesavan.abhil...@gmail.com wrote:
Hi Kevin,
On Thu, Oct 9, 2014 at 4:49 AM, Kevin Hilman khil...@kernel.org wrote:
Vikas Sajjan vikas.saj...@samsung.com writes:
[...]
Tested on Kukjin Kim's tree, for-next branch +
1]
On Thu, Oct 09, 2014 at 09:52:58AM +0100, Russell King - ARM Linux wrote:
On Thu, Oct 09, 2014 at 02:43:02PM +0900, Alexandre Courbot wrote:
But there might be another issue, which is that calls to
drm_vblank_get() will return -EINVAL if invoked between drm_blank_off
and drm_blank_on.
On Thu, Oct 9, 2014 at 7:08 PM, Thierry Reding tred...@nvidia.com wrote:
On Thu, Oct 09, 2014 at 02:43:02PM +0900, Alexandre Courbot wrote:
On 10/02/2014 08:52 PM, Andrzej Hajda wrote:
Hi,
+CC possible victims
On 10/02/2014 12:52 PM, Inki Dae wrote:
On 2014년 10월 02일 17:58, Joonyoung Shim
Ajay,
On Thu, Oct 9, 2014 at 3:48 PM, Ajay kumar ajayn...@gmail.com wrote:
Hi,
On Mon, Sep 15, 2014 at 6:43 PM, Vivek Gautam gautam.vi...@samsung.com
wrote:
These patches are based on 'for-next' branch of kgene's linux-samsung tree.
Refactoring the exynos-dp-video phy to use
On Thu, Oct 9, 2014 at 3:56 PM, Vivek Gautam gautam.vi...@samsung.com wrote:
Ajay,
On Thu, Oct 9, 2014 at 3:48 PM, Ajay kumar ajayn...@gmail.com wrote:
Hi,
On Mon, Sep 15, 2014 at 6:43 PM, Vivek Gautam gautam.vi...@samsung.com
wrote:
These patches are based on 'for-next' branch of
The multi_v7 config already enables MFD and regulators drivers for
Samsung's S2MPS11/S2MPS14 and S5M8767. Enable also drivers for the rest
of these PMICs features: clock and RTC.
These PMICs are used on Arndale (Exynos 5250 and 5420) and Origen
(Exynos 4412) evaluation boards, Google Spring,
Enable all Maxim 14577 drivers and Maxim 17040 fuel gauge driver to
support the Maxim 77836 PMIC present on Samsung Rinato board (Gear 2).
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
arch/arm/configs/multi_v7_defconfig | 6 ++
1 file changed, 6 insertions(+)
diff --git
Enable all Maxim 14577 drivers and Maxim 17040 fuel gauge driver to
support the Maxim 77836 PMIC present on Samsung Rinato board (Gear 2).
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
arch/arm/configs/exynos_defconfig | 6 ++
1 file changed, 6 insertions(+)
diff --git
On Thursday 09 October 2014 10:46:59 Ulf Hansson wrote:
On 8 October 2014 20:28, Arnd Bergmann a...@arndb.de wrote:
On Wednesday 08 October 2014 08:29:16 Doug Anderson wrote:
On Wed, Oct 8, 2014 at 8:20 AM, Arnd Bergmann a...@arndb.de wrote:
Why does it cause a regression though? Does
Changes since v4:
- Rebased over Tomasz Figa's pinctrl clean-up patches[1]
Changes since v3:
- Changed variable name from exynos_wkup_irq_chip to irq_chip
- Added acked-by tag from Tomasz Figa
Changes since v2:
- Added a .irq_chip field to the samsung_pin_bank
The function exynos_irq_demux_eint16_31 uses pre-defined offsets for external
interrupt pending status and mask registers. So this function is not extensible
for Exynos7 SoC which has these registers at different offsets. Generalize
the exynos_irq_demux_eint16_31 function by using the pending/mask
Adding a irq_chip field to the samsung_pin_bank struct helps in
consolidating the irq domain callbacks for external gpio and wakeup
interrupt controllers. The exynos_wkup_irqd_ops and exynos_gpio_irqd_ops
have now been merged into a single exynos_eint_irqd_ops.
Signed-off-by: Abhilash Kesavan
Exynos7 uses different offsets for wakeup interrupt configuration registers.
So a new irq_chip instance for Exynos7 wakeup interrupts is added. The irq_chip
selection is now based on the wakeup interrupt controller compatible string.
Signed-off-by: Abhilash Kesavan a.kesa...@samsung.com
From: Naveen Krishna Ch naveenkrishna...@gmail.com
Add initial pin configuration nodes for EXYNOS7.
Signed-off-by: Naveen Krishna Ch naveenkrishna...@gmail.com
Signed-off-by: Abhilash Kesavan a.kesa...@samsung.com
Reviewed-by: Thomas Abraham thomas...@samsung.com
Tested-by: Thomas Abraham
From: Naveen Krishna Ch naveenkrishna...@gmail.com
This patch adds initial driver data for Exynos7 pinctrl support.
Signed-off-by: Naveen Krishna Ch naveenkrishna...@gmail.com
Signed-off-by: Abhilash Kesavan a.kesa...@samsung.com
Reviewed-by: Thomas Abraham thomas...@samsung.com
Tested-by:
From: Naveen Krishna Ch naveenkrishna...@gmail.com
Enable pinctrl support for exynos7 SoCs.
Signed-off-by: Naveen Krishna Ch naveenkrishna...@gmail.com
Signed-off-by: Abhilash Kesavan a.kesa...@samsung.com
Reviewed-by: Thomas Abraham thomas...@samsung.com
Tested-by: Thomas Abraham
Hi,
On Thursday, October 02, 2014 03:35:18 PM Bartlomiej Zolnierkiewicz wrote:
Hi,
On Wednesday, October 01, 2014 08:31:47 PM Arnd Bergmann wrote:
On Wednesday 01 October 2014 18:49:20 Bartlomiej Zolnierkiewicz wrote:
On Wednesday, October 01, 2014 06:01:29 PM Arnd Bergmann wrote:
Hello Mark,
On 10/08/2014 09:51 PM, Mark Brown wrote:
On Wed, Oct 08, 2014 at 06:25:00PM +0200, Javier Martinez Canillas
What this series tried to solve is when you have to set a opmode on
boot to change how the physical suspend is managed by the PMIC.
Think about the consequences of what's
Hello Krzysztof,
Thanks a lot for your feedback.
On 10/09/2014 10:45 AM, Krzysztof Kozlowski wrote:
On śro, 2014-10-08 at 15:44 +0200, Javier Martinez Canillas wrote:
--- a/Documentation/devicetree/bindings/regulator/regulator.txt
+++
Hello Mark,
On 10/09/2014 12:27 PM, Mark Rutland wrote:
Well, is not fairly obvious to me. One can also say the opposite, why the
kernel is documenting a DT binding that is not (currently) implemented?
Checkpatch will complain regarding undocumented bindings, so from a
pragmatic point of
1. Introduction
Following patches aim to clean up the current implementation of the thermal
framework on Exynos devices.
The main goal was to use a generic code for reading thermal configuration
(of-thermal.c). Due to that redundant exynos_thermal_common.[h|c] files
were removed.
Around 400
This patch extends the of-thermal.c to provide information about number of
available non critical (i.e. non HW) trip points in the system.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
drivers/thermal/of-thermal.c | 12
drivers/thermal/thermal_core.h | 5 +
2
The thermal IP block (Thermal Management Unit) called TMU has been enabled
in this device.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
arch/arm/boot/dts/exynos4210-trats.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/exynos4210-trats.dts
This patch is a preparatory patch for being able to read Exynos thermal
configuration from the device tree.
The DTC is not able to interpret enums properly and hence it is necessary
to #define those values explicitly.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
drivers/thermal/samsung/exynos_tmu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/thermal/samsung/exynos_tmu.c
b/drivers/thermal/samsung/exynos_tmu.c
index 9e7f720..fa29b95 100644
---
Before this change it was only possible to set get_temp() and get_trend()
methods to be used in the common code handling passing parameters via
device tree to cpu-thermal CPU thermal zone device.
Now it is possible to also set emulated value of temperature for debug
purposes.
Signed-off-by:
This patch extends the of-thermal.c to provide check if trip point is
enabled.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
drivers/thermal/of-thermal.c | 9 +
drivers/thermal/thermal_core.h | 5 +
2 files changed, 14 insertions(+)
diff --git
This patch extends the of-thermal.c to provide information about number of
available trip points.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
drivers/thermal/of-thermal.c | 6 ++
drivers/thermal/thermal_core.h | 5 +
2 files changed, 11 insertions(+)
diff --git
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
arch/arm/boot/dts/exynos4412-odroid-common.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/exynos4412-odroid-common.dtsi
b/arch/arm/boot/dts/exynos4412-odroid-common.dtsi
index adadaf9..5364f1a 100644
---
This commit adds necessary bindings for enabling TMU IP block on the
Exynos4412 Odroid U3 device.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
arch/arm/boot/dts/exynos4412-odroid-common.dtsi | 5 +
arch/arm/boot/dts/exynos4x12.dtsi | 10 ++
2 files
Exynos 4 and 5 family of SoCs uses almost identical TMU sensor to measure the
on chip temperature. Hence it is possible to group TMU configuration parameters
in one dts include file.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
arch/arm/boot/dts/exynos4412-tmu-sensor-conf.dtsi | 24
Trip points corresponding to the one defined in the exynos_tmu_data.c
for Exynos4 have been included.
This thermal-zones attribute is afterwards reused for Exynos4210, Exynos4412
and Exynos5250.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
arch/arm/boot/dts/exynos4-cpu-thermal.dtsi
Presented patch aims to move data necessary for correct CPU cooling device
configuration from exynos_tmu_data.c to device tree.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
arch/arm/boot/dts/exynos4210-trats.dts | 15 +++
arch/arm/boot/dts/exynos4210.dtsi
Up till now exynos_tmu_data.c was used for storing CPU cooling configuration
data. Now the Exynos thermal core code uses device tree to get this data.
For this purpose generic thermal code for configuring CPU cooling was
used.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
This patch brings support for providing configuration via device tree.
Previously, data hardcoded in the exynos_tmu_data.c file was used, which is
not scalable and error prone.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
drivers/thermal/samsung/Makefile | 2 -
Since both SoCs have the same TMU IP block embedded on them, it is
not necessary to maintain separate compatible entry.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
drivers/thermal/samsung/exynos_tmu.c | 3 ---
1 file changed, 3 deletions(-)
diff --git
After defining all necessary Exynos data in the device tree
those files can be removed.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
drivers/thermal/samsung/exynos_thermal_common.c | 448
drivers/thermal/samsung/exynos_thermal_common.h | 106 --
2 files
Data already present in the exynos_tmu_data.c file has been moved to the
appropriate device tree files.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
drivers/thermal/samsung/exynos_tmu_data.c | 228 --
1 file changed, 228 deletions(-)
delete mode 100644
This commit provides information about Exynos5440 device configuration.
Previously this information was available in exynos_tmu_data.c file.
Now it is available in the device tree.
Such approach allows reusing some common code for thermal.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
Presented device tree bindings provide data already hardcoded in the
exynos_tmu_data.c file.
After this commit, it should be possible to reuse common thermal core
framework in Exynos SoCs.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
arch/arm/boot/dts/exynos4.dtsi| 5 +
This code groups in one place default settings of trip points. It is used
in SoCs with multiple instances of TMU sensor.
Separate device tree file prevents from multiple copying of the same data.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
On Thu, Oct 09, 2014 at 04:27:37PM +0200, Javier Martinez Canillas wrote:
I see, I thought that an operating mode could be anything that alter the
regulator behavior either during runtime or when the system is suspended.
But under your definition, it is true that most max77802 regulators have
Commit 43eeaa42e03a (ARM: exynos_defconfig: savedefconfig) removed a
set of Kconfig symbols. For most of them there were no functional change
since are selected by other Kconfig options or were deprecated but some
options are not explicitly selected so they should not had been removed.
The
On Thu, Oct 09, 2014 at 05:04:35PM +0200, Javier Martinez Canillas wrote:
Agree, Mark also pointed out that there is a difference between changing
how the regulator will behave on runtime vs changing how the regulator
will behave during system suspend. AFAIU from his explanation, the modes
Hello Mark,
Thanks for your feedback.
On 10/09/2014 07:48 PM, Mark Brown wrote:
On Thu, Oct 09, 2014 at 04:27:37PM +0200, Javier Martinez Canillas wrote:
I see, I thought that an operating mode could be anything that alter the
regulator behavior either during runtime or when the system is
Javier Martinez Canillas jav...@dowhile0.org writes:
Hello Abhilash,
On Thu, Oct 9, 2014 at 4:37 AM, Abhilash Kesavan
kesavan.abhil...@gmail.com wrote:
Hi Kevin,
On Thu, Oct 9, 2014 at 4:49 AM, Kevin Hilman khil...@kernel.org wrote:
Vikas Sajjan vikas.saj...@samsung.com writes:
[...]
On 10/09/2014 09:01 PM, Mark Brown wrote:
On Thu, Oct 09, 2014 at 05:04:35PM +0200, Javier Martinez Canillas wrote:
Agree, Mark also pointed out that there is a difference between changing
how the regulator will behave on runtime vs changing how the regulator
will behave during system
Hi Abhilash,
Abhilash Kesavan a.kesa...@samsung.com writes:
I had noticed a similar issue where only 6 cores would come up during
development on 5420. This was because there was a check in our u-boot
secondary boot-up path which would put a core into WFI if a flag was
not present and hence
Hello Kevin,
On Thu, Oct 9, 2014 at 11:50 PM, Kevin Hilman khil...@kernel.org wrote:
On Peach boards, the S3C source clock is the max77802 32kHZ AP clock
so I fixed that with commit 8bd43b6 (ARM: dts: Add rtc_src clk for
s3c-rtc on exynos Peach boards) but didn't send a patch to enable the
Kevin Hilman khil...@kernel.org writes:
[...]
Trying $SUBJECT series on top of kukjin's for-next is working fine, but
I'm still not able to make it work on linux-next, with or without the
CLK_IGNORE_UNUSED patch.
Nevermind, turns out I didn't apply the CLK_IGNORE_UNUSED PATCH. If I
actually
Javier Martinez Canillas javier.marti...@collabora.co.uk writes:
Commit 43eeaa42e03a (ARM: exynos_defconfig: savedefconfig) removed a
set of Kconfig symbols. For most of them there were no functional change
since are selected by other Kconfig options or were deprecated but some
options are
On 10/10/2014 01:38 AM, Lukasz Majewski wrote:
Since both SoCs have the same TMU IP block embedded on them, it is
not necessary to maintain separate compatible entry.
Signed-off-by: Lukasz Majewski l.majew...@samsung.com
---
drivers/thermal/samsung/exynos_tmu.c | 3 ---
1 file changed, 3
[1].
And one more..., if I try enabling CPUidle[1] with exynos_defconfig, S2R
causes a reboot (seems to be on resume.)
I tested S2R on my Peach-Pi (Exynos5800) on linux-next-20141009. My tree has:
a57db95 TEMP: Use CLK_IGNORE_UNUSED for aclk200_disp1
18158ac ARM: EXYNOS: Use MCPM call-backs
55 matches
Mail list logo
