From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932545AbbHDAmY (ORCPT ); Mon, 3 Aug 2015 20:42:24 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:44482 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755979AbbHDAmW (ORCPT ); Mon, 3 Aug 2015 20:42:22 -0400 Message-ID: <55C00A6B.2030508@codeaurora.org> Date: Mon, 03 Aug 2015 17:42:19 -0700 From: Stephen Boyd User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5 MIME-Version: 1.0 To: Robert Jarzmik CC: Michael Turquette , linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org, Ezequiel Garcia Subject: Re: [PATCH] clk: pxa: pxa3xx: fix CKEN register access References: <1438631907-27993-1-git-send-email-robert.jarzmik@free.fr> In-Reply-To: <1438631907-27993-1-git-send-email-robert.jarzmik@free.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08/03/2015 12:58 PM, Robert Jarzmik wrote: > Clocks 0 to 31 are on CKENA, and not CKENB. The clock register names > were inadequately inverted. As a consequence, all clock operations were > happening on CKENB, because almost all but 2 clocks are on CKENA. > > As the clocks were activated by the bootloader in the former tests, it > escaped the testing that the wrong clock gate was manipulated. The error > was revealed by changing the pxa3xx-and driver to a module, where tupon > unloading the wrong clock was disabled in CKENB. > > Signed-off-by: Robert Jarzmik > --- Did you want a fixes tag to send this back to stable? -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project