On Wed, Nov 05, 2014 at 03:02:58PM +, Charles Keepax wrote:
On Wed, Nov 05, 2014 at 01:04:37PM +0100, Stam, Michel [FINT] wrote:
Hello Charles,
After looking around I found the reset value for the 8772 chip, which
seems to be 0x1E1 (ANAR register).
This equates to (according to
Hi,
On last next (next-20141104, next-20141105) booting locks after
initializing Exynos DRM (Trats2 board):
[2.028283] [drm] Initialized drm 1.1.0 20060810
[ 240.505795] INFO: task swapper/0:1 blocked for more than 120 seconds.
[ 240.510825] Not tainted 3.18.0-rc3-next-20141105 #794
On Mon, Sep 01, 2014 at 03:40:02PM +0530, Ajay Kumar wrote:
The AUO B116XW03 is a 11.6 HD TFT LCD panel connecting to a LVDS
interface and with an integrated LED backlight unit.
This panel is used on the Samsung Chromebook(XE303C12).
Signed-off-by: Ajay Kumar ajaykumar...@samsung.com
---
Exynos7 SPI controller supports only the auto Selection of
CS toggle mode and Exynos7 SoC includes six SPI controllers.
Add support for these changes in Exynos7 SPI controller driver.
Signed-off-by: Padmavathi Venna padm...@samsung.com
---
.../devicetree/bindings/spi/spi-samsung.txt|
On 6 November 2014 00:11, Kevin Hilman khil...@kernel.org wrote:
Rafael J. Wysocki r...@rjwysocki.net writes:
On Wednesday, November 05, 2014 02:43:31 PM Kevin Hilman wrote:
Dmitry Torokhov dmitry.torok...@gmail.com writes:
On Thu, Oct 30, 2014 at 01:38:30PM -0700, Kevin Hilman wrote:
On Thu, Nov 06, 2014 at 11:06:51AM +0200, Riku Voipio wrote:
On Wed, Nov 05, 2014 at 03:02:58PM +, Charles Keepax wrote:
On Wed, Nov 05, 2014 at 01:04:37PM +0100, Stam, Michel [FINT] wrote:
Hello Charles,
After looking around I found the reset value for the 8772 chip, which
On Thu, Nov 06, 2014 at 03:21:49PM +0530, Padmavathi Venna wrote:
Exynos7 SPI controller supports only the auto Selection of
CS toggle mode and Exynos7 SoC includes six SPI controllers.
Add support for these changes in Exynos7 SPI controller driver.
Could you give a bit more detail on what the
This patch resolves temporarily infinite loop issue incurred
when Exynos drm driver is enabled and multi-platform kernel
is used by registering Exynos drm device object only in case
of Exynos SoC. So this patch will be replaced with more generic
way later.
Signed-off-by: Inki Dae
Hello Eduardo Valentin,
On Thursday, November 06, 2014 2:17 AM, Eduardo Valentin wrote:
Hello Yadwinder,
On Wed, Nov 05, 2014 at 05:46:25PM +0530, Yadwinder Singh Brar wrote:
Existing code updates cupfreq policy only while executing
cpufreq_apply_cooling() function (i.e. when
On Thu, Nov 06, 2014 at 10:01:04AM +, Charles Keepax wrote:
On Thu, Nov 06, 2014 at 11:06:51AM +0200, Riku Voipio wrote:
The asix on arndale comes semi-configured from u-boot, which I guess is
not the state kernel expects it to come in. At least in my case where
I use tftp from u-boot
On 06.11.2014 11:32, Inki Dae wrote:
This patch resolves temporarily infinite loop issue incurred
when Exynos drm driver is enabled and multi-platform kernel
is used by registering Exynos drm device object only in case
of Exynos SoC. So this patch will be replaced with more generic
way later.
On 2014년 11월 06일 21:11, Krzysztof Kozłowski wrote:
On 06.11.2014 11:32, Inki Dae wrote:
This patch resolves temporarily infinite loop issue incurred
when Exynos drm driver is enabled and multi-platform kernel
is used by registering Exynos drm device object only in case
of Exynos SoC. So this
Hi Inki,
Could you please give a review to this series?
Thanks.
Gustavo
2014-10-31 Gustavo Padovan gust...@padovan.org:
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
It is not even used in this header anymore.
Signed-off-by: Gustavo Padovan
Hello Riku and Charles,
I tried this with my original patch and the suggested patch applied,
this seems to work for me too.
One thing that bothers me, is the suspend / resume situation; usbnet.c
seems to call the bind( ) on probe( ). Suspend / resume do not seem to
call bind( ) directly.
As
On Thu, Nov 06, 2014 at 01:39:07PM +0100, Stam, Michel [FINT] wrote:
Hello Riku and Charles,
I tried this with my original patch and the suggested patch applied,
this seems to work for me too.
One thing that bothers me, is the suspend / resume situation; usbnet.c
seems to call the bind( )
On 2014년 11월 06일 22:00, Krzysztof Kozlowski wrote:
On czw, 2014-11-06 at 21:32 +0900, Inki Dae wrote:
On 2014년 11월 06일 21:11, Krzysztof Kozłowski wrote:
On 06.11.2014 11:32, Inki Dae wrote:
This patch resolves temporarily infinite loop issue incurred
when Exynos drm driver is enabled and
Hello Charles and Riku,
I've quickly tested this on a 3.10 kernel i had around;
I enabled CONFIG_PM, CONFIG_PM_RUNTIME, CONFIG_PM_AUTOSLEEP,
CONFIG_SUSPEND, CONFIG_SUSPEND_FREEZER, CONFIG_FREEZER in the kernel (by
default they are disabled for our setup, I enabled anything regarded to
runtime
On Thu, Nov 06, 2014 at 03:01:56PM +0100, Stam, Michel [FINT] wrote:
Hello Charles and Riku,
I've quickly tested this on a 3.10 kernel i had around;
I enabled CONFIG_PM, CONFIG_PM_RUNTIME, CONFIG_PM_AUTOSLEEP,
CONFIG_SUSPEND, CONFIG_SUSPEND_FREEZER, CONFIG_FREEZER in the kernel (by
default
This patch resovles the infinite loop issue incurred
when Exyno drm driver is enabled but all kms drivers
are disabled on Exynos board by returning -EPROBE_DEFER
only in case that there is kms device registered.
Signed-off-by: Inki Dae inki@samsung.com
---
Document new device tree bindings for Maxim 77693 charger driver.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
Documentation/devicetree/bindings/mfd/max77693.txt | 45 ++
1 file changed, 45 insertions(+)
diff --git
Add new driver for Maxim 77693 switch-mode charger (part of max77693
MFD driver) providing power supply class information to userspace.
The charger has +20V tolerant input. Current input can be set from 0 to
2.58 A. The charger can deliver up to 2.1 A to the battery or 3.5 A to
the system (when
Document the settings exported by max77693 charger driver through sysfs
entries:
- fast_charge_timer
- top_off_threshold_current
- top_off_timer
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
Documentation/ABI/testing/sysfs-class-power | 42 +
1
Hi,
I got ack from Sebastian [1] but only for charger driver patch. This
means that I still need an ack for documentation (bindings, sysfs)...
Changes since v2
1. Add ack from Sebastian Reichel (charger driver).
2. Drop patch mfd: max77693: Map charger device to its own
Hi Inki,
With all respect,
On 06/11/14 14:10, Inki Dae wrote: This patch resovles the infinite
loop issue incurred
when Exyno drm driver is enabled but all kms drivers
are disabled on Exynos board by returning -EPROBE_DEFER
only in case that there is kms device registered.
I believe it's
On 06/11/14 15:44, Emil Velikov wrote:
Hi Inki,
With all respect,
On 06/11/14 14:10, Inki Dae wrote: This patch resovles the infinite
loop issue incurred
when Exyno drm driver is enabled but all kms drivers
are disabled on Exynos board by returning -EPROBE_DEFER
only in case that there
[dropping some addresses from Cc]
On 03/10/14 12:36, Ulf Hansson wrote:
On 2 October 2014 17:54, Sylwester Nawrocki s.nawro...@samsung.com wrote:
On 02/10/14 15:30, Ulf Hansson wrote:
[...]
Correct me if I am wrong, but I think in principle these exynos
drivers don't use
Register with kernel power-off handler instead of setting pm_power_off
directly. Always use register_power_off_handler_simple as there is no
indication that more than one power-off handler is registered.
If the power-off handler only resets the system or puts the CPU in sleep mode,
select the
On Thu, 2014-11-06 at 23:10 +0900, Inki Dae wrote:
This patch resovles the infinite loop issue incurred
when Exyno drm driver is enabled but all kms drivers
are disabled on Exynos board by returning -EPROBE_DEFER
only in case that there is kms device registered.
It would be nice if you could
Hello Yadwinder,
On Thu, Nov 06, 2014 at 04:26:27PM +0530, Yadwinder Singh Brar wrote:
Hello Eduardo Valentin,
On Thursday, November 06, 2014 2:17 AM, Eduardo Valentin wrote:
Hello Yadwinder,
On Wed, Nov 05, 2014 at 05:46:25PM +0530, Yadwinder Singh Brar wrote:
Existing code updates
[...]
Yes they would, although they require some minor additional adaptations.
Those resources that are enabled from the driver's runtime PM resume
callback, should also be enabled during -probe(). The
pm_runtime_set_active() will then update the state to reflect this.
Then, if
Hello Lukasz,
On Thu, Oct 09, 2014 at 06:38:37PM +0200, Lukasz Majewski wrote:
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 ++
Hello Lukasz,
On Thu, Oct 09, 2014 at 06:38:38PM +0200, Lukasz Majewski wrote:
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 +
On Thu, Oct 09, 2014 at 06:38:39PM +0200, Lukasz Majewski wrote:
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
Hello,
On Thu, Oct 09, 2014 at 06:38:40PM +0200, Lukasz Majewski wrote:
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
From: Naveen Krishna Ch naveenkrishna...@gmail.com
Add initial device tree nodes for EXYNOS7 SoC and board dts file
to support Espresso board based on Exynos7 SoC.
Signed-off-by: Naveen Krishna Ch naveenkrishna...@gmail.com
Signed-off-by: Abhilash Kesavan a.kesa...@samsung.com
Reviewed-by:
From: Pankaj Dubey pankaj.du...@samsung.com
Add symlink to include/dt-bindings from arch/arm64/boot/dts/include/ to
match the ones in ARM architectures so that preprocessed device
tree files can include various useful constant definitions.
See commit c58299aa8754 (kbuild: create an include
Exynos7 is a System-On-Chip that is based on 64-bit ARMv8 RISC processor
(Cortex-A57). This patchset adds arch/device tree support for Exynos7.
These were originally part of 2 patchsets[1][2] adding support for Exynos7.
The clock and pinctrl patches are going through the respective maintainer's
From: Naveen Krishna Ch naveenkrishna...@gmail.com
Add intial 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
Adds PMU DT node for exynos7 SoC.
Signed-off-by: Abhilash Kesavan a.kesa...@samsung.com
---
.../devicetree/bindings/arm/samsung/pmu.txt|1 +
arch/arm64/boot/dts/exynos/exynos7.dtsi|5 +
2 files changed, 6 insertions(+)
diff --git
From: Alim Akhtar alim.akh...@samsung.com
This patch adds the necessary Kconfig entries to enable
support for the ARMv8 based Exynos7 SoC. It also enables
RTC, WDT and Pinctrl for Exynos7.
Signed-off-by: Alim Akhtar alim.akh...@samsung.com
Signed-off-by: Naveen Krishna Ch
Add nodes for 3 mmc channels, 12 i2c channels, rtc, watchdog and adc
on Exynos7.
Signed-off-by: Naveen Krishna Ch naveenkrishna...@gmail.com
Signed-off-by: Abhilash Kesavan a.kesa...@samsung.com
---
arch/arm64/boot/dts/exynos/exynos7-espresso.dts | 45
From: Alim Akhtar alim.akh...@samsung.com
Enable Exynos7 SOC in the arm64 defconfig. Also enable the
samsung serial driver needed by this SoC.
Signed-off-by: Alim Akhtar alim.akh...@samsung.com
Signed-off-by: Abhilash Kesavan a.kesa...@samsung.com
---
arch/arm64/configs/defconfig |4
1
This patch supports Exynos4415 SoC.
Signed-off-by: YoungJun Cho yj44@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
Documentation/devicetree/bindings/video/samsung-fimd.txt | 1 +
drivers/gpu/drm/exynos/exynos_drm_fimd.c | 11 +++
2 files changed,
This patch adds mipi dsi device node to exynos4415.dtsi.
Signed-off-by: YoungJun Cho yj44@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
arch/arm/boot/dts/exynos4415.dtsi | 15 +++
1 file changed, 15 insertions(+)
diff --git a/arch/arm/boot/dts/exynos4415.dtsi
This patch adds fimd device node to exynos4415.dtsi.
Signed-off-by: YoungJun Cho yj44@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
arch/arm/boot/dts/exynos4415.dtsi | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/exynos4415.dtsi
This patch supports Exynos4415 SoC.
Signed-off-by: YoungJun Cho yj44@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
Documentation/devicetree/bindings/video/exynos_dsim.txt | 1 +
drivers/gpu/drm/exynos/exynos_drm_dsi.c | 7 +++
2 files changed, 8
This patch series adds of_device_id and relevant device nodes
for Exynos4415 SoC support.
This is based on exynos-drm-next branch for drm/exynos,
and is based on for-next branch in linux-samsung git for dts.
I think this requires rebase for the patch drm/exynos: add has_vtsel flag[1].
[1]
Dear Linus,
Could you please review this patch?
Best Regards,
Chanwoo Choi
On 10/27/2014 10:21 AM, Chanwoo Choi wrote:
From: Tomasz Figa tomasz.f...@gmail.com
The pin controllers of Exynos4415 are similar to Exynos4412, but certain
differences cause the need to create separate driver data
Hi Chanwoo,
2014-11-07 15:23 GMT+09:00 Chanwoo Choi cw00.c...@samsung.com:
Dear Linus,
Could you please review this patch?
I'll take care of this during this weekend.
Sorry for all the delays, but I was in the middle of relocation to
another country and I just didn't have enough time yet to
I2S on exynos7 includes the below changes
- has got support for lower root clock sampling frequencies like 64,
128, 96, 192fs. I2S on previous SoCs supports only 256,512,384 and 768.
- supports 7.1CH TDM mode for recording. exynos5 has only 7.1CH TDM mode
for playback.
- secondary dai
Internal DMA is available only on some of Samsung platforms.
So added a quirk for the same and made it optional.
Signed-off-by: Padmavathi Venna padm...@samsung.com
---
include/linux/platform_data/asoc-s3c.h |1 +
sound/soc/samsung/i2s.c| 12 ++--
2 files changed, 7
Exynos7 I2S controller has no internal dma, supports more
no. of root clock sampling frequencies and has more no.of Rx
fifos to support 7.1CH recording in TDM mode. Due to more no.
of root clock frequency values some of the bit offsets got
shifted up by one. Also I2S1 on previous Samsung platforms
52 matches
Mail list logo
