From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Herring Subject: Re: [PATCH v3 1/6] dt-bindings: opp: Introduce opp-peak-KBps and opp-avg-KBps bindings Date: Mon, 22 Jul 2019 17:35:01 -0600 Message-ID: <20190722233501.GA19594@bogus> References: <20190703011020.151615-1-saravanak@google.com> <20190703011020.151615-2-saravanak@google.com> <98b2e315-e8da-80ad-1ef8-e6b222c1c6fe@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Saravana Kannan Cc: Sibi Sankar , Georgi Djakov , Mark Rutland , Viresh Kumar , Nishanth Menon , Stephen Boyd , "Rafael J. Wysocki" , Vincent Guittot , "Sweeney, Sean" , daidavid1@codeaurora.org, Rajendra Nayak , Bjorn Andersson , Evan Green , Android Kernel Team , Linux PM , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , LKML List-Id: devicetree@vger.kernel.org On Tue, Jul 16, 2019 at 11:58:08AM -0700, Saravana Kannan wrote: > On Tue, Jul 16, 2019 at 10:25 AM Sibi Sankar wrote: > > > > Hey Saravana, > > > > https://patchwork.kernel.org/patch/10850815/ > > There was already a discussion ^^ on how bandwidth bindings were to be > > named. > > Yes, I'm aware of that series. That series is trying to define a BW > mapping for an existing frequency OPP table. This patch is NOT about > adding a mapping to an existing table. This patch is about adding the > notion of BW OPP tables where BW is the "key" instead of "frequency". > > So let's not mixed up these two series. Maybe different reasons, but in the end we'd end up with 2 bandwidth properties. We need to sort out how they'd overlap/coexist. The same comment in that series about defining a standard unit suffix also applies to this one. Rob