Re: [RFC 0/5] ARM: EXYNOS: ODROID-XU DT and LEDs
Andreas Färber afaer...@suse.de writes: Kukjin, Am 28.07.2014 14:18, schrieb Andreas Färber: 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. Hakjoo, can you please reply with a Signed-off-by to your patches so that we can get them into upstream? Thanks in advance! FTR, Hakjoo Kim did reply with signed off patches (thanks again!) and updated their branch accordingly: https://github.com/hardkernel/linux/commits/odroid-3.14.y-linaro https://github.com/hardkernel/linux/commit/53edc3da0d1da287517681b47daf36679637b6ba https://github.com/hardkernel/linux/commit/afdc310e47e4d1799719566bfb5a47c55141a7cb Andreas Färber (3): ARM: dts: exynos5410: Clean up SMDK5410 indentation ARM: dts: exynos5410: Prepare ODROID-XU device tree The functional changes below haven't been reviewed yet, but could you consider applying trivial patches 1-2? Regards, Andreas ARM: dts: exynos5410: Add ODROID-XU LEDs Hakjoo Kim (2): pinctrl: exynos: add exynos5410 SoC specific data ARM: dts: add pinctrl support to Exynos5410 What happened with this set? It appears that 1-2 were never merged nor was there any review of the remaining patches. Cheers, - Ben pgp05eGPh5jhr.pgp Description: PGP signature
Re: [PATCH v6 0/2] irqchip: Move Exynos PM to use stacked domains
Marc, On Wed, Mar 11, 2015 at 03:44:51PM +, Marc Zyngier wrote: This series is extracted from [4], which is trying to remove all traces of gic_arch_extn from the tree. As some maintainers are more responsive than others (understatement of the year...), I've decided to split it per sub-arch, and get it moving, at least partially. This series addresses Exynos by converting its PM support to a stacked domain on top of the standard GIC. Based on 4.0-rc1. * From v5: [5] - Added a big fat warning when an old DT is detected (as requested by Jason) - Added support for Exynos3250 - Allow interrupt affinity to be changed * From v4: [4] - Extracted from the full series - Rebased on 4.0-rc1 * From v3 [3]: - Rebased on top of the patch working around hardcoded IRQ on OMAP4/5 [4] - Fixed more iMX6 DTs (Stephan) - Fixed Exynos4/5 DTs * From v2 [2]: - Addressed numerous comments from Thierry - Merged bug fixes from Nishanth - Merged bug fix from Stefan * From v1 [1]: - Rebased on 3.19-rc3 - Fixed a number of additional platforms - Added crossbar conversion to stacked domains - Merged bug fixes from Nishanth [5]: http://lists.infradead.org/pipermail/linux-arm-kernel/2015-February/325368.html [4]: http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/317531.html [3]: http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/315385.html [2]: http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/314041.html [1]: http://lists.infradead.org/pipermail/linux-arm-kernel/2014-November/307338.html Marc Zyngier (2): ARM: exynos4/5: convert pmu wakeup to stacked domains DT: exynos: update PMU binding .../devicetree/bindings/arm/samsung/pmu.txt| 17 +++ arch/arm/boot/dts/exynos3250.dtsi | 6 +- arch/arm/boot/dts/exynos4.dtsi | 4 + arch/arm/boot/dts/exynos5250.dtsi | 4 + arch/arm/boot/dts/exynos5420.dtsi | 4 + arch/arm/mach-exynos/exynos.c | 15 +-- arch/arm/mach-exynos/suspend.c | 139 ++--- 7 files changed, 164 insertions(+), 25 deletions(-) Applied to irqchip/stacked-exynos to give the series some time in -next. thx, Jason. -- 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] PM / devfreq: remove checks for CONFIG_EXYNOS_ASV
MyungJoo Ham myungjoo@samsung.com writes: On Fri, May 23, 2014 at 1:52 PM, MyungJoo Ham myungjoo@samsung.com wrote: On Thu, May 22, 2014 at 5:37 AM, Paul Bolle pebo...@tiscali.nl wrote: Checks for CONFIG_EXYNOS_ASV were added in v3.3. But the related Kconfig symbol has never been added to the tree. Remove these checks, as they always evaluate to false. Signed-off-by: Paul Bolle pebo...@tiscali.nl Thanks for pointing this out. ASV was supposed to be merged, but it appears it failed or never attempted. I will merge with the next batch (this week). Cheers, MyungJoo. Uh.. ASV itself affects the power efficiency; thus, I'd like to keep it alive, but not as the current form. What is the current status of ASV? I've not seen any patches since this was sent. Cheers, - Ben pgp1EJZb4wX1s.pgp Description: PGP signature
[PATCH 1/1] ARM: dts: don't make DP a consumer of DISP1 on Exynos5250
By making the DP controller a consumer of DISP1, the PD is powered
off when the exynos-dp probe is deferred and powered on again when
the exynos-drm driver is probed.
But this causes the exynos-dp driver failing to obtain the stream
clock since the FIMD has been powered off with the DISP1 PD:
exynos-dp 145b.dp-controller: Timeout of video streamclk ok
exynos-dp 145b.dp-controller: unable to config video
The Exynos5250 documentation doesn't mention that the Display Port
Transmitter module is included in the DISP1 PD so the device should
not have a reference to this Power Domain.
This patch fixes video display on an Exynos5250 Snow Chromebook.
Fixes: 2d2c9a8d0a4f (ARM: dts: add display power domain for exynos5250)
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
Hello Andrzej and Marek,
I need this patch to have display working on an Snow Chromebook with
next20150312. I remember testing the mentioned patch that introduced
the regression when it was posted and I did not find any issues with
it. Do you know what could had caused this behavior change?
According to the Exynos5250 documentation I've access to, the modules
that are included in the DISP1 power domain are LCD controller (FIMD),
MIE1 VP, MIXER, TV Encoder and HDMI so I think this patch is correct
since it not only solves the regression but also models the HW better.
Please let me know if you think it should be fixed in a different way.
Best regards,
Javier
arch/arm/boot/dts/exynos5250.dtsi | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/boot/dts/exynos5250.dtsi
b/arch/arm/boot/dts/exynos5250.dtsi
index adbde1adad95..ffb505171216 100644
--- a/arch/arm/boot/dts/exynos5250.dtsi
+++ b/arch/arm/boot/dts/exynos5250.dtsi
@@ -775,7 +775,6 @@
};
dp: dp-controller@145B {
- power-domains = pd_disp1;
clocks = clock CLK_DP;
clock-names = dp;
phys = dp_phy;
--
2.1.4
--
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: [GIT PULL 2/2] Samsung fixes-2 for v4.0
Hello Kukjin, On Fri, Mar 6, 2015 at 10:43 AM, Kukjin Kim kg...@kernel.org wrote: Yes, the problem is the Exynos DRM driver which has a lot of issues. It's broken if CONFIG_DRM_EXYNOS_IOMMU is enabled which defaults to yes after commit 8dcc14f82f06 (drm/exynos: IOMMU support should not be selectable by user). I posted a patch to disable IOMMU support on Exynos to avoid these boot failures and also mentioned to Kukjin that it should be a fix for 4.0 [0]. But even with IOMMU disabled, the Exynos DRM is broken in some boards [1] so we may have to disable that driver until everything gets sorted out and is stable again. Yes, the fix is in my tree and it will be sent to upstream via arm-soc soon. Sorry for pestering you but I see that the patch to disable EXYNOS_IOMMU is still not in Linus' master and we are almost in 4.0-rc4 now. A patch to the Exynos DRM driver to check for IOMMU and fail gracefully has landed in 4.0-rc so now at least the machines boot but with IOMMU enabled display is broken in the Exynos5 boards. Thanks, Kukjin Best regards, Javier -- 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
