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 9FD6BC4332F for ; Fri, 25 Feb 2022 00:49:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236081AbiBYAuR (ORCPT ); Thu, 24 Feb 2022 19:50:17 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38600 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235626AbiBYAuR (ORCPT ); Thu, 24 Feb 2022 19:50:17 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 81EC42C0335; Thu, 24 Feb 2022 16:49:46 -0800 (PST) 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 ams.source.kernel.org (Postfix) with ESMTPS id 24EF1B82A7C; Fri, 25 Feb 2022 00:49:45 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id AA8EDC340EF; Fri, 25 Feb 2022 00:49:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1645750183; bh=/gjfyXft3KepKTQGQRWa22PpJYtYND6chFxYq2s6++s=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=Osej/u5wUspxVqADMrgvgoC5FXMvyHDkHZW4fBJ1kgFe1+EKJFtljIZYJhQnFMHnB 6B2AMVFTv+WbbL5IV+/Bgq70y+YevqLtpWLNfmmB+SADRrSDkwIJw7suwxnQrAz074 6k5eD73lafLOJkdIj1k2/mEbD4dIlFFyxc1u8Lq77F1Q5ezIjtZ6UlQeB8G5RUrk/r 6CgFL6QrUg7V4vpBLk4jkbxv9mZ/MLvXSCbcOWR3Nd/ESbF2KYIhOh0dYb87wHpya3 KaI4/FGdO4SeKfmLCGq+owJAwN2gm/SxIfHiAaGa+TRXkg0NU9Fd9fskn42WAl04Gk 9FKPxFUgjkfMA== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: References: <20220216225304.53911-1-djrscally@gmail.com> <20220216225304.53911-4-djrscally@gmail.com> Subject: Re: [PATCH 3/6] platform/x86: int3472: Support multiple clock consumers From: Stephen Boyd Cc: rafael@kernel.org, lenb@kernel.org, markgross@kernel.org, robert.moore@intel.com, linux-acpi@vger.kernel.org, linux-clk@vger.kernel.org, platform-driver-x86@vger.kernel.org To: Daniel Scally , Hans de Goede , Michael Turquette Date: Thu, 24 Feb 2022 16:49:41 -0800 User-Agent: alot/0.10 Message-Id: <20220225004943.AA8EDC340EF@smtp.kernel.org> Precedence: bulk List-ID: X-Mailing-List: linux-acpi@vger.kernel.org Quoting Hans de Goede (2022-02-21 01:59:09) > Hi, >=20 > On 2/16/22 23:53, Daniel Scally wrote: > > At present, the int3472-tps68470 only supports a single clock consumer = when > > passing platform data to the clock driver. In some devices multiple > > sensors depend on the clock provided by a single TPS68470 and so all > > need to be able to acquire the clock. Support passing multiple > > consumers as platform data. > >=20 > > Signed-off-by: Daniel Scally >=20 > Thanks, patch looks good to me: >=20 > Reviewed-by: Hans de Goede >=20 > Michael, I plan to merge this entire series through the platform-drivers-= x86 git > tree, may I have your ack for merging the clk bits from this ? >=20 With the type fix Reviewed-by: Stephen Boyd Acked-by: Stephen Boyd