Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp8818810ybi; Tue, 23 Jul 2019 15:59:51 -0700 (PDT) X-Google-Smtp-Source: APXvYqz3HGVleOUZknQiHhXSrjzy+X8VHYnX7sGePs+xnzVFu2Y/pKWCv5sm+nsIsP9ZKGACTd/r X-Received: by 2002:a63:c008:: with SMTP id h8mr76019921pgg.427.1563922791045; Tue, 23 Jul 2019 15:59:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563922791; cv=none; d=google.com; s=arc-20160816; b=YRgaHxuSp34l0yLxdiwOeNW0a+pseLeEIhvpWrLz5/pHO9XDbICTD48Fb8wEtb35Xy a+F2ocTEFB7LZZznhMhoNnlU4UkO/k2sXBsi7+xTLPK5MC8e7vLnEaKzPKqDgIEuNkaE it5x614zggPX6pryZ8OfYTYSzN3XE5qLiPXXNF2FBpVaCnvZ7JjKU5Xt+7ekMsu8wGRL YSGlAAKxqYD7cM8w12cxNtrpZCGVkXv93hdh6jPONcO6Nhj9nvJya/wpPE1GNRX3xFu3 Xewk3/lIRgcSSsGidjE/lN9SY1yvlXBeTVItPrC3YrmnVXB5MJ2yQe/mfN6TGRewZLeU 8rPw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=QirIdSo16zP75dpk9RofCMNulZC8BT4dh+Fde+pw42M=; b=eSgNBmlKbt4iuka6AxSF/v3EpbjnL9mSsG645NhqMsQJnQq9V098CaBstEk+sid0EH 19G5d8zWuyIZmpuP32g2mAmlSqfTNMk4SJn+l7LriVN5MWDIepznUr6cLt82907rsJeF 9A83SvxsY5V59KIHmCzT5eMHCgmMxccKmgw8Vx9GDjAdQD3FjWHy4YsBLaF8YGTftx7K IA4qd1m6jmAS2nS0FKRiV7ySCtvdUsejvR3jvg1KzS66/LEoYSk3pWEhoI9INR0PVRxf LVV3XoVuL2+2bm4HKxBCLw7NLpnu67rvLGwRPDZp7QtQ1/MOrDEELzUlqycde/YQa1n7 ntxg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=ts2zKnry; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m71si11738007pjb.26.2019.07.23.15.59.35; Tue, 23 Jul 2019 15:59:51 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=ts2zKnry; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387707AbfGWMGr (ORCPT + 99 others); Tue, 23 Jul 2019 08:06:47 -0400 Received: from mail.kernel.org ([198.145.29.99]:39472 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727789AbfGWMGr (ORCPT ); Tue, 23 Jul 2019 08:06:47 -0400 Received: from mail-lf1-f51.google.com (mail-lf1-f51.google.com [209.85.167.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 9D7942238E; Tue, 23 Jul 2019 12:06:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1563883606; bh=DKrbsHStPDRY+4kxJ4/+/qAdj1UDVR+qwitPFb6G9XQ=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=ts2zKnryAHCcWuV+jQCtZ1fXUaMYtk/rse8t/JdjssvTDla0eLrQ7l7Fy7A91meAb 4dq5/+DeF78UIQcOHR3q6qljcYC+4rwJc2IGbOzlxegYgRIX8xVXiAozEtcohEjzSQ NgbJODdAIYTnBIHU6w/0RraMEYcpUUjG5MLfKfAY= Received: by mail-lf1-f51.google.com with SMTP id u10so29137682lfm.12; Tue, 23 Jul 2019 05:06:45 -0700 (PDT) X-Gm-Message-State: APjAAAVbVfIZ0hJpoM11wp+xUFDO6jte7b6wvxP//so07W6yI3b3LePa W7ZgxVpX8sLzxA1KJppeia6ej+kioGvRjjEoxWQ= X-Received: by 2002:a19:f007:: with SMTP id p7mr34881578lfc.24.1563883603819; Tue, 23 Jul 2019 05:06:43 -0700 (PDT) MIME-Version: 1.0 References: <20190715124417.4787-1-l.luba@partner.samsung.com> <20190715124417.4787-38-l.luba@partner.samsung.com> <2fe2e840-f4b2-773b-7d92-4ffb8502d4e6@partner.samsung.com> <518c26ca-4254-056c-d6d0-ae1b4b63709c@partner.samsung.com> <7ad899c5-347d-546e-a2e9-d96f0203210c@partner.samsung.com> In-Reply-To: <7ad899c5-347d-546e-a2e9-d96f0203210c@partner.samsung.com> From: Krzysztof Kozlowski Date: Tue, 23 Jul 2019 14:06:32 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v1 37/50] ARM: dts: exynos: change parent and rate of bus_fsys in Exynos5422 To: Lukasz Luba Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, "linux-samsung-soc@vger.kernel.org" , linux-clk@vger.kernel.org, mturquette@baylibre.com, sboyd@kernel.org, =?UTF-8?B?QmFydMWCb21pZWogxbtvxYJuaWVya2lld2ljeg==?= , kgene@kernel.org, mark.rutland@arm.com, robh+dt@kernel.org, Chanwoo Choi , kyungmin.park@samsung.com, Andrzej Hajda , Marek Szyprowski , s.nawrocki@samsung.com, myungjoo.ham@samsung.com Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 17 Jul 2019 at 14:56, Lukasz Luba wrote: > > > On 7/17/19 1:11 PM, Krzysztof Kozlowski wrote: > > On Wed, 17 Jul 2019 at 13:06, Lukasz Luba wrote: > >> > >> > >> > >> On 7/17/19 12:45 PM, Krzysztof Kozlowski wrote: > >>> On Wed, 17 Jul 2019 at 12:39, Lukasz Luba wrote: > >>>>>> > >>>>>> &bus_fsys { > >>>>>> devfreq = <&bus_wcore>; > >>>>>> + assigned-clocks = <&clock CLK_MOUT_ACLK200_FSYS>, > >>>>>> + <&clock CLK_DOUT_ACLK200_FSYS>, > >>>>>> + <&clock CLK_FOUT_DPLL>; > >>>>>> + assigned-clock-parents = <&clock CLK_MOUT_SCLK_DPLL>; > >>>>>> + assigned-clock-rates = <0>, <240000000>,<1200000000>; > >>>>> > >>>>> Here and in all other patches: > >>>>> I am not entirely sure that this should be here. It looks like > >>>>> property of the SoC. Do we expect that buses will be configured to > >>>>> different clock rates between different boards? > This is the board file for Exynos5420/5422/5800 which enables buses. > Thus, I have change them here. Patch 49/50 adds these buses to > Exynos5800 (Peach Pi). In Exynos5420 there is no clock tree for > bus_isp266. The parents for different devices could be also different. > It is because i.e. in 5420 there is 2 bit in the WCORE 1st mux while in > 5422 there is 3 bits (6 parents possible). > That's why I have picked exynos5422-odroid-core.dtsi to reference > the bus devices and pinned them into proper parent and changed rate. > When you check patch 49/50 for 5800 not all the parents are the same. > > (1) I could create a dedicated files like: exynos5422-bus.dtsi, > exynos5420-bus.dtsi, exynos5800-bus.dtsi which would include some > base file with the basic &bus_X and set the right parent, rate. > Then these files would be included into proper board file like: > exynos5800-peach-pi.dts. > Is this something that you would like to see? I see now. Are there any differences in all these properties between Peach Pi and Odroids? Both of them are using exynos5800.dtsi so that could be a place for all clock assignments. Best regards, Krzysztof