From mboxrd@z Thu Jan 1 00:00:00 1970 From: Doug Anderson Subject: Re: Unable to boot mainline on snow chromebook since 3.15 Date: Wed, 10 Sep 2014 09:03:52 -0700 Message-ID: References: <20140905122232.GP13515@arm.com> <540C202E.2060009@collabora.co.uk> <540C7F5B.6070307@gmail.com> <540C83DE.10505@collabora.co.uk> <540C8577.2070907@gmail.com> <20140908112112.GK26030@arm.com> <20140908134937.GK4015@sirena.org.uk> <540DB7B4.4060300@collabora.co.uk> <20140910111728.GG28488@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from mail-vc0-f169.google.com ([209.85.220.169]:49348 "EHLO mail-vc0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750882AbaIJQDx (ORCPT ); Wed, 10 Sep 2014 12:03:53 -0400 Received: by mail-vc0-f169.google.com with SMTP id ik5so2307711vcb.28 for ; Wed, 10 Sep 2014 09:03:53 -0700 (PDT) In-Reply-To: <20140910111728.GG28488@arm.com> Sender: linux-samsung-soc-owner@vger.kernel.org List-Id: linux-samsung-soc@vger.kernel.org To: Will Deacon Cc: Javier Martinez Canillas , Grant Likely , Mark Brown , Tomasz Figa , "kgene.kim@samsung.com" , "linux-samsung-soc@vger.kernel.org" , "olof@lixom.net" , "linux-arm-kernel@lists.infradead.org" , "rahul.sharma@samsung.com" , Stephen Warren , Jaehoon Chung Will, On Wed, Sep 10, 2014 at 4:17 AM, Will Deacon wrote: > On Mon, Sep 08, 2014 at 03:05:40PM +0100, Javier Martinez Canillas wrote: >> Hello Will, > > Hi Javier, > >> Since many folks don't agree that hacking different subsystems is the way >> forward I'll hold the patches and don't post them. The sunxi thread [0] >> already shows how different people have strong opposite positions on the >> correct approach to handle this. >> >> For now you can just disable the tps65090 PMIC support by not enabling the >> CONFIG_REGULATOR_TPS65090 kconfig symbol on your kernel config. That will give >> you exactly the same behavior that before tps65090 support was added to the >> Snow DT on commit b16be76 ("ARM: dts: add tps65090 power regulator for >> exynos5250-snow") which AFAIU was good enough for your workflow. > > Disabling the regulator support gives me my framebuffer back, thanks. Yay! Is this good enough to tide you over until DRM support lands? > I > then get stuck mounting my root filesystem over sd card because it's > reported as read-only. The following hack solved the issue, but I'm not > exactly sure where this regression has come from (whether this is a board > quirk or pinctrl is really misconfigured). This is a regression that was introduced by: 9795a84 mmc: dw_mmc: remove dw_mci_of_cd_gpio/wp_gpio() In "exynos5250-cros-common.dtsi" you can see that the "wp-gpios = <&gpc2 1 0>;" is still listed under the slot node. Nobody is looking there anymore. This is fixed in linux-next by: aaa25a5 ARM: dts: unuse the slot-node and deprecate the supports-highspeed for dw-mmc in exynos I'll let Kukjin decide what he wants to do about the regression in v3.17 (how to deal with conflicts, backporting, etc). -Doug From mboxrd@z Thu Jan 1 00:00:00 1970 From: dianders@chromium.org (Doug Anderson) Date: Wed, 10 Sep 2014 09:03:52 -0700 Subject: Unable to boot mainline on snow chromebook since 3.15 In-Reply-To: <20140910111728.GG28488@arm.com> References: <20140905122232.GP13515@arm.com> <540C202E.2060009@collabora.co.uk> <540C7F5B.6070307@gmail.com> <540C83DE.10505@collabora.co.uk> <540C8577.2070907@gmail.com> <20140908112112.GK26030@arm.com> <20140908134937.GK4015@sirena.org.uk> <540DB7B4.4060300@collabora.co.uk> <20140910111728.GG28488@arm.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Will, On Wed, Sep 10, 2014 at 4:17 AM, Will Deacon wrote: > On Mon, Sep 08, 2014 at 03:05:40PM +0100, Javier Martinez Canillas wrote: >> Hello Will, > > Hi Javier, > >> Since many folks don't agree that hacking different subsystems is the way >> forward I'll hold the patches and don't post them. The sunxi thread [0] >> already shows how different people have strong opposite positions on the >> correct approach to handle this. >> >> For now you can just disable the tps65090 PMIC support by not enabling the >> CONFIG_REGULATOR_TPS65090 kconfig symbol on your kernel config. That will give >> you exactly the same behavior that before tps65090 support was added to the >> Snow DT on commit b16be76 ("ARM: dts: add tps65090 power regulator for >> exynos5250-snow") which AFAIU was good enough for your workflow. > > Disabling the regulator support gives me my framebuffer back, thanks. Yay! Is this good enough to tide you over until DRM support lands? > I > then get stuck mounting my root filesystem over sd card because it's > reported as read-only. The following hack solved the issue, but I'm not > exactly sure where this regression has come from (whether this is a board > quirk or pinctrl is really misconfigured). This is a regression that was introduced by: 9795a84 mmc: dw_mmc: remove dw_mci_of_cd_gpio/wp_gpio() In "exynos5250-cros-common.dtsi" you can see that the "wp-gpios = <&gpc2 1 0>;" is still listed under the slot node. Nobody is looking there anymore. This is fixed in linux-next by: aaa25a5 ARM: dts: unuse the slot-node and deprecate the supports-highspeed for dw-mmc in exynos I'll let Kukjin decide what he wants to do about the regression in v3.17 (how to deal with conflicts, backporting, etc). -Doug