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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9073FC433F5 for ; Fri, 20 May 2022 00:37:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344088AbiETAhz (ORCPT ); Thu, 19 May 2022 20:37:55 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60274 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1344076AbiETAhu (ORCPT ); Thu, 19 May 2022 20:37:50 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5EACF131281; Thu, 19 May 2022 17:37:49 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id E15B661011; Fri, 20 May 2022 00:37:48 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 42193C385B8; Fri, 20 May 2022 00:37:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1653007068; bh=A1S6mg9OBT6AKltZiiqdbCazkwAG61jCviwhpWl8/IQ=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=ueLxfJiMsabO3DZ1zq2+xp/0ZP75rmH59UF+XVeRNfAYoWFaiIXmfLLsGlSX16SA7 g+mK75hgrGJOty7Y4t9FmGx+zjcCZ8fQCo+y3wxiMW/nNfi/Yxdyfb7l6evmz54FML ZaUcJtpHEH1kYlGRBQ/LKOcWV1I+c3fc94QV2LnA34TZiOLtVimDcgO7VYx7k0l5VC BV2Zat1lkm+I+bvjo6pwRbUcBZoqm04Mjm10NQ4puIcyrZ2MMfNFl4hZP3+A7CBqs6 PlcsyeM3GRpoXZLCIqFmxpIZmbxTler+cGGZsTIs2EDgRL2fJvNwT5yjDa7T3JDxwV HuSM8FsjT7V1A== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <20220519071610.423372-6-wenst@chromium.org> References: <20220519071610.423372-1-wenst@chromium.org> <20220519071610.423372-6-wenst@chromium.org> Subject: Re: [PATCH v3 5/5] clk: mediatek: mt8173: Switch to clk_hw provider APIs From: Stephen Boyd Cc: Chen-Yu Tsai , Chun-Jie Chen , Miles Chen , Rex-BC Chen , Matthias Brugger , AngeloGioacchino Del Regno , linux-clk@vger.kernel.org, linux-mediatek@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org To: Chen-Yu Tsai , Michael Turquette Date: Thu, 19 May 2022 17:37:46 -0700 User-Agent: alot/0.10 Message-Id: <20220520003748.42193C385B8@smtp.kernel.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Chen-Yu Tsai (2022-05-19 00:16:10) > As part of the effort to improve the MediaTek clk drivers, the next step > is to switch from the old 'struct clk' clk prodivder APIs to the new > 'struct clk_hw' ones. >=20 > The MT8173 clk driver has one clk that is registered directly with the > clk provider APIs, instead of going through the MediaTek clk library. >=20 > Switch this instance to use the clk_hw provider API. >=20 > Signed-off-by: Chen-Yu Tsai > Reviewed-by: Miles Chen > Reviewed-by: AngeloGioacchino Del Regno > Tested-by: AngeloGioacchino Del Regno > Tested-by: Miles Chen > --- Applied to clk-next