From: Dmitry Osipenko <digetx@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Georgi Djakov <georgi.djakov@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Mikko Perttunen <cyndis@kapsi.fi>,
Viresh Kumar <vireshk@kernel.org>,
Peter Geis <pgwipeout@gmail.com>,
Nicolas Chauvet <kwizart@gmail.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
linux-tegra@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v10 00/19] Introduce memory interconnect for NVIDIA Tegra SoCs
Date: Mon, 23 Nov 2020 15:13:57 +0300 [thread overview]
Message-ID: <1bfbeb36-29b3-30c2-899f-faa5b0682bd7@gmail.com> (raw)
In-Reply-To: <20201123061734.mpmkdxzullrh52o7@vireshk-i7>
23.11.2020 09:17, Viresh Kumar пишет:
> On 23-11-20, 03:27, Dmitry Osipenko wrote:
>> This series brings initial support for memory interconnect to Tegra20,
>> Tegra30 and Tegra124 SoCs.
>>
>> For the starter only display controllers and devfreq devices are getting
>> interconnect API support, others could be supported later on. The display
>> controllers have the biggest demand for interconnect API right now because
>> dynamic memory frequency scaling can't be done safely without taking into
>> account bandwidth requirement from the displays. In particular this series
>> fixes distorted display output on T30 Ouya and T124 TK1 devices.
>>
>> Changelog:
>>
>> v10 - In a longer run it will be much nicer if we could support EMC
>> hardware versioning on Tegra20 and it's not late to support it now.
>> Hence I added these new patches:
>>
>> dt-bindings: memory: tegra20: emc: Document opp-supported-hw property
>> memory: tegra20: Support hardware versioning and clean up OPP table initialization
>>
>> - Removed error message from tegra30-devfreq driver about missing OPP
>> properties in a device-tree because EMC driver already prints that
>> message and it uses OPP API error code instead of checking DT directly,
>> which is a more correct way of doing that.
>
> Looks good to me (from OPP APIs usage perspective). Thanks for
> continuing with this and fixing all the issues Dmitry.
>
Hello Viresh,
Thank you for all the clarifications and for reviewing of the patches!
WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Osipenko <digetx@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Peter De Schrijver <pdeschrijver@nvidia.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Mikko Perttunen <cyndis@kapsi.fi>,
dri-devel@lists.freedesktop.org,
Nicolas Chauvet <kwizart@gmail.com>,
Stephen Boyd <sboyd@kernel.org>,
Viresh Kumar <vireshk@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Thierry Reding <thierry.reding@gmail.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Peter Geis <pgwipeout@gmail.com>,
linux-tegra@vger.kernel.org,
Georgi Djakov <georgi.djakov@linaro.org>
Subject: Re: [PATCH v10 00/19] Introduce memory interconnect for NVIDIA Tegra SoCs
Date: Mon, 23 Nov 2020 15:13:57 +0300 [thread overview]
Message-ID: <1bfbeb36-29b3-30c2-899f-faa5b0682bd7@gmail.com> (raw)
In-Reply-To: <20201123061734.mpmkdxzullrh52o7@vireshk-i7>
23.11.2020 09:17, Viresh Kumar пишет:
> On 23-11-20, 03:27, Dmitry Osipenko wrote:
>> This series brings initial support for memory interconnect to Tegra20,
>> Tegra30 and Tegra124 SoCs.
>>
>> For the starter only display controllers and devfreq devices are getting
>> interconnect API support, others could be supported later on. The display
>> controllers have the biggest demand for interconnect API right now because
>> dynamic memory frequency scaling can't be done safely without taking into
>> account bandwidth requirement from the displays. In particular this series
>> fixes distorted display output on T30 Ouya and T124 TK1 devices.
>>
>> Changelog:
>>
>> v10 - In a longer run it will be much nicer if we could support EMC
>> hardware versioning on Tegra20 and it's not late to support it now.
>> Hence I added these new patches:
>>
>> dt-bindings: memory: tegra20: emc: Document opp-supported-hw property
>> memory: tegra20: Support hardware versioning and clean up OPP table initialization
>>
>> - Removed error message from tegra30-devfreq driver about missing OPP
>> properties in a device-tree because EMC driver already prints that
>> message and it uses OPP API error code instead of checking DT directly,
>> which is a more correct way of doing that.
>
> Looks good to me (from OPP APIs usage perspective). Thanks for
> continuing with this and fixing all the issues Dmitry.
>
Hello Viresh,
Thank you for all the clarifications and for reviewing of the patches!
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-11-23 12:14 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20201123003254epcas1p1763e1ce693d7cb8e2f20d521e701ad5f@epcas1p1.samsung.com>
2020-11-23 0:27 ` [PATCH v10 00/19] Introduce memory interconnect for NVIDIA Tegra SoCs Dmitry Osipenko
2020-11-23 0:27 ` Dmitry Osipenko
2020-11-23 0:27 ` [PATCH v10 01/19] dt-bindings: memory: tegra20: emc: Document opp-supported-hw property Dmitry Osipenko
2020-11-23 0:27 ` Dmitry Osipenko
2020-11-30 9:48 ` Georgi Djakov
2020-11-30 9:48 ` Georgi Djakov
2020-11-30 18:23 ` Krzysztof Kozlowski
2020-11-30 18:23 ` Krzysztof Kozlowski
2020-11-30 20:03 ` Dmitry Osipenko
2020-11-30 20:03 ` Dmitry Osipenko
2020-11-23 0:27 ` [PATCH v10 02/19] memory: tegra20: Support hardware versioning and clean up OPP table initialization Dmitry Osipenko
2020-11-23 0:27 ` Dmitry Osipenko
2020-11-23 0:27 ` [PATCH v10 03/19] memory: tegra30: Support interconnect framework Dmitry Osipenko
2020-11-23 0:27 ` Dmitry Osipenko
2020-11-23 6:32 ` Georgi Djakov
2020-11-23 6:32 ` Georgi Djakov
2020-11-23 12:14 ` Dmitry Osipenko
2020-11-23 12:14 ` Dmitry Osipenko
2020-11-23 0:27 ` [PATCH v10 04/19] memory: tegra124-emc: Make driver modular Dmitry Osipenko
2020-11-23 0:27 ` Dmitry Osipenko
2020-11-23 0:27 ` [PATCH v10 05/19] memory: tegra124-emc: Continue probing if timings are missing in device-tree Dmitry Osipenko
2020-11-23 0:27 ` Dmitry Osipenko
2020-11-23 0:27 ` [PATCH v10 06/19] memory: tegra124: Support interconnect framework Dmitry Osipenko
2020-11-23 0:27 ` Dmitry Osipenko
2020-11-23 6:33 ` Georgi Djakov
2020-11-23 6:33 ` Georgi Djakov
2020-11-23 0:27 ` [PATCH v10 07/19] drm/tegra: dc: Support memory bandwidth management Dmitry Osipenko
2020-11-23 0:27 ` Dmitry Osipenko
2020-11-23 0:27 ` [PATCH v10 08/19] drm/tegra: dc: Extend debug stats with total number of events Dmitry Osipenko
2020-11-23 0:27 ` Dmitry Osipenko
2020-11-23 0:27 ` [PATCH v10 09/19] PM / devfreq: tegra30: Support interconnect and OPPs from device-tree Dmitry Osipenko
2020-11-23 0:27 ` Dmitry Osipenko
2020-11-23 7:02 ` Chanwoo Choi
2020-11-23 7:02 ` Chanwoo Choi
2020-11-23 12:14 ` Dmitry Osipenko
2020-11-23 12:14 ` Dmitry Osipenko
2020-11-23 0:27 ` [PATCH v10 10/19] PM / devfreq: tegra30: Separate configurations per-SoC generation Dmitry Osipenko
2020-11-23 0:27 ` Dmitry Osipenko
2020-11-23 0:27 ` [PATCH v10 11/19] PM / devfreq: tegra20: Deprecate in a favor of emc-stat based driver Dmitry Osipenko
2020-11-23 0:27 ` Dmitry Osipenko
2020-11-23 7:02 ` Chanwoo Choi
2020-11-23 7:02 ` Chanwoo Choi
2020-11-23 0:27 ` [PATCH v10 12/19] ARM: tegra: Correct EMC registers size in Tegra20 device-tree Dmitry Osipenko
2020-11-23 0:27 ` Dmitry Osipenko
2020-11-23 0:27 ` [PATCH v10 13/19] ARM: tegra: Add interconnect properties to " Dmitry Osipenko
2020-11-23 0:27 ` Dmitry Osipenko
2020-11-23 0:27 ` [PATCH v10 14/19] ARM: tegra: Add interconnect properties to Tegra30 device-tree Dmitry Osipenko
2020-11-23 0:27 ` Dmitry Osipenko
2020-11-23 0:27 ` [PATCH v10 15/19] ARM: tegra: Add interconnect properties to Tegra124 device-tree Dmitry Osipenko
2020-11-23 0:27 ` Dmitry Osipenko
2020-11-23 0:27 ` [PATCH v10 16/19] ARM: tegra: Add nvidia,memory-controller phandle to Tegra20 EMC device-tree Dmitry Osipenko
2020-11-23 0:27 ` [PATCH v10 16/19] ARM: tegra: Add nvidia, memory-controller " Dmitry Osipenko
2020-11-23 0:27 ` [PATCH v10 17/19] ARM: tegra: Add EMC OPP properties to Tegra20 device-trees Dmitry Osipenko
2020-11-23 0:27 ` Dmitry Osipenko
2020-11-30 21:17 ` Jon Hunter
2020-11-30 21:17 ` Jon Hunter
2020-11-30 22:57 ` Dmitry Osipenko
2020-11-30 22:57 ` Dmitry Osipenko
2020-12-01 20:42 ` Jon Hunter
2020-12-01 20:42 ` Jon Hunter
2020-12-04 15:54 ` Thierry Reding
2020-12-04 15:54 ` Thierry Reding
2020-12-05 13:52 ` Krzysztof Kozlowski
2020-12-05 13:52 ` Krzysztof Kozlowski
2020-11-23 0:27 ` [PATCH v10 18/19] ARM: tegra: Add EMC OPP and ICC properties to Tegra30 EMC and ACTMON device-tree nodes Dmitry Osipenko
2020-11-23 0:27 ` Dmitry Osipenko
2020-11-23 0:27 ` [PATCH v10 19/19] ARM: tegra: Add EMC OPP and ICC properties to Tegra124 " Dmitry Osipenko
2020-11-23 0:27 ` Dmitry Osipenko
2020-11-23 6:17 ` [PATCH v10 00/19] Introduce memory interconnect for NVIDIA Tegra SoCs Viresh Kumar
2020-11-23 6:17 ` Viresh Kumar
2020-11-23 12:13 ` Dmitry Osipenko [this message]
2020-11-23 12:13 ` Dmitry Osipenko
2020-11-30 8:44 ` Chanwoo Choi
2020-11-30 8:44 ` Chanwoo Choi
2020-11-30 8:36 ` Krzysztof Kozlowski
2020-11-30 8:36 ` Krzysztof Kozlowski
2020-11-30 8:59 ` Chanwoo Choi
2020-11-30 8:59 ` Chanwoo Choi
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=1bfbeb36-29b3-30c2-899f-faa5b0682bd7@gmail.com \
--to=digetx@gmail.com \
--cc=cw00.choi@samsung.com \
--cc=cyndis@kapsi.fi \
--cc=dri-devel@lists.freedesktop.org \
--cc=georgi.djakov@linaro.org \
--cc=jonathanh@nvidia.com \
--cc=krzk@kernel.org \
--cc=kwizart@gmail.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=myungjoo.ham@samsung.com \
--cc=pdeschrijver@nvidia.com \
--cc=pgwipeout@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@kernel.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.