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 A3A0CC433E0 for ; Thu, 25 Jun 2020 00:46:07 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 7C6EA20857 for ; Thu, 25 Jun 2020 00:46:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1593045967; bh=OUxXBFoghacMANUGTE7ZG9CeSufUCQvHlJDK1Yo+EJA=; h=In-Reply-To:References:Subject:From:Cc:To:Date:List-ID:From; b=GXwuXAe6wLQZUbTXBYu/YBbeH6JOXgc9fUq90gcF+hvRaZvDan9NnleYR/7vZyB0B Qn/QD9ik2ahIhJgCbAV5Er9weTUJ1fgNbkEDG6wO2xB5OaMziHpwWmMms729QEbmEx GJ17srShU2IuQ9Y+RZr+Q7u8saSGnqNLwdCFdbxw= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388543AbgFYAqH (ORCPT ); Wed, 24 Jun 2020 20:46:07 -0400 Received: from mail.kernel.org ([198.145.29.99]:60080 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729175AbgFYAqG (ORCPT ); Wed, 24 Jun 2020 20:46:06 -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 E5833207E8; Thu, 25 Jun 2020 00:46:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1593045966; bh=OUxXBFoghacMANUGTE7ZG9CeSufUCQvHlJDK1Yo+EJA=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=oYFQ3lMGqoNbaCLc5QTotVZFrL4vtTg0ehMZnp+/sFuuD5eSkXAARlcQi3Thz7g1d xdsYyPdWaR5TFE5jilGiMEDhlXK/wL3pXRJtRAKL3tI2D6qbazQ1Db8dsNKWbCv/jj skm92CRyFl2C4lBiWJlmkFr7GKS4PbuatBO5I2Mo= Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: References: Subject: Re: [PATCH v5 25/27] clk: bcm2835: Allow custom CCF flags for the PLLs From: Stephen Boyd Cc: 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 , Mike Turquette , linux-clk@vger.kernel.org, Philipp Zabel , Maxime Ripard To: Maxime Ripard , Nicolas Saenz Julienne Date: Wed, 24 Jun 2020 17:46:05 -0700 Message-ID: <159304596533.62212.5983688856832285825@swboyd.mtv.corp.google.com> User-Agent: alot/0.9 Sender: linux-clk-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-clk@vger.kernel.org Quoting Maxime Ripard (2020-06-15 01:41:05) > While some clock types allow for each clock to specify its own custom > flags, the PLLs can't. We will need this for the PLLB, so let's add it. >=20 > Acked-by: Nicolas Saenz Julienne > Tested-by: Nicolas Saenz Julienne > Signed-off-by: Maxime Ripard > --- Applied to clk-next