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 X-Spam-Level: X-Spam-Status: No, score=-4.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 39443C10DCE for ; Fri, 13 Mar 2020 01:11:44 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0AAC4206EB for ; Fri, 13 Mar 2020 01:11:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1584061904; bh=IVJisS2GXrsxrK9O9HPwtS0E/pajmPEpiboizL+NXBk=; h=In-Reply-To:References:Subject:From:Cc:To:Date:List-ID:From; b=L2SUcm37hVpLnIvDaSKrynvDut98O16QwDsySSSap+m+n3cfMQcJrHwLk65RCYagE Y43GrRnr5jlyQy+YJDiJOL4zIqNGbWzaZOoEvcY7lo4QvUgdothBRU9rVpdHgqqKd6 UQndEv3SLumbHkYnL30WfZyg8i4Wisx9EDsESljM= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727357AbgCMBLn (ORCPT ); Thu, 12 Mar 2020 21:11:43 -0400 Received: from mail.kernel.org ([198.145.29.99]:35198 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726838AbgCMBLk (ORCPT ); Thu, 12 Mar 2020 21:11:40 -0400 Received: from kernel.org (unknown [104.132.0.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 134B9206EB; Fri, 13 Mar 2020 01:11:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1584061900; bh=IVJisS2GXrsxrK9O9HPwtS0E/pajmPEpiboizL+NXBk=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=Yyd3MsF7QPgOVGGT/yNCY9vzU56TCnh7wEzl/aelJHdYI/NE8WNuOdQmAyh5sPB3O 6YFk69qvOs6vVxKqaggWyf2G1033dkXPkrtP2JXyGV93b5q9BuQqOKJJ4gebKVUJ7j 3UlUQwnLGlCtjLY6+JejUCpMGE2V/Yo/2VhMaj+Q= Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: References: Subject: Re: [PATCH 15/89] clk: bcm: rpi: Create a data structure for the clocks From: Stephen Boyd Cc: dri-devel@lists.freedesktop.org, linux-rpi-kernel@lists.infradead.org, bcm-kernel-feedback-list@broadcom.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Dave Stevenson , Tim Gover , Phil Elwell , Maxime Ripard , Michael Turquette , linux-clk@vger.kernel.org To: Eric Anholt , Maxime Ripard , Nicolas Saenz Julienne Date: Thu, 12 Mar 2020 18:11:39 -0700 Message-ID: <158406189924.149997.7523053804639833250@swboyd.mtv.corp.google.com> User-Agent: alot/0.9 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Maxime Ripard (2020-02-24 01:06:17) > So far the driver has really only been providing a single clock, and stor= ed > both the data associated to that clock in particular with the data > associated to the "controller". >=20 > Since we will change that in the future, let's decouple the clock data fr= om > the provider data. >=20 > Cc: Michael Turquette > Cc: Stephen Boyd > Cc: linux-clk@vger.kernel.org > Signed-off-by: Maxime Ripard > --- Reviewed-by: Stephen Boyd