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=-8.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS autolearn=ham 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 DA864C43603 for ; Wed, 4 Dec 2019 17:32:03 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id AE201207DD for ; Wed, 4 Dec 2019 17:32:02 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="EsImF3cA" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org AE201207DD Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=sntech.de Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Date:Subject:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=w8hVNpSUlSYKYnGCFhj7MMg5Ga+aqXfwUli+zGEGRvw=; b=EsImF3cA0ZYo37 Nek8EEoT6HlwSNLhnsMHfEu3LyhxHkLr2jJT8RXQzE3cPSNNizWtvf8Qefuf1hkLvnmPgRJSKEHsc w9e/qVWYgx3Ipu3GXJg61lYWtAlSkQg86JY23hCoIhpcp7gwIhDkxwmln2JjRMWe6pXfnV2qnV+Cw oW34XPjwJB310jfrxg7wdkzHfcsqOkTsTLK34q968ZXwZi5viXDncspvKX2oi7thEccZMamzlcMOD k4qdvS/5sAqwJMnajqe4f92OSLslUCja5kwdlUy+obXMCZLaMbnMzXNoCZOVBhPfIryRSirCAgCyx 3id80oNwPz1XEyDzBygw==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1icYVN-0000XY-SK; Wed, 04 Dec 2019 17:32:01 +0000 Received: from gloria.sntech.de ([185.11.138.130]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1icYVK-0000WJ-M0; Wed, 04 Dec 2019 17:32:00 +0000 Received: from ip5f5a6266.dynamic.kabel-deutschland.de ([95.90.98.102] helo=diego.localnet) by gloria.sntech.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1icYV9-0000uM-6T; Wed, 04 Dec 2019 18:31:47 +0100 From: Heiko =?ISO-8859-1?Q?St=FCbner?= To: Miquel Raynal Subject: Re: [PATCH] arm64: dts: rockchip: Move xin32k fixed-clock out of PX30 DTSI Date: Wed, 04 Dec 2019 18:31:46 +0100 Message-ID: <2665233.YyXs6BPQ7y@diego> In-Reply-To: <20191204171537.14163-1-miquel.raynal@bootlin.com> References: <20191204171537.14163-1-miquel.raynal@bootlin.com> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20191204_093158_872303_1CBF64AD X-CRM114-Status: GOOD ( 13.39 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Mark Rutland , linux-rockchip@lists.infradead.org, Rob Herring , linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi Miquel, Am Mittwoch, 4. Dezember 2019, 18:15:37 CET schrieb Miquel Raynal: > This clock has nothing to do in the PX30 DTSI as it is supposed to be > an input of the SoC. Moving it to the EVB DTS (only board file using > this DTSI) makes more sense. Also, when this clock is not a fixed > clock and comes from eg. a PMIC the situation can be described cleanly > in the device tree (avoids having to delete the fixed-clock node > first). > > This clock is not mandatory to boot so it should not break existing > users. > > Signed-off-by: Miquel Raynal Sorry foo being the bearer of bad news again, but that issue got already fixed by: arm64: dts: rockchip: remove static xin32k from px30 https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git/commit/?h=v5.5-armsoc/dts64&id=00519137f7d4fc19ff27f3d3f4fc45b5b222ae82 arm64: dts: rockchip: fix the px30-evb power tree https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git/commit/?h=v5.5-armsoc/dts64&id=915b6a8b54a6d436885a458867e59fb20fc6356d On most/all Rockchip the xin32k clock is actually provided by the boards pmic - the rk809 in this case. Heiko _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel