Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp265774ybl; Wed, 4 Dec 2019 02:22:39 -0800 (PST) X-Google-Smtp-Source: APXvYqzc73QnDyzNfIBVkmVxu3LYMT9EdLmxNURf/703zX/YW3nkhV0//KdYfQv8bZaUMFEXVOEE X-Received: by 2002:aca:4106:: with SMTP id o6mr1911177oia.173.1575454959220; Wed, 04 Dec 2019 02:22:39 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575454959; cv=none; d=google.com; s=arc-20160816; b=kRyqz9tbZmtHNkGUV0dh7lmhW2ALqh18x+nxl/7mpey9VxKR/89km0qj+3YQVz9MHz eCcJJ8XC6NELKhYb2dhXxNtUxlEXHd5DTIvhMOpCcSqUTnQIlRNiyK9DQVv+1akVy6wF xSJJ9niOcEQKHBZJqle0iE7fjpO1HmvzeQCBovne1kbctjESUo4vMtkz3u5z3yzScJhX UX6wuYjWluhlrlnxakHk3yNgObNd+Pc5fWXDwDbariYNAGqJPnIR99Q6hQ7cjtt3BSO6 opLmwAmm9A9mqKYaDEIDU7flpLcTeg/rvjf5p83M7Z/pClQm/w2tTP1cmIY1vi1N/or3 Uhag== 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:from:references:cc:to:subject:dkim-signature; bh=lXkM2TiakZNWEer24NnBU2s4hqmdaq894N1amWO3xwU=; b=V6i1NyaZfPPNZCjP+CB83rPIF9Ld4aw9AchRpIBbo6/6Gc7dkSIdLkb90CSMbVXIYj 2uIrGGXO1GY5+GkHXRyoiURcprDTSE4EoLBwa6QKn3ssDd6KozSBH5apGKHZOK8Y53Bl vOIY+4ym7g4I68TzMowOFRy6HSGLK34UHZcbi0RY+2KCrFt16fYjM8BAenNtlHhpEV/7 GMabhF1BHvyu/Of9wlpKR9EuA2dsrdj+TYTSa75XZgiFKyxtH2IFUVk6qQ/7Ljph4I9l wZLBWa1+KhOww5O5+VSF3N3OpTu0zEbIBRENBL8ScTLRNpwg+gJW2x/CEkOR1aJk2EoV 6pqw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@kapsi.fi header.s=20161220 header.b=rlYVOhaH; 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 p12si2848176otk.86.2019.12.04.02.22.26; Wed, 04 Dec 2019 02:22:39 -0800 (PST) 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=fail header.i=@kapsi.fi header.s=20161220 header.b=rlYVOhaH; 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 S1727543AbfLDKVn (ORCPT + 99 others); Wed, 4 Dec 2019 05:21:43 -0500 Received: from mail.kapsi.fi ([91.232.154.25]:38167 "EHLO mail.kapsi.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726899AbfLDKVn (ORCPT ); Wed, 4 Dec 2019 05:21:43 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kapsi.fi; s=20161220; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=lXkM2TiakZNWEer24NnBU2s4hqmdaq894N1amWO3xwU=; b=rlYVOhaHmSwAOLiBcI9DwOvenr gX8xA9bN6W8vbD13Q9Q3z4CiCKVYK8IqzXgRiflrhDM0CBRJRVZQKfkYaMLkCRgQh2FIvLqDFAL0Y 6KKx5oZKzKuQDR8G5YdcU3LAJWI6CjHI2fbpfKaDoPh+6z7B3ulwVIVpCzXul1u1RCjiaN6RkHt0T OP+svFIIBKcgAggm+wW19khbF6hdcQyC25UOynrd7rVPZA4UcGNRBstE1bMeibgDRJ5gsjljRCOsN TXxKFMtheZpM18pQeBZ+9hf7xOpG2dRM+THKOMQ7t9Y3UOXZqetqM52D+ojk+JL8P8NoDF6NODW2a Cci6wq/Q==; Received: from [193.209.96.43] (helo=[10.21.26.179]) by mail.kapsi.fi with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from ) id 1icRmk-0001Ce-NM; Wed, 04 Dec 2019 12:21:30 +0200 Subject: Re: [TEGRA194_CPUFREQ Patch 1/3] firmware: tegra: adding function to get BPMP data To: Viresh Kumar Cc: Thierry Reding , Sumit Gupta , rjw@rjwysocki.net, catalin.marinas@arm.com, will@kernel.org, jonathanh@nvidia.com, talho@nvidia.com, linux-pm@vger.kernel.org, linux-tegra@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, bbasu@nvidia.com, mperttunen@nvidia.com References: <1575394348-17649-1-git-send-email-sumitg@nvidia.com> <20191203174229.GA1721849@ulmo> <9404232d-84ce-a117-89dd-f2d8de80993e@kapsi.fi> <20191204091703.d32to5omdm3eynon@vireshk-i7> From: Mikko Perttunen Message-ID: Date: Wed, 4 Dec 2019 12:21:30 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.1 MIME-Version: 1.0 In-Reply-To: <20191204091703.d32to5omdm3eynon@vireshk-i7> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 193.209.96.43 X-SA-Exim-Mail-From: cyndis@kapsi.fi X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Ah, it seems I was mistaken here. Thanks for the information. Thanks, Mikko On 4.12.2019 11.17, Viresh Kumar wrote: > On 04-12-19, 10:45, Mikko Perttunen wrote: >> Now, my original patchset (which this series is based on) did add >> nvidia,bpmp properties on the CPU DT nodes itself and query BPMP based on >> that. A change is still required for that since tegra_bpmp_get() currently >> takes a 'struct device *' which we don't have for a CPU DT node. > > I may be missing the context, but the CPUs always have a struct device > * for them, which we get via a call to get_cpu_device(cpu), isn't ? >