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 E02C5C197BF for ; Thu, 27 Feb 2025 22:34:09 +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=vHU3dhEYskWbI85RowdDZTLXbFGbdRE7ty47cEABw8w=; b=Ty7UDH8e0zbBjr3HHgcSRV0Gmv chTynzoVf/L2WjnDI6KIXWhi/tkDU4kGVJIsYyMLRC4ejF5Hqfd8wC8Oph6c5Ydsd2t9jBjwtdUrs cq8EFc8hySWSw7qYB0LtC27kujDj74oxtwhA9XZ/hOqd4nf0PfbiIlWQxfqORXhaE3r72Vc5xx1TL lqotmHf1w/ljuug8Dg/8zUtRWp2AbFkBYlEG+tbTHzUaON9TO0FEnSfBPSM5GkA7J0QKclJfQtsld jm6uOP5sKNBovq4fMFULhvFWGyEfb5lGIUJvY0CDOTG2xnaYQWbRUyiVmHLQWLkXhvUoBEadXzxCU XgCzElkQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98 #2 (Red Hat Linux)) id 1tnmSG-000000092D8-01Yj; Thu, 27 Feb 2025 22:34:08 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.98 #2 (Red Hat Linux)) id 1tnmQd-0000000921W-0bZ1; Thu, 27 Feb 2025 22:32:32 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id 9A0195C1083; Thu, 27 Feb 2025 22:30:06 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 161D5C4CEDD; Thu, 27 Feb 2025 22:32:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1740695543; bh=k6e8ofzrBt9aHKWkZMG3dJtLmoBrQbP6qnALTS2lQdI=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=H/hNhaWAVRKKe3XZoM8aE+Jxa6aolkEyh1d6I4j1+iH+3E9HGKKLb9LdoFcJatXsL eDcqBLfAPj5Z6OWNkystoQ0BqtnVavVl7/masmi+87CnxdmkDfggsT3gIdmexq8jvX S19uIXKOBnZzJQTOya790x0e7iKBTnrYoIDuSYij2rUoGvPeuWX4KnBTtJdyi8Gzy9 bn5ZM9IVamjZ9/1wIPh6jCP8QlCm/I1Ppb//1UNOaIzJ4xPVHqXORoM1LIIP2tU5bJ N43UcaPi1aKd4kcATSus3TbDuEEmxi2YauzUK4xpZ1Hr1GOcDZHOXpIaTdZsNrw+zp cGktaOohkmQ3Q== Message-ID: <14dcbc0a6000aa43feda3681a3ad7548.sboyd@kernel.org> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <20250221075058.14180-2-friday.yang@mediatek.com> References: <20250221075058.14180-1-friday.yang@mediatek.com> <20250221075058.14180-2-friday.yang@mediatek.com> Subject: Re: [PATCH v4 1/2] dt-bindings: clock: mediatek: Add SMI LARBs reset for MT8188 From: Stephen Boyd Cc: Friday Yang , linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, Project_Global_Chrome_Upstream_Group@mediatek.com To: AngeloGioacchino Del Regno , Conor Dooley , Friday Yang , Garmin Chang , Krzysztof Kozlowski , Matthias Brugger , Michael Turquette , Rob Herring , Yong Wu Date: Thu, 27 Feb 2025 14:32:21 -0800 User-Agent: alot/0.12.dev1+gaa8c22fdeedb X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20250227_143227_224955_28BA2CCC X-CRM114-Status: UNSURE ( 8.34 ) X-CRM114-Notice: Please train this message. X-BeenThere: linux-mediatek@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-mediatek" Errors-To: linux-mediatek-bounces+linux-mediatek=archiver.kernel.org@lists.infradead.org Quoting Friday Yang (2025-02-20 23:50:53) > On the MediaTek platform, some SMI LARBs are directly connected to > the SMI Common, while others are connected to the SMI Sub-Common, > which in turn is connected to the SMI Common. The hardware block > diagram can be described as follows. >=20 > SMI-Common(Smart Multimedia Interface Common) > | > +----------------+------------------+ Applied to clk-next