Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751686AbbBLS7f (ORCPT ); Thu, 12 Feb 2015 13:59:35 -0500 Received: from mout.kundenserver.de ([212.227.17.24]:65258 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751038AbbBLS7d (ORCPT ); Thu, 12 Feb 2015 13:59:33 -0500 Date: Thu, 12 Feb 2015 19:59:00 +0100 (CET) From: Stefan Wahren Reply-To: Stefan Wahren To: Fabio Estevam Cc: Sascha Hauer , linux-kernel , Shawn Guo , Mike Turquette , "linux-arm-kernel@lists.infradead.org" , Marek Vasut , Zhi Li Message-ID: <1378197784.470306.1423767540298.JavaMail.open-xchange@oxbaltgw01.schlund.de> In-Reply-To: References: <1422645610-3052-1-git-send-email-stefan.wahren@i2se.com> <54DA020C.6030703@i2se.com> <54DA0DE7.5050708@i2se.com> <462270270.419156.1423603473431.JavaMail.open-xchange@oxbaltgw02.schlund.de> <1705379122.406018.1423686677196.JavaMail.open-xchange@oxbaltgw01.schlund.de> Subject: Re: [PATCH V2 RESEND] clk: mxs: Fix invalid 32-bit access to frac registers MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Priority: 3 Importance: Medium X-Mailer: Open-Xchange Mailer v7.6.0-Rev36 X-Originating-Client: com.openexchange.ox.gui.dhtml X-Provags-ID: V03:K0:pcOtmIaeamUf5PvQ9yLzZ1cTi0Iz5Lpnad+C/dYcwdRSMvtdPjF fMt8Iy9ZuMujKefuuPsJ5RTSlxlNIsGMfT30j1cXL0EWAqVWnzczeiBg9SxQnl/T/Vsjf+8 +eM0oaCh7nRmUJKz1K1LIJvAsRP+c545BxkCOWu1XPYaxS4RrqelqSFsXjfFmaRAiKUS9OH A/TtOVQVkvOPszQQiG5fQ== X-UI-Out-Filterresults: notjunk:1; Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1195 Lines: 48 Hi Fabio, > Fabio Estevam hat am 11. Februar 2015 um 22:10 > geschrieben: > > > On Wed, Feb 11, 2015 at 6:31 PM, Stefan Wahren wrote: > > >> I always get 0x5e5b5513 with or without your patch. > > > > very strange. Do you have any idea why IO1_STABLE is permanent low? > > On my case it is always 1. i expected the same behavior on my hardware. Do you use u-boot as bootloader? > > > Can you confirm the behavior according to your flash issue? > > In my tests IO1_STABLE stays the same. This wasn't the intension of my second question. I wanted to know about the state of the SPI NOR flash detection process. Does it sucessed if you apply the patch, but revert the changes in clk_ref_set_rate() from clk-ref.c? > > > I think it would be the best to revert my patch. Sorry for the trouble. > > To be on the safe side, I agree. > > Could you please send a revert patch? Sure. > > Thanks > Stefan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/