devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Aaron Kling <webgeek1234@gmail.com>
Cc: Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
	Thierry Reding <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	MyungJoo Ham <myungjoo.ham@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Dmitry Osipenko <digetx@gmail.com>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-tegra@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v3 5/9] memory: tegra210: Support interconnect framework
Date: Mon, 15 Sep 2025 09:24:25 +0200	[thread overview]
Message-ID: <bf72ff58-f149-4f99-9d74-abd4ec314774@kernel.org> (raw)
In-Reply-To: <CALHNRZ9G_OA0+quNP=NwnwX43iaV1JWxjJFM0Aoect9Y8jGjWw@mail.gmail.com>

On 15/09/2025 08:08, Aaron Kling wrote:
> On Wed, Sep 10, 2025 at 5:07 AM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>>> +    icc_provider_init(&emc->icc_provider);
>>>> +
>>>> +    /* create External Memory Controller node */
>>>> +    node = icc_node_create(TEGRA_ICC_EMC);
>>>> +    if (IS_ERR(node)) {
>>>> +            err = PTR_ERR(node);
>>>> +            goto err_msg;
>>>
>>> return dev_err_probe
>>
>>
>> I will send patches to fix existing code. I also found some more issues
>> which I would like to implement here.
>>
>> I apologize for coming with all this at v3. I should point out things a
>> bit earlier, although how this patchset was organized also affected review.
>>
>> Anyway my comments are mostly non-critical things, so v3 is late to
>> bring these, I understand. That's on me. I appreciate your work and
>> please do not get discouraged with my comments.
> 
> I understand and that's fine. Get it done right the first time so it
> doesn't have to be redone later. I will try to get a new revision out
> this week once I cycle back around to the relevant devices here.
> 

Just FYI, I closed my tree already so I will take anything after merge
window earliest.

Best regards,
Krzysztof

  reply	other threads:[~2025-09-15  7:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-06 20:16 [PATCH v3 0/9] Support Tegra210 actmon for dynamic EMC scaling Aaron Kling via B4 Relay
2025-09-06 20:16 ` [PATCH v3 1/9] dt-bindings: devfreq: tegra30-actmon: Add Tegra124 fallback for Tegra210 Aaron Kling via B4 Relay
2025-09-06 20:16 ` [PATCH v3 2/9] dt-bindings: memory: tegra210: emc: Document OPP table and interconnect Aaron Kling via B4 Relay
2025-09-10  9:41   ` (subset) " Krzysztof Kozlowski
2025-09-06 20:16 ` [PATCH v3 3/9] dt-bindings: memory: tegra210: Add memory client IDs Aaron Kling via B4 Relay
2025-09-10  9:41   ` (subset) " Krzysztof Kozlowski
2025-09-06 20:16 ` [PATCH v3 4/9] memory: tegra210: Use bindings for client ids Aaron Kling via B4 Relay
2025-09-10  9:41   ` (subset) " Krzysztof Kozlowski
2025-09-06 20:16 ` [PATCH v3 5/9] memory: tegra210: Support interconnect framework Aaron Kling via B4 Relay
2025-09-10  9:39   ` Krzysztof Kozlowski
2025-09-10 10:06     ` Krzysztof Kozlowski
2025-09-15  6:08       ` Aaron Kling
2025-09-15  7:24         ` Krzysztof Kozlowski [this message]
2025-09-06 20:16 ` [PATCH v3 6/9] soc: tegra: fuse: speedo-tegra210: Add soc speedo 2 Aaron Kling via B4 Relay
2025-09-06 20:16 ` [PATCH v3 7/9] arm64: tegra: tegra210: Add actmon Aaron Kling via B4 Relay
2025-09-06 20:16 ` [PATCH v3 8/9] arm64: tegra: Add interconnect properties to Tegra210 device-tree Aaron Kling via B4 Relay
2025-09-06 20:16 ` [PATCH v3 9/9] arm64: tegra: Add OPP tables on Tegra210 Aaron Kling via B4 Relay

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=bf72ff58-f149-4f99-9d74-abd4ec314774@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=cw00.choi@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=digetx@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=krzk+dt@kernel.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=robh@kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=webgeek1234@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).