Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp348118imm; Tue, 15 May 2018 02:36:05 -0700 (PDT) X-Google-Smtp-Source: AB8JxZoiDzCwTjNntJbqtY4A0iLHWCrO5Ye5p1UB/iFbqzGYxuvxzGCp2ACK9uoUA3h534HyzDKJ X-Received: by 2002:a63:a74a:: with SMTP id w10-v6mr11784582pgo.109.1526376965149; Tue, 15 May 2018 02:36:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526376965; cv=none; d=google.com; s=arc-20160816; b=eSZephyxqXoPMcjXJMz6uWX66Xbh3s+i4YW6HMPVJqzju2EBulYy7iYtqB3bKz/6Ou yAjyUYmeauuf/BUPFtOuhh9xo20wE7SmesAdDl9STCqDvy19IACQN2Evs9CxEjcsEFvc hA8Duw3C4uUD3VY8d3pYTLsBJ7hmHnXwIyKyd8ArAhQuQBi1Xw8ET3qGGpBLEO6i6Jwf SQ/IAxjJCVHC/VKB1vxdFjdpDNzDZemlHp6lDNlIE9WW43Kn1nJEuh+a3mu4aQbklYqt shrNNdHVGBSDEvE3GRVZjYDVnx8M7oYML9uDpYvob6X+3bKDFc5s9IwBosfSH26yyenj e4Vw== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:organization:from:references:to:subject:cc :arc-authentication-results; bh=3y25TCOBtdKxH6XZPhMyZ74wJHwqvCAVjjnycV/3AnI=; b=TumSSmF2l6qNasDelAeHp7rw8MbM2BGD9XkxuoMdA4QWSJ3r7+dC7YZtQ7UuTQcOPn F/pzW7kHWZNAQvR/XKTXPgra1ZTLwixe8nSwOXeyI4mS9NcY0HOXOnJaPsagZ/y3gI11 KD+R4Wv0mYN35SSNNZGBc6tuv25kGjfQ9nff+WToJCGkthqdEtZWA2+duJ/eKSATT47S YhTcd8qCSPOQtiu0pE23swjfnGyh+oSZ4GPKiuHFdcAlqMwTxjiI6TJjyRZV5VMvwHuc 4+yp8uUhpBv8k9XEdFm2cApc0a3IJ6/ngAo9x+VwW0MLUgznYTWp44apDBJnd50Jtbzf Gxlg== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p11-v6si10923039pfh.249.2018.05.15.02.35.51; Tue, 15 May 2018 02:36:05 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752498AbeEOJe2 (ORCPT + 99 others); Tue, 15 May 2018 05:34:28 -0400 Received: from foss.arm.com ([217.140.101.70]:57012 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752215AbeEOJe0 (ORCPT ); Tue, 15 May 2018 05:34:26 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id EE47D1529; Tue, 15 May 2018 02:34:25 -0700 (PDT) Received: from [10.1.210.28] (unknown [10.1.210.28]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id B97EA3F23C; Tue, 15 May 2018 02:34:19 -0700 (PDT) Cc: Sudeep Holla , Rajan Vaja , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "devicetree@vger.kernel.org" Subject: Re: [PATCH v6 04/11] firmware: xilinx: Add query data API To: Jolly Shah , "ard.biesheuvel@linaro.org" , "mingo@kernel.org" , "gregkh@linuxfoundation.org" , "matt@codeblueprint.co.uk" , "hkallweit1@gmail.com" , "keescook@chromium.org" , "dmitry.torokhov@gmail.com" , "mturquette@baylibre.com" , "sboyd@codeaurora.org" , "michal.simek@xilinx.com" , "robh+dt@kernel.org" , "mark.rutland@arm.com" , "linux-clk@vger.kernel.org" References: <1523389127-14243-1-git-send-email-jollys@xilinx.com> <1523389127-14243-5-git-send-email-jollys@xilinx.com> <85f8f8c5-a177-dad8-e095-a9dd1c513e8d@arm.com> From: Sudeep Holla Organization: ARM Message-ID: Date: Tue, 15 May 2018 10:34:18 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 14/05/18 20:16, Jolly Shah wrote: > HI Sudeep, > [...] >> >> Can you give more insight into this ? How will be this used ? How >> this aligns with data we get from DT ? I am just trying to >> understand how is this information split between this API and DT >> for example. >> > > This API is used to get clock information from firmware and register > clocks accordingly in driver. In our case, firmware maintains > database of all clocks available on chip. DT will provide information > for off chip reference clocks only. This is to avoid duplication of > clocks data in DT and firmware both as firmware anyways need clock > data to manage them. > I wanted to understand the difference with example. What kind of information you get from DT and what you get from firmware ? -- Regards, Sudeep