From: Georgi Djakov <georgi.djakov@linaro.org>
To: Chanwoo Choi <cw00.choi@samsung.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
inki.dae@samsung.com
Cc: krzk@kernel.org, devicetree@vger.kernel.org, robh+dt@kernel.org,
a.swigon@samsung.com, myungjoo.ham@samsung.com,
sw0312.kim@samsung.com, b.zolnierkie@samsung.com,
m.szyprowski@samsung.com, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v9 0/5] Exynos: Simple QoS for exynos-bus using interconnect
Date: Fri, 13 Nov 2020 11:02:51 +0200 [thread overview]
Message-ID: <a5fbc409-1af6-1c9a-f648-910baeb191d6@linaro.org> (raw)
In-Reply-To: <9cb7e3a6-2a3f-8f46-2bf1-d6d8ea01613b@samsung.com>
On 11/13/20 11:07, Chanwoo Choi wrote:
> On 11/13/20 5:48 PM, Georgi Djakov wrote:
>> On 11/12/20 16:09, Sylwester Nawrocki wrote:
>>>
>>> This patchset adds interconnect API support for the Exynos SoC "samsung,
>>> exynos-bus" compatible devices, which already have their corresponding
>>> exynos-bus driver in the devfreq subsystem. Complementing the devfreq
>>> driver with an interconnect functionality allows to ensure the QoS
>>> requirements of devices accessing the system memory (e.g. video processing
>>> devices) are fulfilled and allows to avoid issues like the one discussed
>>> in thread [1].
>>>
>>> This patch series adds implementation of the interconnect provider per each
>>> "samsung,exynos-bus" compatible DT node, with one interconnect node per
>>> provider. The interconnect code which was previously added as a part of
>>> the devfreq driver has been converted to a separate platform driver.
>>> In the devfreq a corresponding virtual child platform device is registered.
>>> Integration of devfreq and interconnect frameworks is achieved through
>>> the PM QoS API.
>>>
>>> A sample interconnect consumer for exynos-mixer is added in patch 5/5,
>>> it is currently added only for exynos4412 and allows to address the
>>> mixer DMA underrun error issues [1].
>>
>> Good work Sylwester! Thank you and all the reviewers! What would be the merge
>> path for this patchset? Looks like there is no build dependency between patches.
>> Should i take just patches 2,3 or also patch 1? Chanwoo?
>
> Hi Georgi,
>
> If you take the patch 2,3, I'll apply patch 1,4 to devfreq.git.
Ok, sounds good! Thanks for clarifying!
BR,
Georgi
next prev parent reply other threads:[~2020-11-13 9:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20201112141041eucas1p1a29130955afd4ec1d5d94cf17183920c@eucas1p1.samsung.com>
2020-11-12 14:09 ` [PATCH v9 0/5] Exynos: Simple QoS for exynos-bus using interconnect Sylwester Nawrocki
[not found] ` <CGME20201112141047eucas1p1f4294148c61b778bbb321863b8ef0092@eucas1p1.samsung.com>
2020-11-12 14:09 ` [PATCH v9 1/5] dt-bindings: devfreq: Add documentation for the interconnect properties Sylwester Nawrocki
[not found] ` <CGME20201112141050eucas1p250f62d09adf38b97c521ef67b4b540f0@eucas1p2.samsung.com>
2020-11-12 14:09 ` [PATCH v9 2/5] interconnect: Add generic interconnect driver for Exynos SoCs Sylwester Nawrocki
[not found] ` <CGME20201112141051eucas1p1c94de8fd6032e0a9966cbff9e41c0f2f@eucas1p1.samsung.com>
2020-11-12 14:09 ` [PATCH v9 3/5] MAINTAINERS: Add entry for Samsung interconnect drivers Sylwester Nawrocki
2020-11-12 16:21 ` Krzysztof Kozlowski
[not found] ` <CGME20201112141053eucas1p1acf592a7ece14104a408b77afebb9eed@eucas1p1.samsung.com>
2020-11-12 14:09 ` [PATCH v9 4/5] PM / devfreq: exynos-bus: Add registration of interconnect child device Sylwester Nawrocki
[not found] ` <CGME20201112141055eucas1p10bb68467fbb8c481b1275433f5f5f467@eucas1p1.samsung.com>
2020-11-12 14:09 ` [PATCH v9 5/5] drm: exynos: mixer: Add interconnect support Sylwester Nawrocki
2020-11-13 8:48 ` [PATCH v9 0/5] Exynos: Simple QoS for exynos-bus using interconnect Georgi Djakov
2020-11-13 9:07 ` Chanwoo Choi
2020-11-13 9:02 ` Georgi Djakov [this message]
2020-11-13 10:32 ` Sylwester Nawrocki
2020-11-13 11:00 ` Marek Szyprowski
2020-11-23 6: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=a5fbc409-1af6-1c9a-f648-910baeb191d6@linaro.org \
--to=georgi.djakov@linaro.org \
--cc=a.swigon@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=myungjoo.ham@samsung.com \
--cc=robh+dt@kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=sw0312.kim@samsung.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).