All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sumit Gupta <sumitg@nvidia.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	<treding@nvidia.com>, <dmitry.osipenko@collabora.com>,
	<viresh.kumar@linaro.org>, <rafael@kernel.org>,
	<jonathanh@nvidia.com>, <robh+dt@kernel.org>,
	<lpieralisi@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
	<linux-pm@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-pci@vger.kernel.org>, <mmaddireddy@nvidia.com>,
	<kw@linux.com>, <bhelgaas@google.com>, <vidyas@nvidia.com>,
	<sanjayc@nvidia.com>, <ksitaraman@nvidia.com>, <ishah@nvidia.com>,
	<bbasu@nvidia.com>, Sumit Gupta <sumitg@nvidia.com>
Subject: Re: [Patch v4 02/10] arm64: tegra: add bpmp ref in tegra234-mc node
Date: Tue, 28 Mar 2023 18:11:56 +0530	[thread overview]
Message-ID: <db682990-573f-e827-7342-ca8cda0b4067@nvidia.com> (raw)
In-Reply-To: <af455119-7178-bed8-4099-ee50c7b6134b@linaro.org>



On 28/03/23 12:51, Krzysztof Kozlowski wrote:
> External email: Use caution opening links or attachments
> 
> 
> On 27/03/2023 18:14, Sumit Gupta wrote:
>> Add the "nvidia,bpmp" property within the "memory-controller" node
>> to reference BPMP node. This is needed by the MC driver to pass
>> the client info to the BPMP-FW when memory interconnect support is
>> available.
>>
>> Signed-off-by: Sumit Gupta <sumitg@nvidia.com>
> 
> DTS goes to the end of patchset. If you put it here to fix
> bisectability, then your patchset is already broken.
> 
> Best regards,
> Krzysztof
> 

Ok, will move the 'Patch 2 & 7' to the end of patch set (i.e. Patch 9 & 10)
   [Patch v4 02/10] arm64: tegra: add bpmp ref in tegra234-mc node
   [Patch v4 07/10] arm64: tegra: Add cpu OPP tables and interconnects 
property

Thank you,
Sumit Gupta


  reply	other threads:[~2023-03-28 12:42 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27 16:14 [Patch v4 00/10] Tegra234 Memory interconnect support Sumit Gupta
2023-03-27 16:14 ` [Patch v4 01/10] dt-bindings: memory: tegra: add bpmp ref in tegra234-mc node Sumit Gupta
2023-03-28  7:23   ` Krzysztof Kozlowski
2023-03-28 10:48     ` Thierry Reding
2023-03-28 11:22       ` Krzysztof Kozlowski
2023-03-28 12:48         ` Thierry Reding
2023-03-29 17:12           ` Sumit Gupta
2023-04-02 10:47             ` Krzysztof Kozlowski
2023-04-04 11:44               ` Thierry Reding
2023-03-28 10:42   ` Thierry Reding
2023-03-27 16:14 ` [Patch v4 02/10] arm64: " Sumit Gupta
2023-03-28  7:21   ` Krzysztof Kozlowski
2023-03-28 12:41     ` Sumit Gupta [this message]
2023-03-27 16:14 ` [Patch v4 03/10] memory: tegra: add interconnect support for DRAM scaling in Tegra234 Sumit Gupta
2023-03-28  7:31   ` Krzysztof Kozlowski
2023-03-28 11:05     ` Thierry Reding
2023-03-28 12:30       ` Sumit Gupta
2023-03-28 12:34     ` Sumit Gupta
2023-03-27 16:14 ` [Patch v4 04/10] memory: tegra: add mc clients for Tegra234 Sumit Gupta
2023-03-27 16:14 ` [Patch v4 05/10] memory: tegra: add software mc clients in Tegra234 Sumit Gupta
2023-03-27 16:14 ` [Patch v4 06/10] dt-bindings: tegra: add icc ids for dummy MC clients Sumit Gupta
2023-03-27 16:14 ` [Patch v4 07/10] arm64: tegra: Add cpu OPP tables and interconnects property Sumit Gupta
2023-03-27 16:14 ` [Patch v4 08/10] cpufreq: tegra194: add OPP support and set bandwidth Sumit Gupta
2023-03-27 16:14 ` [Patch v4 09/10] memory: tegra: make cpu cluster bw request a multiple of mc channels Sumit Gupta
2023-03-27 16:14 ` [Patch v4 10/10] PCI: tegra194: add interconnect support in Tegra234 Sumit Gupta
2023-03-28 17:53   ` Bjorn Helgaas
2023-03-29  9:14     ` Sumit Gupta
2023-03-29 16:59       ` Bjorn Helgaas
2023-03-29 17:58         ` Sumit Gupta
2023-03-29 19:17           ` Bjorn Helgaas
2023-03-30  8:00             ` Sumit Gupta

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=db682990-573f-e827-7342-ca8cda0b4067@nvidia.com \
    --to=sumitg@nvidia.com \
    --cc=bbasu@nvidia.com \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.osipenko@collabora.com \
    --cc=ishah@nvidia.com \
    --cc=jonathanh@nvidia.com \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=ksitaraman@nvidia.com \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mmaddireddy@nvidia.com \
    --cc=rafael@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sanjayc@nvidia.com \
    --cc=treding@nvidia.com \
    --cc=vidyas@nvidia.com \
    --cc=viresh.kumar@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.