From: Dmitry Osipenko <digetx@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH v2 0/6] NVIDIA Tegra memory improvements
Date: Fri, 2 Apr 2021 17:47:52 +0300 [thread overview]
Message-ID: <25acdacd-ace5-f680-cace-f8d8119589ea@gmail.com> (raw)
In-Reply-To: <b9bc9700-d3c1-54b4-72a3-ace4c3b9e9ed@canonical.com>
01.04.2021 20:54, Krzysztof Kozlowski пишет:
> On 31/03/2021 01:04, Dmitry Osipenko wrote:
>> Hi,
>>
>> This series replaces the raw voltage regulator with a power domain that
>> will be managing SoC core voltage. The core power domain patches are still
>> under review, but it's clear at this point that this is the way we will
>> implement the DVFS support.
>>
>> The remaining Tegra20 memory bindings are converted to schema. I also
>> made a small improvement to the memory drivers.
>>
>> Changelog:
>>
>> v2: - Fixed typos in the converted schemas.
>> - Corrected reg entry of tegra20-mc-gart schema to use fixed number of items.
>> - Made power-domain to use maxItems instead of $ref phandle in schemas.
>>
>> Dmitry Osipenko (6):
>> dt-bindings: memory: tegra20: emc: Replace core regulator with power
>> domain
>> dt-bindings: memory: tegra30: emc: Replace core regulator with power
>> domain
>> dt-bindings: memory: tegra124: emc: Replace core regulator with power
>> domain
>> dt-bindings: memory: tegra20: mc: Convert to schema
>> dt-bindings: memory: tegra20: emc: Convert to schema
>> memory: tegra: Print out info-level once per driver probe
>
> Thanks, applied subset - 1-4 and 6. For patch 5/6 I expect v3.
I'll make a v3, thank you.
prev parent reply other threads:[~2021-04-02 14:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 23:04 [PATCH v2 0/6] NVIDIA Tegra memory improvements Dmitry Osipenko
2021-03-30 23:04 ` [PATCH v2 1/6] dt-bindings: memory: tegra20: emc: Replace core regulator with power domain Dmitry Osipenko
2021-03-30 23:04 ` [PATCH v2 2/6] dt-bindings: memory: tegra30: " Dmitry Osipenko
2021-04-01 17:17 ` Rob Herring
2021-03-30 23:04 ` [PATCH v2 3/6] dt-bindings: memory: tegra124: " Dmitry Osipenko
2021-04-01 17:17 ` Rob Herring
2021-03-30 23:04 ` [PATCH v2 4/6] dt-bindings: memory: tegra20: mc: Convert to schema Dmitry Osipenko
2021-04-01 17:18 ` Rob Herring
2021-03-30 23:04 ` [PATCH v2 5/6] dt-bindings: memory: tegra20: emc: " Dmitry Osipenko
2021-03-31 13:40 ` Rob Herring
2021-03-31 14:59 ` Dmitry Osipenko
2021-04-01 15:55 ` Rob Herring
2021-04-02 14:45 ` Dmitry Osipenko
2021-04-04 13:18 ` Dmitry Osipenko
2021-03-30 23:04 ` [PATCH v2 6/6] memory: tegra: Print out info-level once per driver probe Dmitry Osipenko
2021-04-01 17:50 ` [PATCH v2 0/6] NVIDIA Tegra memory improvements Krzysztof Kozlowski
2021-04-01 17:54 ` (subset) " Krzysztof Kozlowski
2021-04-01 17:54 ` Krzysztof Kozlowski
2021-04-02 14:47 ` Dmitry Osipenko [this message]
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=25acdacd-ace5-f680-cace-f8d8119589ea@gmail.com \
--to=digetx@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@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).