Hi Andreas,
On 7/27/14, Andreas Färber afaer...@suse.de wrote:
Hi Ajay,
Am 25.07.2014 21:22, schrieb Ajay Kumar:
This series is based on exynos-drm-next branch of Inki Dae's tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git
I have tested this after adding few DT
On Tue, 15 Jul 2014, Amit Daniel Kachhap wrote:
This is a cleanup patch and moves min/step voltages in a common samsung
header file so that they can be used by other s2mpxxx PMIC drivers. Only
few required macros are added currently and others can be added if needed.
Cc: Sangbeom Kim
On 07/09/2014 07:17 PM, Bartlomiej Zolnierkiewicz wrote:
Hi,
This patch series adds support for AFTR idle mode on boards with
secure firmware enabled and allows EXYNOS cpuidle driver usage on
Exynos4x12 SoCs.
It has been tested on Trats2 board (using Exynos4412 SoC with secure
firmware
The hdmiphy can be apb and hdmiphy_port can be null. So before
accessing hdmiphy_port, it should be checked.
Signed-off-by: Seung-Woo Kim sw0312@samsung.com
---
drivers/gpu/drm/exynos/exynos_hdmi.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git
Hey Inki,
On Mon, 2014-07-21 at 08:50 +0200, Sjoerd Simons wrote:
Hey Inki,
On Mon, 2014-07-21 at 12:02 +0900, Inki Dae wrote:
On 2014년 07월 19일 05:36, Sjoerd Simons wrote:
The exynos DRM module currently is not automatically loaded when build as
a
module. This is due to the simple
Hello Mike,
On 07/26/2014 12:31 AM, Mike Turquette wrote:
Quoting Javier Martinez Canillas (2014-07-14 04:35:56)
This series are based on drivers added by Simon Glass to the Chrome OS
kernel and adds support for the Maxim 77802 Power Management IC, their
regulators, clocks, RTC and i2c
On 07/28/2014 05:35 AM, Hartmut Knaack wrote:
Chanwoo Choi schrieb:
This patch add support for s3c2410/s3c2416/s3c2440/s3c2443 ADC. The s3c24xx
is alomost same as ADCv1. But, There are a little difference as following:
- ADCMUX register address to select channel
- ADCDAT mask (10bit or 12bit
On 07/22/2014 09:59 PM, Arnd Bergmann wrote:
On Tuesday 22 July 2014 11:11:14 Chanwoo Choi wrote:
This patch add support for s3c2410/s3c2416/s3c2440/s3c2443 ADC. The s3c24xx
is alomost same as ADCv1. But, There are a little difference as following:
- ADCMUX register address to select channel
On 07/28/2014 03:49 AM, Hartmut Knaack wrote:
Chanwoo Choi schrieb:
From: Arnd Bergmann a...@arndb.de
The ADC in s3c64xx is almost the same as exynosv1, but
has a different 'select' method. Adding this here will be
helpful to move over the existing s3c64xx platform from the
legacy
On 07/22/2014 05:39 PM, Arnd Bergmann wrote:
On Tuesday 22 July 2014 11:11:14 Chanwoo Choi wrote:
This patch add support for s3c2410/s3c2416/s3c2440/s3c2443 ADC. The s3c24xx
is alomost same as ADCv1. But, There are a little difference as following:
- ADCMUX register address to select channel
On 07/22/2014 07:44 PM, Heiko Stübner wrote:
Am Dienstag, 22. Juli 2014, 10:39:38 schrieb Arnd Bergmann:
On Tuesday 22 July 2014 11:11:14 Chanwoo Choi wrote:
This patch add support for s3c2410/s3c2416/s3c2440/s3c2443 ADC. The
s3c24xx
is alomost same as ADCv1. But, There are a little
Signed-off-by: Andreas Färber afaer...@suse.de
---
arch/arm/boot/dts/exynos5410-odroidxu.dts | 25 +
1 file changed, 25 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5410-odroidxu.dts
b/arch/arm/boot/dts/exynos5410-odroidxu.dts
index b67112bf062a..f6e7555feeff
Addd PMU DT node for exynos5260 SoC.
Signed-off-by: Vikas Sajjan vikas.saj...@samsung.com
---
.../devicetree/bindings/arm/samsung/pmu.txt|1 +
arch/arm/boot/dts/exynos5260.dtsi |5 +
2 files changed, 6 insertions(+)
diff --git
From: Hakjoo Kim ruppi@hardkernel.com
Add the required pin configuration support to Exynos5410 using pinctrl
interface.
Cc: Hakjoo Kim ruppi@hardkernel.com
[AF: Rebased]
---
arch/arm/boot/dts/exynos5410-pinctrl.dtsi | 408 ++
arch/arm/boot/dts/exynos5410.dtsi
Exynos initialisation code now relies on obtaining the PMU address via
DT node, so add the exynos5260 PMU compatible string to DT match table.
Signed-off-by: Vikas Sajjan vikas.saj...@samsung.com
---
arch/arm/mach-exynos/exynos.c |1 +
1 file changed, 1 insertion(+)
diff --git
Hello,
This series adds a dedicated ODROID-XU device tree and enhances it with
LED configuration, to match the downstream 3.14 based behavior.
It had turned out less trivial than I initially thought as the whole
pinctrl stuff is still missing. I thus cherry-pick two downstream commits.
Derived from exynos5410-smdk5410.dts.
Signed-off-by: Andreas Färber afaer...@suse.de
---
arch/arm/boot/dts/Makefile| 1 +
arch/arm/boot/dts/exynos5410-odroidxu.dts | 86 +++
2 files changed, 87 insertions(+)
create mode 100644
rebased on kgene tree for-next branch
https://git.kernel.org/cgit/linux/kernel/git/kgene/linux-samsung.git/log/?h=for-next
Vikas Sajjan (2):
ARM: EXYNOS: Add PMU DT node for exynos5260 SoC
ARM: EXYNOS: Add exynos5260 PMU compatible string to DT match table
From: Derek Basehore dbaseh...@chromium.org
Since the i2c bus can get wedged on the EC sometimes, set the number of retries
to 3. Since we un-wedge the bus immediately after the wedge happens, this is the
correct fix since only one transfer will fail.
Signed-off-by: Derek Basehore
From: Andrew Bresticker abres...@chromium.org
When an EC command returns EC_RES_IN_PROGRESS, we need to query
the state of the EC until it indicates that it is no longer busy.
Do this in cros_ec_cmd_xfer() under the EC's mutex so that other
commands (e.g. keyboard, I2C passtru) aren't issued to
This is a second batch of cleanups patches for the mfd cros_ec
driver and its subdevices drivers. The first batch of cleanups
was posted by Doug Anderson [0] and have already been merged.
The patches were picked from the ChromeOS 3.8 kernel and after
these no cleanups patches for cros_ec are left,
From: Hakjoo Kim ruppi@hardkernel.com
Add Samsung EXYNOS5410 SoC specific data to enable pinctrl
support for all platforms based on EXYNOS5410.
Cc: Hakjoo Kim ruppi@hardkernel.com
[AF: Rebased onto Exynos5260]
---
.../bindings/pinctrl/samsung-pinctrl.txt | 1 +
From: Andrew Bresticker abres...@chromium.org
Now that there's a central cros_ec_cmd_xfer(), move the locking
out of the SPI and LPC drivers.
Signed-off-by: Andrew Bresticker abres...@chromium.org
Reviewed-by: Simon Glass s...@chromium.org
---
drivers/mfd/cros_ec.c | 10 +-
From: Andrew Bresticker abres...@chromium.org
Instead of having users of the ChromeOS EC call the interface-specific
cmd_xfer() callback directly, introduce a central cros_ec_cmd_xfer()
to use instead. This will allow us to put all the locking and retry
logic in one place instead of duplicating
From: Todd Broch tbr...@chromium.org
If the EC device tree node has sub-nodes, try to instantiate them as
MFD sub-devices. We can configure the EC features provided by the board.
Signed-off-by: Todd Broch tbr...@chromium.org
---
drivers/mfd/cros_ec.c | 40
The UART status properties are indented one level too deep, and we want
to derive a device tree for the ODROID-XU. Fix this before it propagates.
Signed-off-by: Andreas Färber afaer...@suse.de
---
arch/arm/boot/dts/exynos5410-smdk5410.dts | 6 +++---
1 file changed, 3 insertions(+), 3
From: Todd Broch tbr...@chromium.org
Previous algorithm was a bit conservative and complicating with
respect to identifying key ghosting. This CL uses the bitops hamming
weight function (hweight8) to count the number of matching rows for
colM colN. If that number is 1 ghosting is present.
rebased on kgene tree for-next branch
https://git.kernel.org/cgit/linux/kernel/git/kgene/linux-samsung.git/log/?h=for-next
Vikas Sajjan (2):
ARM: DTS: Add PMU DT node for exynos5260 SoC
ARM: EXYNOS: Add exynos5260 PMU compatible string to DT match table
Exynos initialisation code now relies on obtaining the PMU address via
DT, so add the exynos5260 PMU compatible string to DT match table.
Signed-off-by: Vikas Sajjan vikas.saj...@samsung.com
---
arch/arm/mach-exynos/exynos.c |1 +
1 file changed, 1 insertion(+)
diff --git
Adds PMU DT node for exynos5260 SoC.
Signed-off-by: Vikas Sajjan vikas.saj...@samsung.com
---
.../devicetree/bindings/arm/samsung/pmu.txt|1 +
arch/arm/boot/dts/exynos5260.dtsi |5 +
2 files changed, 6 insertions(+)
diff --git
This patch add support for s3c64xx/s3c24xx ADC. s3c64xx/s3c24xx is alomost same
as ADCv1. But, s3c64xx/s3c24xx has a little difference from ADCv1 as following:
- ADCMUX register address to select channel
- ADCDAT mask (10bit or 12bit ADC resolution according to SoC version)
- s3c24xx/s3c64xx has
This patch remove un-necessary white-sapce to code clean.
Signed-off-by: Chanwoo Choi cw00.c...@samsung.com
---
Documentation/devicetree/bindings/arm/samsung/exynos-adc.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Arnd Bergmann a...@arndb.de
The ADC in s3c64xx is almost the same as exynosv1, but
has a different 'select' method. Adding this here will be
helpful to move over the existing s3c64xx platform from the
legacy plat-samsung/adc driver to the new exynos-adc.
Signed-off-by: Arnd Bergmann
This patch add support for s3c2410/s3c2416/s3c2440/s3c2443 ADC. The s3c24xx
is alomost same as ADCv1. But, There are a little difference as following:
- ADCMUX register address
- ADCDAT mask (10 bit or 12 bit ADC resolution according to SoC version)
- s3c24xx/s3c64xx has not included ADC_PHY
On 2014년 07월 28일 17:30, Sjoerd Simons wrote:
Hey Inki,
On Mon, 2014-07-21 at 08:50 +0200, Sjoerd Simons wrote:
Hey Inki,
On Mon, 2014-07-21 at 12:02 +0900, Inki Dae wrote:
On 2014년 07월 19일 05:36, Sjoerd Simons wrote:
The exynos DRM module currently is not automatically loaded when build
On Tue, Jun 17, 2014 at 07:27:16PM +0200, Bartlomiej Zolnierkiewicz wrote:
Hi,
This patch series contains various cleanups for EXYNOS thermal
driver. Overall it decreases driver's LOC by 12%. It is based
on next-20140617 kernel. It should not cause any functionality
changes.
Changes
Hey Inki,
On Mon, 2014-07-28 at 23:17 +0900, Inki Dae wrote:
On 2014년 07월 28일 17:30, Sjoerd Simons wrote:
Sorry for late,
I don't see why Exynos drm driver should be auto-loaded module. I think
all devices covered by Exynos drm framework are not hot-plugged. Maybe
there is my missing
Hi Eduardo,
Please reject this entire series as this is not re-based recently.
Actually two point trimming which this series seeks to remove is used
by exynos3250 and is in Rui's tree
Hi Vikas,
On Mon, Jul 28, 2014 at 6:07 PM, Vikas Sajjan vikas.saj...@samsung.com wrote:
Adds PMU DT node for exynos5260 SoC.
Signed-off-by: Vikas Sajjan vikas.saj...@samsung.com
---
.../devicetree/bindings/arm/samsung/pmu.txt|1 +
arch/arm/boot/dts/exynos5260.dtsi
Hi Vikas,
On Mon, Jul 28, 2014 at 6:08 PM, Vikas Sajjan vikas.saj...@samsung.com wrote:
Exynos initialisation code now relies on obtaining the PMU address via
DT, so add the exynos5260 PMU compatible string to DT match table.
Signed-off-by: Vikas Sajjan vikas.saj...@samsung.com
---
On 07/28/2014 04:00 AM, Inki Dae wrote:
This patch adds LPM transfer support for video or command data.
With this patch, Exynos MIPI DSI controller can transfer command or
video data with HS or LP mode in accordance with mode_flags set
by LCD Panel driver.
Changelog v2: Enable High Speed
On 07/28/2014 04:00 AM, Inki Dae wrote:
This patch adds below two flags for LPM transfer, and it attaches LPM flags
to a msg in accordance with master's mode_flags set by LCD Panel driver.
MIPI_DSI_MODE_CMD_LPM
- If this flag is set by Panel driver, MIPI-DSI controller will tranfer
command
On 7/26/2014 2:20 PM, Rob Herring wrote:
On Tue, Jul 15, 2014 at 12:03 PM, Laura Abbott lau...@codeaurora.org wrote:
Hi,
This is a resend of the series to fix the uboot bug exposed by the removal
of meminfo. I haven't gotten any acks though.
Is the bug with ATAGs that get converted to DT
Hi Vikas and Sachin,
Am 28.07.2014 17:26, schrieb Sachin Kamat:
On Mon, Jul 28, 2014 at 6:07 PM, Vikas Sajjan vikas.saj...@samsung.com
wrote:
Adds PMU DT node for exynos5260 SoC.
Signed-off-by: Vikas Sajjan vikas.saj...@samsung.com
---
.../devicetree/bindings/arm/samsung/pmu.txt|
On 07/29/14 05:29, Andreas Färber wrote:
Hi Vikas and Sachin,
Am 28.07.2014 17:26, schrieb Sachin Kamat:
On Mon, Jul 28, 2014 at 6:07 PM, Vikas Sajjanvikas.saj...@samsung.com wrote:
Adds PMU DT node for exynos5260 SoC.
Signed-off-by: Vikas Sajjanvikas.saj...@samsung.com
---
Hi Andrzej,
On 07/29/2014 01:09 AM, Andrzej Hajda wrote:
On 07/28/2014 04:00 AM, Inki Dae wrote:
This patch adds below two flags for LPM transfer, and it attaches LPM flags
to a msg in accordance with master's mode_flags set by LCD Panel driver.
MIPI_DSI_MODE_CMD_LPM
- If this flag is set by
This patch add missing pinctrl for uart0/1 for Exynos3250. The gpio pin (
uart0_data, uart0_fctl, uart1_data) is only used for UART IP.
Signed-off-by: Chanwoo Choi cw00.c...@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
arch/arm/boot/dts/exynos3250.dtsi | 4
1 file
This patch removes duplicat 'interrupt-parent' property for Exynos3250
because exynos3250.dtsi already defined 'interrupt-parent' property
as following:
In arch/arm/boot/dts/exynos3250.dtsi:
compatible = samsung,exynos3250;
interrupt-parent = gic;
Signed-off-by: Chanwoo Choi
This patchset add TMU (Thermal Management Unit) dt node and missing pinctrl
property of uart0/1. Also, this patchset remove duplcate 'interrupt-parent'
property for code clean.
Chanwoo Choi (3):
ARM: dts: Add TMU dt node to monitor the temperature for Exynos3250
ARM: dts: Remove duplicate
This patch add TMU (Thermal Management Unit) dt node to monitor the high
temperature for Exynos3250.
Signed-off-by: Chanwoo Choi cw00.c...@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
This patch has a dependency on following patch [1] which supporting the TMU
of Exynos3250:
On 2014년 07월 29일 01:09, Andrzej Hajda wrote:
On 07/28/2014 04:00 AM, Inki Dae wrote:
This patch adds below two flags for LPM transfer, and it attaches LPM flags
to a msg in accordance with master's mode_flags set by LCD Panel driver.
MIPI_DSI_MODE_CMD_LPM
- If this flag is set by Panel
On 2014년 07월 29일 00:50, Andrzej Hajda wrote:
On 07/28/2014 04:00 AM, Inki Dae wrote:
This patch adds LPM transfer support for video or command data.
With this patch, Exynos MIPI DSI controller can transfer command or
video data with HS or LP mode in accordance with mode_flags set
by LCD
The IRQB interrupt pin of MAX77686 PMIC is connected to GPX3[2] pin of
Exynos5250 on the Exynos5250 SMDK board. Specify this connection using
interrupts property for the max77686 pmic node.
Signed-off-by: Thomas Abraham thomas...@samsung.com
---
arch/arm/boot/dts/exynos5250-smdk5250.dts |2
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 Exynos4210,
Exynos5250 and Exynos5420.
Cc: Tomasz Figa t.f...@samsung.com
Signed-off-by: Thomas Abraham
The CPU clock provider supplies the clock to the CPU clock domain. The
composition and organization of the CPU clock provider could vary among
Exynos SoCs. A CPU clock provider can be composed of clock mux, dividers
and gates. This patch defines a new clock type for CPU clock provider and
adds
Changes since v7:
- Fixes suggested by Tomasz Figa.
This patch series removes the use of Exynos4210 and Exynos5250 specific cpufreq
drivers and enables the use of cpufreq-cpu0 driver for these platforms. This
series also enables cpufreq support for Exynos5420 using arm_big_little cpufreq
driver.
For Exynos 4210/5250/5420 based platforms, add CPU operating points and CPU
regulator supply properties for migrating from Exynos specific cpufreq driver
to using generic cpufreq drivers.
Cc: Kukjin Kim kgene@samsung.com
Signed-off-by: Thomas Abraham thomas...@samsung.com
---
The new CPU clock type allows the use of generic CPUfreq drivers. So for
Exynos4210/5250, switch to using generic cpufreq driver. For Exynos5420,
which did not have CPUfreq driver support, enable the use of generic
CPUfreq driver.
Suggested-by: Tomasz Figa t.f...@samsung.com
Cc: Kukjin Kim
With some of the Exynos SoCs switched over to use the generic CPUfreq drivers,
the unused clock aliases can be removed. In addition to this, the individual
clock blocks which are now encapsulated with the consolidate CPU clock type
can now be marked with read-only flags.
Cc: Tomasz Figa
Exynos4210 and Exynos5250 based platforms have switched over to use generic
cpufreq drivers for cpufreq functionality. So the Exynos specific cpufreq
drivers for these platforms can be removed.
Cc: Viresh Kumar viresh.ku...@linaro.org
Signed-off-by: Thomas Abraham thomas...@samsung.com
---
Hi Tomasz,
Thanks for your review comments. I have made most of the changes you
have suggested. The suggested modifications which I did not include is
marked below.
On Sat, Jul 19, 2014 at 6:25 PM, Tomasz Figa tomasz.f...@gmail.com wrote:
Hi Thomas,
Please see my comments inline.
On
Hi Tomasz,
On Sat, Jul 19, 2014 at 6:48 PM, Tomasz Figa tomasz.f...@gmail.com wrote:
Hi Thomas,
Please see my comments inline.
On 14.07.2014 15:38, Thomas Abraham wrote:
From: Thomas Abraham thomas...@samsung.com
For Exynos 4210/5250/5420 based platforms, add CPU nodes, operating points
On Sat, Jul 19, 2014 at 6:57 PM, Tomasz Figa tomasz.f...@gmail.com wrote:
On 14.07.2014 15:38, Thomas Abraham wrote:
From: Thomas Abraham thomas...@samsung.com
Remove the platform device instantiation for exynos cpufreq driver and add
the
platform device for generic cpufreq drivers.
Cc:
On 2014년 07월 28일 23:45, Sjoerd Simons wrote:
Hey Inki,
On Mon, 2014-07-28 at 23:17 +0900, Inki Dae wrote:
On 2014년 07월 28일 17:30, Sjoerd Simons wrote:
Sorry for late,
I don't see why Exynos drm driver should be auto-loaded module. I think
all devices covered by Exynos drm framework are
Hi Tomasz,
On Sat, Jul 19, 2014 at 6:59 PM, Tomasz Figa tomasz.f...@gmail.com wrote:
Hi,
On 14.07.2014 15:38, Thomas Abraham wrote:
From: Thomas Abraham thomas...@samsung.com
Exynos4210 and Exynos5250 based platforms have switched over to use generic
cpufreq drivers for cpufreq
65 matches
Mail list logo
