Received: by 2002:a05:7412:b112:b0:f9:3106:f1c0 with SMTP id az18csp80142rdb; Sun, 17 Dec 2023 22:33:00 -0800 (PST) X-Google-Smtp-Source: AGHT+IHhFEKMxT5IxNVOos8Jo9Y4F3SZuNLON1VxUr0tapenC+Lw5cM7zXvzZKvb571ooffU+hWf X-Received: by 2002:a05:6358:6f93:b0:170:f1ab:9612 with SMTP id s19-20020a0563586f9300b00170f1ab9612mr9773759rwn.65.1702881180565; Sun, 17 Dec 2023 22:33:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1702881180; cv=none; d=google.com; s=arc-20160816; b=VcLii52MfGFFbJq1UdR6fWY906v9Dh8PrUzH0x+9xAQo9O/uriv3vKv/CEqjwbIHlQ lNs7SRXXLSP3nEfr1lYw2KrfuDmW3llRN7aspHamjDdtNw66b9ETKEYsdyf9kXuNKTOC RdxOxX8jUpvuwrsaOQtuh+Je82BKvCr4UGSY1B/tGF052lHcZNqgSxMCWLO2hWgknMOE igSQKm48xWvfyXk4MVIiV9msrQZbE/my2cIDeqUZZVUgnAoxUgyHOWsKEDN7avbZmtZR I8EH2olzaNENN5u2HJwSOLwv9Gc3YiBB6gwctRfzOyPCy9+PZFsXlV4T0S2fKUqq5qza cpkw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:date:to:cc:from:subject:references:in-reply-to :content-transfer-encoding:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:message-id:dkim-signature; bh=P+FpMjf2mykyFNclosXhXZPRX1VsrQekgOEK3L9QqY0=; fh=Khgzqsu/OqwTzMV/e6XTS6JgOIilNqm9IVGNdjYk17A=; b=VQnm55QU9zFdsOIW0fQn8ZmPZiNhmO02gclPgnvw0MSWj5c6Jg63B9HoLzjdVi3xrb nPSsLZrl9ZhuB2farzHwIh0xR7KYOt1kKakoGN/2bwP2oit0r1kLg32U26Yh6zWtdqJM ZXz2A9AMvmnuYxwV+yh9nnzbuEQG+xIh32+xkycXcxrp0ymUThv3zUF8ymnYkWkt1Dyt RR8RvBAIWIcK7GA06YBf6j0uYNMujsieA8MUL1vnlTGuxw++ybkZZdVMLHiS8R/I9Dob 8r4Heb4Ve2SiZZXUzkBPmR8IBsl+3mRVckYk6MQaGgLCiC1PTO6JTItig0WXagj0Tp1J tqmQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=jLFpJnfe; spf=pass (google.com: domain of linux-kernel+bounces-3046-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-3046-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from sv.mirrors.kernel.org (sv.mirrors.kernel.org. [2604:1380:45e3:2400::1]) by mx.google.com with ESMTPS id a14-20020a631a4e000000b005cd7818afb9si4055819pgm.698.2023.12.17.22.33.00 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 17 Dec 2023 22:33:00 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-3046-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=jLFpJnfe; spf=pass (google.com: domain of linux-kernel+bounces-3046-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-3046-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sv.mirrors.kernel.org (Postfix) with ESMTPS id 360CE28296E for ; Mon, 18 Dec 2023 06:33:00 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 367476FD1; Mon, 18 Dec 2023 06:32:53 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="jLFpJnfe" X-Original-To: linux-kernel@vger.kernel.org Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 58A456FA5; Mon, 18 Dec 2023 06:32:51 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id AF350C433C7; Mon, 18 Dec 2023 06:32:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1702881171; bh=P+FpMjf2mykyFNclosXhXZPRX1VsrQekgOEK3L9QqY0=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=jLFpJnfeluZNkdrcEvIArVja7yW1RA5z4DELGrRNmRUmceW90bJr5VXBUPF1jkZ9a fLEhfoCfr6mhZmhRagX12JOoQv8PVxRVj+W81QOwIw+LysPDoa+RSzUjYoNGTAsBev PeXPGAfzmsj754Pcel6qPSJx1DRiDHxufST2zv/iIJSmwSMazER26DXrWl/yd2iD5V S6pWel0GmDomrzVn0s99VcakbmLtriKgyPMssIAdkwA/fAYmMndvRqBWuR32qxkkCW B481tkcDwToqwBBy2f3dE2PPCpNrV+0uC7+O5LJkZqJ538btMyWJZUN2uEEY6VHWDz e34sRTdSfmHCg== Message-ID: Content-Type: text/plain; charset="utf-8" Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <20231124-alvin-clk-si5351-no-pll-reset-v6-3-69b82311cb90@bang-olufsen.dk> References: <20231124-alvin-clk-si5351-no-pll-reset-v6-0-69b82311cb90@bang-olufsen.dk> <20231124-alvin-clk-si5351-no-pll-reset-v6-3-69b82311cb90@bang-olufsen.dk> Subject: Re: [PATCH v6 3/3] clk: si5351: allow PLLs to be adjusted without reset From: Stephen Boyd Cc: Sebastian Hesselbarth , Rabeeh Khoury , Jacob Siverskog , Sergej Sawazki , linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org To: Alvin =?utf-8?q?=C5=A0ipraga?= , Alvin =?utf-8?q?=C5=A0ipraga?= , Conor Dooley , Krzysztof Kozlowski , Michael Turquette , Rob Herring Date: Sun, 17 Dec 2023 22:32:49 -0800 User-Agent: alot/0.10 Quoting Alvin =C5=A0ipraga (2023-11-24 05:17:44) > From: Alvin =C5=A0ipraga >=20 > Introduce a new PLL reset mode flag which controls whether or not to > reset a PLL after adjusting its rate. The mode can be configured through > platform data or device tree. >=20 > Since commit 6dc669a22c77 ("clk: si5351: Add PLL soft reset"), the > driver unconditionally resets a PLL whenever its rate is adjusted. > The rationale was that a PLL reset was required to get three outputs > working at the same time. Before this change, the driver never reset the > PLLs. >=20 > Commit b26ff127c52c ("clk: si5351: Apply PLL soft reset before enabling > the outputs") subsequently introduced an option to reset the PLL when > enabling a clock output that sourced it. Here, the rationale was that > this is required to get a deterministic phase relationship between > multiple output clocks. >=20 > This clearly shows that it is useful to reset the PLLs in applications > where multiple clock outputs are used. However, the Si5351 also allows > for glitch-free rate adjustment of its PLLs if one avoids resetting the > PLL. In our audio application where a single Si5351 clock output is used > to supply a runtime adjustable bit clock, this unconditional PLL reset > behaviour introduces unwanted glitches in the clock output. >=20 > It would appear that the problem being solved in the former commit > may be solved by using the optional device tree property introduced in > the latter commit, obviating the need for an unconditional PLL reset > after rate adjustment. But it's not OK to break the default behaviour of > the driver, and it cannot be assumed that all device trees are using the > property introduced in the latter commit. Hence, the new behaviour is > made opt-in. >=20 > Cc: Sebastian Hesselbarth > Cc: Rabeeh Khoury > Cc: Jacob Siverskog > Cc: Sergej Sawazki > Signed-off-by: Alvin =C5=A0ipraga > Acked-by: Sebastian Hesselbarth > --- Applied to clk-next