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 7AFF2C3DA61 for ; Thu, 18 Jul 2024 20:55:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Date:To:Cc:From:Subject: References:In-Reply-To:Content-Transfer-Encoding:MIME-Version:Content-Type: Message-ID:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=CsJA16iM/P2sj2H9XllwFQ+rN3XitbGqsX0IJx7VZ2I=; b=fS6tci0G5GalyK2ZIksCWW7Mi7 GVigLDcY55IRJ+jUaiKJK2YsuijZoFXDAe0l62YZQDn8jxlt1y6m8EFOyVKntdB6f561BdleTp4PP r31Xn3vClqBCwbjPZcuJa3UqXGk2+wx+Zi3P/YzHdxKPQ/OwqKn+CJSplw0fbKuVxwrNaxkJitiYp +DMbXYJdGmo5Ekv4OV0pbaPg8h5B/a4yqCEKOHRs2Gvqs6yzDjB1AQXvmWmLVJGD83O9ekQ6GDyke bgJ9HTezeIRVH/LFXno77CbtvXzsipNguyxVLCrjl+H1Bz445T3D4n9u0JZ/tmWMPywo3o2NoNpMm D/xb9h4w==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1sUYAA-00000000cHv-0gbG; Thu, 18 Jul 2024 20:55:42 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1sUY9n-00000000cDX-3abz for linux-arm-kernel@lists.infradead.org; Thu, 18 Jul 2024 20:55:21 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id 4A14161B9D; Thu, 18 Jul 2024 20:55:19 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D43D0C116B1; Thu, 18 Jul 2024 20:55:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1721336119; bh=CsJA16iM/P2sj2H9XllwFQ+rN3XitbGqsX0IJx7VZ2I=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=UZmLfjLL8nL1eINz5srFwr2rQ0CBPg/sw/YfhO4e9aVg7/BO0uNjI6CrJf6wslm8f J2dk3XGn/M7tlkRLF9+MuYIZ0D9PzcwQz2JoJe95uWc02glnvc8tfsjSxalOJu33QM NmxDj2Q42+fj4ClJhp+soGNa/99p6Cehn20SdcmHl90TWWUOO+g8SjZPc6aH/VA1hC WP/NXw7CnB/hTNd9nHCH+oYd9Y5umyHp6lvPekA9qSP7/1PlyJ2MqL+z9FpCkXz+XM vGpRK0isK16wXk0OPEIbUtotfwkLpnXi7pGZxRtm3w60yNqrrkDH6eewf+G+X9iGbh Tw5QSS9fD75XA== Message-ID: Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <20240712-gs101-non-essential-clocks-2-v4-0-310aee0de46e@linaro.org> References: <20240712-gs101-non-essential-clocks-2-v4-0-310aee0de46e@linaro.org> Subject: Re: [PATCH v4 0/2] gs101 oriole: UART clock fixes From: Stephen Boyd Cc: Tudor Ambarus , Will McVicker , kernel-team@android.com, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org, =?utf-8?q?Andr=C3=A9?= Draszik To: Alim Akhtar , =?utf-8?q?Andr=C3=A9?= Draszik , Chanwoo Choi , Krzysztof Kozlowski , Michael Turquette , Peter Griffin , Sam Protsenko , Sylwester Nawrocki , Tudor Ambarus Date: Thu, 18 Jul 2024 13:55:16 -0700 User-Agent: alot/0.10 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240718_135519_971680_2C4596A5 X-CRM114-Status: GOOD ( 10.88 ) 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: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Quoting Andr=C3=A9 Draszik (2024-07-12 10:09:42) > Hi, >=20 > This series fixes a long-standing issue in the gs101 clocking / uart > handling. >=20 > We can now disable clocks that had previously been marked critical, and > still get a working earlycon. >=20 > There is a preparatory patch, and then a patch to drop an incorrect clock > counting work-around. That 2nd patch is essentially the last remaining pa= tch > [1] with all review comments addressed, from the series [2] that was sent > earlier this year, see lore links below. Is there a binding update for the chosen node to have a clocks property?