Re: [PATCH 0/4] ASoC: samsung: clean up references to outdated Kconfig symbols
On Sat, 2015-02-07 at 07:50 +0800, Mark Brown wrote: On Mon, Jan 19, 2015 at 11:41:07AM +0100, Paul Bolle wrote: A few series of ARM cleanups regarding S5PC100 and S5PV210 were included in v3.17. These series removed these five Kconfig symbols: MACH_AQUILA MACH_GONI MACH_SMDKC100 MACH_SMDKC110 MACH_SMDKV210 This series, done on top of next-20150119, removes the remaining If you are posting a patch series please ensure that all the patches in the series are threaded in reply to the cover letter (or first patch if there isn't one) so that mail clients can see to display them as a series. Patches 2/4, 3/4, and 4/4 didn't apply. Locally I carry them in a tree that constantly rebases on top of linux-next. So locally I carry these patches on top of next-20150204. What tree would you like me to rebase this onto? Paul Bolle -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 4/4] ASoC: samsung: remove outdated Kconfig references
On Mon, Jan 19, 2015 at 11:43:02AM +0100, Paul Bolle wrote: The Kconfig symbols MACH_SMDKC110 and MACH_SMDKV210 were removed in v3.17. But the Kconfig entries for SND_SOC_SAMSUNG_SMDK_WM8580 and SND_SOC_SAMSUNG_SMDK_WM9713 still reference them. This doesn't apply against current code. signature.asc Description: Digital signature
Re: [PATCH 0/4] ASoC: samsung: clean up references to outdated Kconfig symbols
On Mon, Jan 19, 2015 at 11:41:07AM +0100, Paul Bolle wrote: A few series of ARM cleanups regarding S5PC100 and S5PV210 were included in v3.17. These series removed these five Kconfig symbols: MACH_AQUILA MACH_GONI MACH_SMDKC100 MACH_SMDKC110 MACH_SMDKV210 This series, done on top of next-20150119, removes the remaining If you are posting a patch series please ensure that all the patches in the series are threaded in reply to the cover letter (or first patch if there isn't one) so that mail clients can see to display them as a series. signature.asc Description: Digital signature
Re: [PATCH 2/4] ASoC: samsung: Remove PCM support for WM8580 on SMDK
On Mon, Jan 19, 2015 at 11:42:07AM +0100, Paul Bolle wrote: Commit 28c8331d386a (ARM: S5PV210: Remove support for board files) removed the Kconfig symbols MACH_SMDKC110 and MACH_SMDKV210. As a result the dependencies of SND_SOC_SMDK_WM8580_PCM can never be met. So remove the unbuildable SoC PCM Audio support for WM8580 on SMDK. This doesn't apply against current code. signature.asc Description: Digital signature
Re: [PATCH 3/4] ASoC: samsung: MACH_SMDKC100 isn't supported anymore
On Mon, Jan 19, 2015 at 11:42:45AM +0100, Paul Bolle wrote: Commit b8529ec1c1b0 (ARM: S5PC100: no more support S5PC100 SoC) removed Kconfig symbol MACH_SMDKC100. But there are still two references to that symbol left. These are now pointless. Remove them too. This doesn't apply against current code. signature.asc Description: Digital signature
Re: [PATCH 1/4] ASoC: samsung: Remove goni or aquila with the WM8994
On Mon, Jan 19, 2015 at 11:41:41AM +0100, Paul Bolle wrote: Commit 28c8331d386a (ARM: S5PV210: Remove support for board files) removed the Kconfig symbols MACH_GONI and MACH_AQUILA. As a result the dependencies of SND_SOC_GONI_AQUILA_WM8994 can never be met. So remove the unbuildable SoC I2S Audio support for AQUILA/GONI - WM8994. Applied, thanks. signature.asc Description: Digital signature
[PATCH 0/4] drm/exynos: use syscon framework to enable mipi phy
This patch series makes syscon framework to be used instead of phy framework. For this, I adds syscon support to mipi dsi driver and the relevant device tree properties to each dtsi files, Exynos4, Exynos3250 and Exynos5420. Inki Dae (4): drm/exynos: dsim: fix to control mipi phy register ARM: dts: exynos4: use pmureg device node to enable mipi phy ARM: dts: exynos3250: use pmureg device node to enable mipi phy ARM: dts: exynos5420: use pmureg device node to enable mipi phy .../devicetree/bindings/video/exynos_dsim.txt |9 ++-- arch/arm/boot/dts/exynos3250.dtsi |3 +- arch/arm/boot/dts/exynos4.dtsi |3 +- arch/arm/boot/dts/exynos5420.dtsi |3 +- drivers/gpu/drm/exynos/exynos_drm_dsi.c| 54 ++-- 5 files changed, 59 insertions(+), 13 deletions(-) -- 1.7.9.5 -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH 1/4] drm/exynos: dsim: fix to control mipi phy register
This patch fixes the issue that the try to get a phy object is failed
to enable mipi phy.
System and power management unit registers should be controlled by
syscon framework. So this patch removes existing phy framework based
codes and adds syscon support instead. However, we should support
legacy device tree binding so consider the legacy binding for compatibility.
In addition, we need to remove below device node and relevant properties,
mipi_phy: video-phy@10020710 {
compatible = samsung,s5pv210-mipi-video-phy;
reg = 0x10020710 8;
#phy-cells = 1;
};
Now camera device node uses mipi_phy node relevant properties like below,
camera {
...
csis_0: csis@1188 {
...
phys = mipi_phy 0;
phy-names = csis;
...
};
csis_1: csis@1189 {
...
phys = mipi_phy 2;
phy-names = csis;
...
};
...
};
With above, we will find below message while booting,
can't request region for resource [mem 0x10020710-0x10020717]
Signed-off-by: Inki Dae inki@samsung.com
---
.../devicetree/bindings/video/exynos_dsim.txt |9 ++--
drivers/gpu/drm/exynos/exynos_drm_dsi.c| 54 ++--
2 files changed, 56 insertions(+), 7 deletions(-)
diff --git a/Documentation/devicetree/bindings/video/exynos_dsim.txt
b/Documentation/devicetree/bindings/video/exynos_dsim.txt
index ca2b4aa..dec3b55 100644
--- a/Documentation/devicetree/bindings/video/exynos_dsim.txt
+++ b/Documentation/devicetree/bindings/video/exynos_dsim.txt
@@ -11,15 +11,18 @@ Required properties:
- clocks: list of clock specifiers, must contain an entry for each required
entry in clock-names
- clock-names: should include bus_clkand pll_clk entries
- - phys: list of phy specifiers, must contain an entry for each required
-entry in phy-names
- - phy-names: should include dsim entry
+ - samsung,pmureg: handle to syscon used to control the PMU registers
- vddcore-supply: MIPI DSIM Core voltage supply (e.g. 1.1V)
- vddio-supply: MIPI DSIM I/O and PLL voltage supply (e.g. 1.8V)
- samsung,pll-clock-frequency: specifies frequency of the pll_clk clock
- #address-cells, #size-cells: should be set respectively to 1 and 0
according to DSI host bindings (see MIPI DSI bindings [1])
+Deprecated properties for MIPI DSI Master:
+ - phys: list of phy specifiers, must contain an entry for each required
+entry in phy-names (Deprecated)
+ - phy-names: should include dsim entry (Deprecated)
+
Optional properties:
- samsung,power-domain: a phandle to DSIM power domain node
diff --git a/drivers/gpu/drm/exynos/exynos_drm_dsi.c
b/drivers/gpu/drm/exynos/exynos_drm_dsi.c
index 05fe93d..38b025e 100644
--- a/drivers/gpu/drm/exynos/exynos_drm_dsi.c
+++ b/drivers/gpu/drm/exynos/exynos_drm_dsi.c
@@ -23,6 +23,8 @@
#include linux/phy/phy.h
#include linux/regulator/consumer.h
#include linux/component.h
+#include linux/mfd/syscon.h
+#include linux/regmap.h
#include video/mipi_display.h
#include video/videomode.h
@@ -263,6 +265,8 @@ struct exynos_dsi_transfer {
struct exynos_dsi_driver_data {
unsigned int plltmr_reg;
+ unsigned int mipi_phy_offset;
+ unsigned int mipi_phy_en_shift;
unsigned int has_freqband:1;
unsigned int has_clklane_stop:1;
};
@@ -277,6 +281,7 @@ struct exynos_dsi {
void __iomem *reg_base;
struct phy *phy;
+ struct regmap *pmureg;
struct clk *pll_clk;
struct clk *bus_clk;
struct regulator_bulk_data supplies[2];
@@ -313,21 +318,29 @@ static struct exynos_dsi_driver_data
exynos3_dsi_driver_data = {
.plltmr_reg = 0x50,
.has_freqband = 1,
.has_clklane_stop = 1,
+ .mipi_phy_offset = 0x710,
+ .mipi_phy_en_shift = 0,
};
static struct exynos_dsi_driver_data exynos4_dsi_driver_data = {
.plltmr_reg = 0x50,
.has_freqband = 1,
.has_clklane_stop = 1,
+ .mipi_phy_offset = 0x710,
+ .mipi_phy_en_shift = 0,
};
static struct exynos_dsi_driver_data exynos4415_dsi_driver_data = {
.plltmr_reg = 0x58,
.has_clklane_stop = 1,
+ .mipi_phy_offset = 0x710,
+ .mipi_phy_en_shift = 0,
};
static struct exynos_dsi_driver_data exynos5_dsi_driver_data = {
.plltmr_reg = 0x58,
+ .mipi_phy_offset = 0x714,
+ .mipi_phy_en_shift = 0,
};
static struct of_device_id exynos_dsi_of_match[] = {
@@ -1294,6 +1307,7 @@ static const struct mipi_dsi_host_ops exynos_dsi_ops = {
static int exynos_dsi_poweron(struct exynos_dsi *dsi)
{
+ struct exynos_dsi_driver_data *driver_data = dsi-driver_data;
int ret;
ret =
[PATCH 2/4] ARM: dts: exynos4: use pmureg device node to enable mipi phy
This patch removes mipi phy relevant properties from dsim device node and makes the pmureg device node to be used instead to enable mipi phy. Signed-off-by: Inki Dae inki@samsung.com --- arch/arm/boot/dts/exynos4.dtsi |3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/arch/arm/boot/dts/exynos4.dtsi b/arch/arm/boot/dts/exynos4.dtsi index b8168f1..42dfdcf 100644 --- a/arch/arm/boot/dts/exynos4.dtsi +++ b/arch/arm/boot/dts/exynos4.dtsi @@ -148,8 +148,7 @@ reg = 0x11C8 0x1; interrupts = 0 79 0; samsung,power-domain = pd_lcd0; - phys = mipi_phy 1; - phy-names = dsim; + samsung,pmureg = pmu_system_controller; clocks = clock CLK_DSIM0, clock CLK_SCLK_MIPI0; clock-names = bus_clk, pll_clk; status = disabled; -- 1.7.9.5 -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH 3/4] ARM: dts: exynos3250: use pmureg device node to enable mipi phy
This patch removes mipi phy relevant properties from dsim device node and makes the pmureg device node to be used instead to enable mipi phy. Signed-off-by: Inki Dae inki@samsung.com --- arch/arm/boot/dts/exynos3250.dtsi |3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/arch/arm/boot/dts/exynos3250.dtsi b/arch/arm/boot/dts/exynos3250.dtsi index 2246549..eb80802 100644 --- a/arch/arm/boot/dts/exynos3250.dtsi +++ b/arch/arm/boot/dts/exynos3250.dtsi @@ -246,8 +246,7 @@ interrupts = 0 83 0; samsung,phy-type = 0; samsung,power-domain = pd_lcd0; - phys = mipi_phy 1; - phy-names = dsim; + samsung,pmureg = pmu_system_controller; clocks = cmu CLK_DSIM0, cmu CLK_SCLK_MIPI0; clock-names = bus_clk, pll_clk; #address-cells = 1; -- 1.7.9.5 -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH 4/4] ARM: dts: exynos5420: use pmureg device node to enable mipi phy
This patch removes mipi phy relevant properties from dsim device node and makes the pmureg device node to be used instead to enable mipi phy. Signed-off-by: Inki Dae inki@samsung.com --- arch/arm/boot/dts/exynos5420.dtsi |3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/arch/arm/boot/dts/exynos5420.dtsi b/arch/arm/boot/dts/exynos5420.dtsi index 6d38f8b..b8b8826 100644 --- a/arch/arm/boot/dts/exynos5420.dtsi +++ b/arch/arm/boot/dts/exynos5420.dtsi @@ -525,8 +525,7 @@ compatible = samsung,exynos5410-mipi-dsi; reg = 0x1450 0x1; interrupts = 0 82 0; - phys = mipi_phy 1; - phy-names = dsim; + samsung,pmureg = pmu_system_controller; clocks = clock CLK_DSIM1, clock CLK_SCLK_MIPI1; clock-names = bus_clk, pll_clk; #address-cells = 1; -- 1.7.9.5 -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH] ARM: dts: exynos4412-trats2: set display clock correctly
This patch sets display clock correctly.
If Display clock isn't set correctly then you would find below messages
and Display controller doesn't work correctly since a patch[1]
exynos-drm: No connectors reported connected with modes
[drm] Cannot find any crtc or sizes - going 1024x768
[1] commit abc0b1447d49 (drm: Perform basic sanity checks on probed modes)
Signed-off-by: Inki Dae inki@samsung.com
---
arch/arm/boot/dts/exynos4412-trats2.dts |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/exynos4412-trats2.dts
b/arch/arm/boot/dts/exynos4412-trats2.dts
index 29231b4..1ec4d33 100644
--- a/arch/arm/boot/dts/exynos4412-trats2.dts
+++ b/arch/arm/boot/dts/exynos4412-trats2.dts
@@ -691,7 +691,7 @@
display-timings {
timing-0 {
- clock-frequency = 0;
+ clock-frequency = 57153600;
hactive = 720;
vactive = 1280;
hfront-porch = 5;
--
1.7.9.5
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
exynos4412: misc issues on Hardkernel Odroid boards
Hello, I've collected some of the more serious remaining problems on the Hardkernel Odroid boards (here on an X2). 1) When using cpufreq-exynos and having selected the 'ondemand' governor, the system shutdown/reboot process doesn't complete and hangs before the end. I'm currently hotfixing this by switching to 'performance' governor in a custom initscript. 2) When reading the 'clk_summary' debugfs entry the system locks up immediately. Currently hotfixing this by having the ISP powerdomain always-on. The problem seems to be known, at least it was mentioned here: http://www.spinics.net/lists/linux-samsung-soc/msg39488.html 3) Maybe related to (1). I'm experiencing high SoC temperatures after shutting the system down and leaving the AC connector plugged into the board. The shutdown procedure is like mentioned in (1): Switch to 'performance' and then do a normal 'shutdown -h now'. I was wondering if the Odroid boards need a special shutdown procedure (like designed in the odroid-restart handler patch) after all. 4) Spinlock BUGs triggered by the sdhci subsystem (so for the people using the system with a SD card). This is also a known problem, I think first mentioned here: http://www.spinics.net/lists/linux-mmc/msg27277.html Currently fixing this with this patch: https://github.com/tobiasjakobi/linux-odroid/commit/abc749843dd7022d01322dca3db0181211a30cd8 With best wishes, Tobias -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
