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 DB432C433FE for ; Mon, 14 Nov 2022 13:04:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237758AbiKNNE1 (ORCPT ); Mon, 14 Nov 2022 08:04:27 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59062 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237750AbiKNNEY (ORCPT ); Mon, 14 Nov 2022 08:04:24 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6C50727DDA; Mon, 14 Nov 2022 05:04:24 -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 dfw.source.kernel.org (Postfix) with ESMTPS id 09A936117E; Mon, 14 Nov 2022 13:04:24 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5CA3BC433C1; Mon, 14 Nov 2022 13:04:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1668431063; bh=B8vw6qZp1pAdTc0xkFcFrwXOTcOIyVYrxMXbsKmlHSo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=iLyerZK1InQ8OyNqlEdaHZAmAzfxqIrN+EaSobimUtA3S5xPZA06hIatGXMCGJvAn 3hLPt6LNZayKDMC6tLu05P/PtJ1RH7LiTHN+IjNAk2e3/H24n2UBcQgdxmg0506egE hl7LQmKcsKsll7LActV8R++9ndv2PZvCPdrgvxbGv8H1SlAyIzP9nigHw4jzyNZTOh 4ryeEF/WSdauM1I8BMdZ62bZrgdTwmuHTrRCdt7dpZtXxF/6scgNP/PnXv8D6ylDFy t5EFVSIS28TUWR4ixRa38Ty6sGSW6Uo/NqH6jhmU9CLO123ZPTZDrjL75nxldHpD7I IKKWUNY5Ucaag== Received: from johan by xi.lan with local (Exim 4.94.2) (envelope-from ) id 1ouZ7v-0002Yl-Ig; Mon, 14 Nov 2022 14:03:51 +0100 Date: Mon, 14 Nov 2022 14:03:51 +0100 From: Johan Hovold To: Dmitry Baryshkov Cc: Johan Hovold , Vinod Koul , Andy Gross , Bjorn Andersson , Konrad Dybcio , Rob Herring , Krzysztof Kozlowski , linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 03/14] phy: qcom-qmp-combo: drop v4 reference-clock source Message-ID: References: <20221111092457.10546-1-johan+linaro@kernel.org> <20221111092457.10546-4-johan+linaro@kernel.org> <14f01c33-dada-b66a-f81a-74b9028de18b@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <14f01c33-dada-b66a-f81a-74b9028de18b@linaro.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Nov 12, 2022 at 02:43:38PM +0300, Dmitry Baryshkov wrote: > On 11/11/2022 12:24, Johan Hovold wrote: > > The source clock for the reference clock should not be described by the > > devicetree and instead this relationship should be modelled in the clock > > driver. > > Do we have a fix for the gcc driver? Bjorn is preparing one, but there's no need to wait for that to be merged in this case (we have a ton of references on CXO, we need to get the binding fixed in 6.2, and some other reasons which Bjorn may be able to share soon). Johan