From mboxrd@z Thu Jan 1 00:00:00 1970 From: srinivas.kandagatla@linaro.org (Srinivas Kandagatla) Date: Wed, 24 Sep 2014 16:30:24 +0100 Subject: [PATCH v2] soc: qcom: do not disable the iface clock in probe In-Reply-To: <7hbnq5m4a5.fsf@deeprootsystems.com> References: <1411500054-13600-1-git-send-email-srinivas.kandagatla@linaro.org> <7hbnq5m4a5.fsf@deeprootsystems.com> Message-ID: <5422E390.9060802@linaro.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 24/09/14 16:22, Kevin Hilman wrote: > Srinivas Kandagatla writes: > >> since commit 31964ffebbb9 ("tty: serial: msm: Remove direct access to GSBI")' >> serial hangs if earlyprintk are enabled. >> >> This hang is noticed only when the GSBI driver is probed and all the >> earlyprintks before gsbi probe are seen on the console. >> The reason why it hangs is because GSBI driver disables hclk in its >> probe function without realizing that the serial IP might be in use by >> a bootconsole. As gsbi driver disables the clock in probe the >> bootconsole locks up. > >> Turning off hclk's could be dangerous if there are system components >> like earlyprintk using the hclk. > > This seems rather fragile. Isn't the right fix for these other > components to use the clk api to ensure the clock does not get enabled? Here we are depending on the bootloader to setup the clocks. Am not sure if we can really use clk apis at that early stage of bootstrap. --srini > > Kevin >