From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= Subject: Re: [PATCH 0/3] ARM: EXYNOS: Fix Exynos5410 boot Date: Thu, 31 Jul 2014 07:00:40 +0200 Message-ID: <53D9CD78.2050207@suse.de> References: <1406463725-4208-1-git-send-email-afaerber@suse.de> <53D4EFBB.6000404@suse.de> <00c901cfa9fc$727b4e10$5771ea30$@samsung.com> <03f501cfac5c$2c69be90$853d3bb0$@samsung.com> <53D9BF09.7060002@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <53D9BF09.7060002@suse.de> Sender: linux-kernel-owner@vger.kernel.org To: Kukjin Kim , Doug Anderson Cc: 'Olof Johansson' , linux-samsung-soc@vger.kernel.org, 'Tarek Dakhran' , 'Kevin Hilman' , 'Pankaj Dubey' , 'Tomasz Figa' , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Ajay Kumar , Thierry Reding , Javier Martinez Canillas List-Id: linux-samsung-soc@vger.kernel.org Am 31.07.2014 05:59, schrieb Andreas F=C3=A4rber: > Hi Kukjin, >=20 > Am 31.07.2014 03:10, schrieb Kukjin Kim: >> Olof Johansson wrote: >>> >>> Hi, >>> >> Hi Olof, >> >>> On Sun, Jul 27, 2014 at 5:39 PM, Kukjin Kim = wrote: >>>> Andreas F=C3=A4rber wrote: >>>>> >>>>> Am 27.07.2014 14:22, schrieb Andreas F=C3=A4rber: >>>>>> Hello, >>>>>> >>>>>> This mini-series unbreaks booting on 5410 based ODROID-XU. >>>>>> >>>>>> Since I do not have access to a TRM, the address is a guess base= d on >>>>>> 5250 and 5410. Such a node was not present in the 3.14 downstrea= m tree. >>>>> >>>>> s/5410/5420/ >>>>> >>>> OK. >>>> >>>>>> >>>>>> Regards, >>>>>> Andreas >>>>>> >>>>>> Andreas F=C3=A4rber (3): >>>>>> Documentation: devicetree: Document exynos5410 PMU >>>>>> ARM: dts: exynos: Add PMU to Exynos5410 >>>>>> ARM: EXYNOS: Add support for Exynos5410 PMU >>>>>> >>>>>> Documentation/devicetree/bindings/arm/samsung/pmu.txt | 1 + >>>>>> arch/arm/boot/dts/exynos5410.dtsi | 5 +++++ >>>>>> arch/arm/mach-exynos/exynos.c | 1 + >>>>>> 3 files changed, 7 insertions(+) >>>>> >>>> Andreas, thanks. >>>> >>>> I'll apply this whole series. >>> >>> We're getting close to the merge window. I'd prefer not to have to >>> start reverting samsung code to recover from these regressions, so >>> please send this up very soon. >>> >> Thanks for your gentle reminder. >> >> BTW I'm waiting for exynos5250-spring support from Andreas and I'd l= ike to get >> confirmation about that from Doug. And I'm looking at s2r related pa= tches now. >> >> OK, I will send out current samsung tree tonight in my time anyway. >=20 > That would be kind. >=20 > Patches 2-3 in spring v3 should be non-functional snow refactorings f= or > you to consider, but untested by me; patch 1 you could skip if you > modify patch 2, if necessary. As for patch 4, you can see from my > spring-next branch [1] how I am successfully testing it with a TEST_O= NLY > patch: For simplefb usage I comment out the /dp-controller node to av= oid > drm/exynos detection (not enabling the driver in the user's .config > would be an alternative); when I run into issues with the drm during > testing, I can usually ssh in via USB ethernet/wifi. >=20 > In the dmesg for drm/exynos bridge series testing [2] (which I guess = is > not gonna hit 3.17 any more?) I noticed that the USB3503 /usb-hub nod= e > new in v3 is not working yet (complains about lack of #gpio-cells, I > guess for my reset-gpios property), not sure how to fix, so we/you co= uld > probably just drop that node - preparing to test that now. Misread that message, it does not seem to be fatal. I do see the device as /sys/devices/usb-hub. [ 0.618757] of_get_named_gpiod_flags: can't parse gpios property of node '/usb-hub[0]' [ 0.618763] of_get_named_gpiod_flags: can't parse gpios property of node '/usb-hub[0]' [ 0.618777] /usb-hub: could not get #gpio-cells for /pinctrl@13400000/hsic-reset [ 0.620743] of_get_named_gpiod_flags: can't parse gpios property of node '/usb-hub[0]' [ 0.629797] usb3503 usb-hub: switched to HUB mode [ 0.631752] usb3503 usb-hub: usb3503_probe: probed in hub mode Andreas > As for the rest of patch 4, it's a new DT, so we could fix up any > remaining bugs during 3.17 RC cycle, if it looks sane to you guys now= =2E I > had replied to two series - namely cpufreq [3] and dwmmc [4] - where > merge conflicts might arise. Let me know if you need a respin for any= thing. >=20 > Regards, > Andreas >=20 > [1] https://github.com/afaerber/linux/commits/spring-next > [2] > http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg3492= 7.html > [3] > http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg3480= 7.html > [4] > http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg3489= 8.html >=20 --=20 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=C3=BCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=C3=B6rffer; HRB 16746 AG N=C3= =BCrnberg From mboxrd@z Thu Jan 1 00:00:00 1970 From: afaerber@suse.de (=?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?=) Date: Thu, 31 Jul 2014 07:00:40 +0200 Subject: [PATCH 0/3] ARM: EXYNOS: Fix Exynos5410 boot In-Reply-To: <53D9BF09.7060002@suse.de> References: <1406463725-4208-1-git-send-email-afaerber@suse.de> <53D4EFBB.6000404@suse.de> <00c901cfa9fc$727b4e10$5771ea30$@samsung.com> <03f501cfac5c$2c69be90$853d3bb0$@samsung.com> <53D9BF09.7060002@suse.de> Message-ID: <53D9CD78.2050207@suse.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Am 31.07.2014 05:59, schrieb Andreas F?rber: > Hi Kukjin, > > Am 31.07.2014 03:10, schrieb Kukjin Kim: >> Olof Johansson wrote: >>> >>> Hi, >>> >> Hi Olof, >> >>> On Sun, Jul 27, 2014 at 5:39 PM, Kukjin Kim wrote: >>>> Andreas F?rber wrote: >>>>> >>>>> Am 27.07.2014 14:22, schrieb Andreas F?rber: >>>>>> Hello, >>>>>> >>>>>> This mini-series unbreaks booting on 5410 based ODROID-XU. >>>>>> >>>>>> Since I do not have access to a TRM, the address is a guess based on >>>>>> 5250 and 5410. Such a node was not present in the 3.14 downstream tree. >>>>> >>>>> s/5410/5420/ >>>>> >>>> OK. >>>> >>>>>> >>>>>> Regards, >>>>>> Andreas >>>>>> >>>>>> Andreas F?rber (3): >>>>>> Documentation: devicetree: Document exynos5410 PMU >>>>>> ARM: dts: exynos: Add PMU to Exynos5410 >>>>>> ARM: EXYNOS: Add support for Exynos5410 PMU >>>>>> >>>>>> Documentation/devicetree/bindings/arm/samsung/pmu.txt | 1 + >>>>>> arch/arm/boot/dts/exynos5410.dtsi | 5 +++++ >>>>>> arch/arm/mach-exynos/exynos.c | 1 + >>>>>> 3 files changed, 7 insertions(+) >>>>> >>>> Andreas, thanks. >>>> >>>> I'll apply this whole series. >>> >>> We're getting close to the merge window. I'd prefer not to have to >>> start reverting samsung code to recover from these regressions, so >>> please send this up very soon. >>> >> Thanks for your gentle reminder. >> >> BTW I'm waiting for exynos5250-spring support from Andreas and I'd like to get >> confirmation about that from Doug. And I'm looking at s2r related patches now. >> >> OK, I will send out current samsung tree tonight in my time anyway. > > That would be kind. > > Patches 2-3 in spring v3 should be non-functional snow refactorings for > you to consider, but untested by me; patch 1 you could skip if you > modify patch 2, if necessary. As for patch 4, you can see from my > spring-next branch [1] how I am successfully testing it with a TEST_ONLY > patch: For simplefb usage I comment out the /dp-controller node to avoid > drm/exynos detection (not enabling the driver in the user's .config > would be an alternative); when I run into issues with the drm during > testing, I can usually ssh in via USB ethernet/wifi. > > In the dmesg for drm/exynos bridge series testing [2] (which I guess is > not gonna hit 3.17 any more?) I noticed that the USB3503 /usb-hub node > new in v3 is not working yet (complains about lack of #gpio-cells, I > guess for my reset-gpios property), not sure how to fix, so we/you could > probably just drop that node - preparing to test that now. Misread that message, it does not seem to be fatal. I do see the device as /sys/devices/usb-hub. [ 0.618757] of_get_named_gpiod_flags: can't parse gpios property of node '/usb-hub[0]' [ 0.618763] of_get_named_gpiod_flags: can't parse gpios property of node '/usb-hub[0]' [ 0.618777] /usb-hub: could not get #gpio-cells for /pinctrl at 13400000/hsic-reset [ 0.620743] of_get_named_gpiod_flags: can't parse gpios property of node '/usb-hub[0]' [ 0.629797] usb3503 usb-hub: switched to HUB mode [ 0.631752] usb3503 usb-hub: usb3503_probe: probed in hub mode Andreas > As for the rest of patch 4, it's a new DT, so we could fix up any > remaining bugs during 3.17 RC cycle, if it looks sane to you guys now. I > had replied to two series - namely cpufreq [3] and dwmmc [4] - where > merge conflicts might arise. Let me know if you need a respin for anything. > > Regards, > Andreas > > [1] https://github.com/afaerber/linux/commits/spring-next > [2] > http://www.mail-archive.com/linux-samsung-soc at vger.kernel.org/msg34927.html > [3] > http://www.mail-archive.com/linux-samsung-soc at vger.kernel.org/msg34807.html > [4] > http://www.mail-archive.com/linux-samsung-soc at vger.kernel.org/msg34898.html > -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer; HRB 16746 AG N?rnberg