From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3B7A1C43331 for ; Fri, 6 Sep 2019 17:20:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0B01F20842 for ; Fri, 6 Sep 2019 17:20:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1567790447; bh=MqN/EtBkVnxG8eZiColGzmDCTwXUPyPh5+LpIVe0YG4=; h=In-Reply-To:References:To:From:Cc:Subject:Date:List-ID:From; b=Rn/HOrEpgyCBkhACN1PPVFJg6fHhBhEv4iBLWil67ZDPBVdgFvDNHn0ME8rEe+4QY GXrucTPx7qaaw7N2WNkeLOMppbWMzS3QK9sWs58QvgPf0sFObiA2b9CevRS4Ukew6J 4EjumjhUPUKbfwSl4UXd2e9wB7Btk+N9zlAPq9TM= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2406051AbfIFRUq (ORCPT ); Fri, 6 Sep 2019 13:20:46 -0400 Received: from mail.kernel.org ([198.145.29.99]:35152 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729928AbfIFRUp (ORCPT ); Fri, 6 Sep 2019 13:20:45 -0400 Received: from kernel.org (unknown [104.132.0.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id B99FB20838; Fri, 6 Sep 2019 17:20:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1567790444; bh=MqN/EtBkVnxG8eZiColGzmDCTwXUPyPh5+LpIVe0YG4=; h=In-Reply-To:References:To:From:Cc:Subject:Date:From; b=CYozECqVpRrFJH2xvk6dZ4mN6OY4KecJUOzK1vGdSGMnbIKxRA8qh/Kc+LdHjTEx5 PUZXjE89eK7y1b+ifK4UXKqZC6DrG2/yezn1PYX7R3f5S+sw3IiAvYj3lL3oy5GVCa FqYmivqaXH8/EfZQDELvYwg6vU0Xnas34hkqips0= Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <1566936978-28519-1-git-send-email-peng.fan@nxp.com> References: <1566936978-28519-1-git-send-email-peng.fan@nxp.com> To: "festevam@gmail.com" , "mturquette@baylibre.com" , "s.hauer@pengutronix.de" , "shawnguo@kernel.org" , Aisheng Dong , Peng Fan From: Stephen Boyd Cc: "kernel@pengutronix.de" , dl-linux-imx , Anson Huang , Jacky Bai , Abel Vesa , "linux-clk@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , Peng Fan Subject: Re: [PATCH] clk: imx: lpcg: write twice when writing lpcg regs User-Agent: alot/0.8.1 Date: Fri, 06 Sep 2019 10:20:43 -0700 Message-Id: <20190906172044.B99FB20838@mail.kernel.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Peng Fan (2019-08-27 01:17:50) > From: Peng Fan >=20 > There is hardware issue that: > The output clock the LPCG cell will not turn back on as expected, > even though a read of the IPG registers in the LPCG indicates that > the clock should be enabled. >=20 > The software workaround is to write twice to enable the LPCG clock > output. >=20 > Signed-off-by: Peng Fan Does this need a Fixes tag?