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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 7256FC54E49 for ; Mon, 26 Feb 2024 10:55:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=41lFTmaZtfK7DVT1iY4DLbGH6aEJkivFK6WPZYPpjEM=; b=YLDeqZXQP9tpui oVQzA/MeahmooXRz2O57N3Wz/Tokp6yQ2+L9dM4DhV031FNY8hIL5RXCBx+sxGsV+nYCgPYSfqDbV ODH7qjIs00bEUoUtJUNmOxNoSeRbz90w0gVtOQZxWQxoILKVoqJM1i4uDrLch9mzY3O54qd0ePkHC h/kw6sfpLsVN37bqc0xKHlt37WMnV6Ms7s8iW5dNNTB8WkNMPRsmbhPUYvHPWZI5iqCbCaUk2UAae 8tlV05y1Ju9raNooMPiMLmp12mCmzwDFGqUX7TrnDyA43b/JtZva9Y7ACzw81xgQz56/odDUnaDlP pQnlSQGbB3dut0uu2lag==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1reYdK-00000000DXV-3RUE; Mon, 26 Feb 2024 10:54:54 +0000 Received: from mail11.truemail.it ([2001:4b7e:0:8::81]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1reYdF-00000000DRw-40ch for linux-arm-kernel@lists.infradead.org; Mon, 26 Feb 2024 10:54:52 +0000 Received: from francesco-nb (93-49-2-63.ip317.fastwebnet.it [93.49.2.63]) by mail11.truemail.it (Postfix) with ESMTPA id 213CF1FA1B; Mon, 26 Feb 2024 11:54:40 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dolcini.it; s=default; t=1708944880; bh=q3t+9DN4ngdFtdrD/shw1T/iqqp+imBFrdQtbCvoMSk=; h=From:To:Subject; b=wlTuwqC0H1O/peAc9lJ9z0cg3MH3qww3bF5PPCHKa/gsvJoHlJh6BeX6Yh1F/8JWN Gqy2TGXS7OigX0xx5ZjAZh8CUmLp1FRsV5HfS9g7FbYxQ4yUsdWO9eX58ccXUwu54G vhbbUewQ4cICT9YHsOUnSUZynO5pMgPkz2PNolQ9DoeEm6GnMZuIK4n2Nh58Gif3eK r3FSAz42CvOntdJVqU7Lb1htcNWEula22vbsU/EsgAF+PC611jRL6WQ1aQ4IlXOTLv yAtSDYjdIQ8/XTQ1WVQFDO8bTlnK99k8jVsYcHBGTYaDfHeGcmjWIxV7ixiWCNMMc9 oHvte4g8izPFg== Date: Mon, 26 Feb 2024 11:54:35 +0100 From: Francesco Dolcini To: Udit Kumar Cc: nm@ti.com, kristo@kernel.org, ssantosh@kernel.org, chandru@ti.com, rishabh@ti.com, kamlesh@ti.com, francesco@dolcini.it, vigneshr@ti.com, mturquette@baylibre.com, sboyd@kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org Subject: Re: [PATCH v4] clk: keystone: sci-clk: Adding support for non contiguous clocks Message-ID: <20240226105435.GA11908@francesco-nb> References: <20240213082640.457316-1-u-kumar1@ti.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20240213082640.457316-1-u-kumar1@ti.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240226_025451_061479_7A4EC15F X-CRM114-Status: UNSURE ( 9.59 ) X-CRM114-Notice: Please train this message. X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Feb 13, 2024 at 01:56:40PM +0530, Udit Kumar wrote: > Most of clocks and their parents are defined in contiguous range, > But in few cases, there is gap in clock numbers[0]. > Driver assumes clocks to be in contiguous range, and add their clock > ids incrementally. > > New firmware started returning error while calling get_freq and is_on > API for non-available clock ids. Is this the kind of errors I should expect in such situation? ti-sci-clk 44043000.system-controller:clock-controller: recalc-rate failed for dev=13, clk=7, ret=-19 If this is the case, I feel like this patch should be back-ported to stable kernels. Any malfunction because of these errors or just some noise in the logs? Francesco _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel