From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S969565AbeCSSYK convert rfc822-to-8bit (ORCPT ); Mon, 19 Mar 2018 14:24:10 -0400 Received: from mail.kernel.org ([198.145.29.99]:58298 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1031528AbeCSSX5 (ORCPT ); Mon, 19 Mar 2018 14:23:57 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 53D1A21720 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=sboyd@kernel.org Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8BIT To: Jolly Shah , Rob Herring From: Stephen Boyd In-Reply-To: Cc: "mark.rutland@arm.com" , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "mturquette@baylibre.com" , "sboyd@codeaurora.org" , "michal.simek@xilinx.com" , Shubhrajyoti Datta , Rajan Vaja , "linux-clk@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" References: <1519856861-31384-1-git-send-email-jollys@xilinx.com> <1519856861-31384-3-git-send-email-jollys@xilinx.com> <20180306014549.6t3ae5adzc3cpi5v@rob-hp-laptop> Message-ID: <152148383577.242365.14896728603053993045@swboyd.mtv.corp.google.com> User-Agent: alot/0.7 Subject: RE: [PATCH 2/3] dt-bindings: clock: Add bindings for ZynqMP clock driver Date: Mon, 19 Mar 2018 11:23:55 -0700 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Jolly Shah (2018-03-13 11:39:13) > Hi Rob, > > > > What is the interface to the "platform management controller"? Because you > > have no registers, I'm guessing a firmware interface? If so, then just define the > > firmware node as a clock provider. > > Yes it is firmware interface. Along with clocks, firmware interface also controls power and pinctrl operations as major. > I am not sure if I understand you correctly. Do you suggest to register clocks through Firmware driver or just use firmware DT node as clock provider and clock driver DT node can reference clocks from FW node to register same? I would suggest making the firmware driver register the clks and act as the clk provider. Not sure what Rob wants. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Boyd Subject: RE: [PATCH 2/3] dt-bindings: clock: Add bindings for ZynqMP clock driver Date: Mon, 19 Mar 2018 11:23:55 -0700 Message-ID: <152148383577.242365.14896728603053993045@swboyd.mtv.corp.google.com> References: <1519856861-31384-1-git-send-email-jollys@xilinx.com> <1519856861-31384-3-git-send-email-jollys@xilinx.com> <20180306014549.6t3ae5adzc3cpi5v@rob-hp-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Jolly Shah , Rob Herring Cc: "mark.rutland@arm.com" , "devicetree@vger.kernel.org" , "linux-clk@vger.kernel.org" , "mturquette@baylibre.com" , "sboyd@codeaurora.org" , "linux-kernel@vger.kernel.org" , "michal.simek@xilinx.com" , Rajan Vaja , Shubhrajyoti Datta , "linux-arm-kernel@lists.infradead.org" List-Id: devicetree@vger.kernel.org Quoting Jolly Shah (2018-03-13 11:39:13) > Hi Rob, > > > > What is the interface to the "platform management controller"? Because you > > have no registers, I'm guessing a firmware interface? If so, then just define the > > firmware node as a clock provider. > > Yes it is firmware interface. Along with clocks, firmware interface also controls power and pinctrl operations as major. > I am not sure if I understand you correctly. Do you suggest to register clocks through Firmware driver or just use firmware DT node as clock provider and clock driver DT node can reference clocks from FW node to register same? I would suggest making the firmware driver register the clks and act as the clk provider. Not sure what Rob wants. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 To: Jolly Shah , Rob Herring From: Stephen Boyd In-Reply-To: Cc: "mark.rutland@arm.com" , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "mturquette@baylibre.com" , "sboyd@codeaurora.org" , "michal.simek@xilinx.com" , Shubhrajyoti Datta , Rajan Vaja , "linux-clk@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" References: <1519856861-31384-1-git-send-email-jollys@xilinx.com> <1519856861-31384-3-git-send-email-jollys@xilinx.com> <20180306014549.6t3ae5adzc3cpi5v@rob-hp-laptop> Message-ID: <152148383577.242365.14896728603053993045@swboyd.mtv.corp.google.com> Subject: RE: [PATCH 2/3] dt-bindings: clock: Add bindings for ZynqMP clock driver Date: Mon, 19 Mar 2018 11:23:55 -0700 List-ID: Quoting Jolly Shah (2018-03-13 11:39:13) > Hi Rob, > > = > > What is the interface to the "platform management controller"? Because = you > > have no registers, I'm guessing a firmware interface? If so, then just = define the > > firmware node as a clock provider. > = > Yes it is firmware interface. Along with clocks, firmware interface also = controls power and pinctrl operations as major. > I am not sure if I understand you correctly. Do you suggest to register c= locks through Firmware driver or just use firmware DT node as clock provide= r and clock driver DT node can reference clocks from FW node to register sa= me? I would suggest making the firmware driver register the clks and act as the clk provider. Not sure what Rob wants. From mboxrd@z Thu Jan 1 00:00:00 1970 From: sboyd@kernel.org (Stephen Boyd) Date: Mon, 19 Mar 2018 11:23:55 -0700 Subject: [PATCH 2/3] dt-bindings: clock: Add bindings for ZynqMP clock driver In-Reply-To: References: <1519856861-31384-1-git-send-email-jollys@xilinx.com> <1519856861-31384-3-git-send-email-jollys@xilinx.com> <20180306014549.6t3ae5adzc3cpi5v@rob-hp-laptop> Message-ID: <152148383577.242365.14896728603053993045@swboyd.mtv.corp.google.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Quoting Jolly Shah (2018-03-13 11:39:13) > Hi Rob, > > > > What is the interface to the "platform management controller"? Because you > > have no registers, I'm guessing a firmware interface? If so, then just define the > > firmware node as a clock provider. > > Yes it is firmware interface. Along with clocks, firmware interface also controls power and pinctrl operations as major. > I am not sure if I understand you correctly. Do you suggest to register clocks through Firmware driver or just use firmware DT node as clock provider and clock driver DT node can reference clocks from FW node to register same? I would suggest making the firmware driver register the clks and act as the clk provider. Not sure what Rob wants.