Received: by 2002:a25:ef43:0:0:0:0:0 with SMTP id w3csp1674487ybm; Sat, 30 May 2020 17:05:56 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyi84/+JWB8iY6449dUdMs+0NvhW65mwjt6HHKoxLxLo3/LtoSXCeqgGdsD+hOhPBBKRFLC X-Received: by 2002:a05:6402:155a:: with SMTP id p26mr14387999edx.376.1590883556772; Sat, 30 May 2020 17:05:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590883556; cv=none; d=google.com; s=arc-20160816; b=q1YK3gKnDiGuS/Bq9/05VTpoNZinGdYZxJZ+MIqxxdOFJArJd6pOO5MaFkzOnEzgcV kFF3cOcx8DfxMc9cmjT+0YkzhiQPP6jYCiUZMPJwiUBprOWUX3L8Mi9e0+EWhcdKIVl1 VITNiZ61BBO4JUqXCsH4IO+JyavGeqLT5Y5NOE2iBU1V+s7Wy0LecqTj4iTjQyNpYXzt N0MW9kbiPZkvfqm7LkRtV7mwu8U1as4VuiWPg7y2IfWLiVoLk1KioEi0W4q8OYs3t0Wn 0AA35znSJvCZLkTtd5GnQ27hI3XaI9fN8JqcJIDl83Z+0AzcO5DyrZLxO/jyOXTwcSdF 978Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=a9J75p5lTlGlwHDQ/bXXCoO9brHC/gyCZzqto7tv/S0=; b=dqT/97Wxa+O+3tvPGwPhAgRRgtdLcZNbhaVa2RnYcaXu1/FG+s/ybilf9Ezd/aT1NO hvkkdF//DmX1lMG084yqKOxdOaWAbHQQpC2ewpWChCQ2tUT/Gtcw5a8EXl+RkrpknQIt raGazNM9p+5yOD9gXZQb/5x56XIJUnrGCk5fqJs4CsX6qakOi6MM5K4dn19FOBBP1AAW fKt4bRmazmcDxS+4SozLMZyVJwLBqRUa1HAF9+c+/VMaHTXlpBZLrCOX5VTPf2AUjZpR AT7tkUUbpAOlYqkgNCvCy6CfLBoBz5wXh9I8y+TuVxWS03Elyf0E323jTs9aqNy/eqPS Goig== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=LAZ2ml8d; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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. [23.128.96.18]) by mx.google.com with ESMTP id n16si970356edt.7.2020.05.30.17.05.34; Sat, 30 May 2020 17:05:56 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=LAZ2ml8d; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 S1729559AbgEaABj (ORCPT + 99 others); Sat, 30 May 2020 20:01:39 -0400 Received: from mail.kernel.org ([198.145.29.99]:47686 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729385AbgEaABj (ORCPT ); Sat, 30 May 2020 20:01:39 -0400 Received: from mail-lj1-f180.google.com (mail-lj1-f180.google.com [209.85.208.180]) (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 3ABCB207DF; Sun, 31 May 2020 00:01:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1590883298; bh=2p4SBOzIcxqldDQV+EgA8g75sZR4n3jmr6ytOgA1hPs=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=LAZ2ml8d4tllly6yUKcA/bFgxj/GgNzOm0gXCJCNiuDci5YuQ5r4pMox+T1OJYV72 5PjXNv1Y5hW8w24ZrhtxIMQ3p8jB3cTQoOBZT4n+D+hRCfoeplyK67Lrya9geraBXN ab34i9F2dcOBC5NYC1slzpGFwKQ7Cuys08WeKMAk= Received: by mail-lj1-f180.google.com with SMTP id z18so3687865lji.12; Sat, 30 May 2020 17:01:38 -0700 (PDT) X-Gm-Message-State: AOAM530GAHJBTAO4A3QsHV+IQFbkbAc+8d4aCdwUxV165OamenzaMnBE 7FMztQZtLLsjG0ltit6fQpbcvJ/iDmCPmPUt2qE= X-Received: by 2002:a2e:b5b0:: with SMTP id f16mr7700307ljn.100.1590883296477; Sat, 30 May 2020 17:01:36 -0700 (PDT) MIME-Version: 1.0 References: <20200529163200.18031-1-s.nawrocki@samsung.com> <20200529163200.18031-2-s.nawrocki@samsung.com> In-Reply-To: <20200529163200.18031-2-s.nawrocki@samsung.com> From: Chanwoo Choi Date: Sun, 31 May 2020 09:01:00 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [RFC PATCH v5 1/6] dt-bindings: exynos-bus: Add documentation for interconnect properties To: Sylwester Nawrocki Cc: Georgi Djakov , Chanwoo Choi , Krzysztof Kozlowski , =?UTF-8?B?QXJ0dXIgxZp3aWdvxYQ=?= , MyungJoo Ham , inki.dae@samsung.com, Seung-Woo Kim , Bartlomiej Zolnierkiewicz , Marek Szyprowski , linux-kernel , linux-samsung-soc , dri-devel , linux-arm-kernel Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Sylwester, On Sat, May 30, 2020 at 1:32 AM Sylwester Nawrocki wrote: > > Add documentation for new optional properties in the exynos bus nodes: > samsung,interconnect-parent, #interconnect-cells. > These properties allow to specify the SoC interconnect structure which > then allows the interconnect consumer devices to request specific > bandwidth requirements. > > Signed-off-by: Artur =C5=9Awigo=C5=84 > Signed-off-by: Sylwester Nawrocki > --- > Changes for v5: > - exynos,interconnect-parent-node renamed to samsung,interconnect-parent > --- > Documentation/devicetree/bindings/devfreq/exynos-bus.txt | 15 ++++++++++= +++-- > 1 file changed, 13 insertions(+), 2 deletions(-) > > diff --git a/Documentation/devicetree/bindings/devfreq/exynos-bus.txt b/D= ocumentation/devicetree/bindings/devfreq/exynos-bus.txt > index e71f752..e0d2daa 100644 > --- a/Documentation/devicetree/bindings/devfreq/exynos-bus.txt > +++ b/Documentation/devicetree/bindings/devfreq/exynos-bus.txt > @@ -51,6 +51,11 @@ Optional properties only for parent bus device: > - exynos,saturation-ratio: the percentage value which is used to calibra= te > the performance count against total cycle count. > > +Optional properties for interconnect functionality (QoS frequency constr= aints): > +- samsung,interconnect-parent: phandle to the parent interconnect node; = for > + passive devices should point to same node as the exynos,parent-bus pro= perty. > +- #interconnect-cells: should be 0 > + > Detailed correlation between sub-blocks and power line according to Exyn= os SoC: > - In case of Exynos3250, there are two power line as following: > VDD_MIF |--- DMC > @@ -185,8 +190,9 @@ Example1: > ---------------------------------------------------------- > > Example2 : > - The bus of DMC (Dynamic Memory Controller) block in exynos3250.dt= si > - is listed below: > + The bus of DMC (Dynamic Memory Controller) block in exynos3250.dt= si is > + listed below. An interconnect path "bus_lcd0 -- bus_leftbus -- bu= s_dmc" > + is defined for demonstration purposes. > > bus_dmc: bus_dmc { > compatible =3D "samsung,exynos-bus"; > @@ -376,12 +382,15 @@ Example2 : > &bus_dmc { > devfreq-events =3D <&ppmu_dmc0_3>, <&ppmu_dmc1_3>; > vdd-supply =3D <&buck1_reg>; /* VDD_MIF */ > + #interconnect-cells =3D <0>; > status =3D "okay"; > }; > > &bus_leftbus { > devfreq-events =3D <&ppmu_leftbus_3>, <&ppmu_rightbus_3>; > vdd-supply =3D <&buck3_reg>; > + samsung,interconnect-parent =3D <&bus_dmc>; > + #interconnect-cells =3D <0>; > status =3D "okay"; > }; > > @@ -392,6 +401,8 @@ Example2 : > > &bus_lcd0 { > devfreq =3D <&bus_leftbus>; > + samsung,interconnect-parent =3D <&bus_leftbus>; > + #interconnect-cells =3D <0>; > status =3D "okay"; > }; > > -- > 2.7.4 > If you add the usage example like the mixer device of patch5 to this dt-binding document, I think it is very beneficial and more helpful for user of exynos-bus/exynos-generic-icc. Acked-by: Chanwoo Choi -- Best Regards, Chanwoo Choi Samsung Electronics