From: Kevin Hilman <khilman@kernel.org>
To: Johnson Wang <johnson.wang@mediatek.com>,
cw00.choi@samsung.com, krzk+dt@kernel.org, robh+dt@kernel.org,
kyungmin.park@samsung.com
Cc: djakov@kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, jia-wei.chang@mediatek.com,
Project_Global_Chrome_Upstream_Group@mediatek.com,
Johnson Wang <johnson.wang@mediatek.com>
Subject: Re: [PATCH v7 0/2] Introduce MediaTek CCI devfreq driver
Date: Wed, 08 Jun 2022 02:32:45 -0700 [thread overview]
Message-ID: <7hr13z7b5u.fsf@baylibre.com> (raw)
In-Reply-To: <20220607140556.6278-1-johnson.wang@mediatek.com>
Johnson Wang <johnson.wang@mediatek.com> writes:
> The Cache Coherent Interconnect (CCI) is the management of cache
> coherency by hardware. CCI DEVFREQ is DVFS driver for power saving by
> scaling clock frequency and supply voltage of CCI. CCI uses the same
> input clock source and power rail as LITTLE CPUs on Mediatek SoCs.
Tested-by: Kevin Hilman <khilman@baylibre.com>
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@kernel.org>
To: Johnson Wang <johnson.wang@mediatek.com>,
cw00.choi@samsung.com, krzk+dt@kernel.org, robh+dt@kernel.org,
kyungmin.park@samsung.com
Cc: djakov@kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, jia-wei.chang@mediatek.com,
Project_Global_Chrome_Upstream_Group@mediatek.com,
Johnson Wang <johnson.wang@mediatek.com>
Subject: Re: [PATCH v7 0/2] Introduce MediaTek CCI devfreq driver
Date: Wed, 08 Jun 2022 02:32:45 -0700 [thread overview]
Message-ID: <7hr13z7b5u.fsf@baylibre.com> (raw)
In-Reply-To: <20220607140556.6278-1-johnson.wang@mediatek.com>
Johnson Wang <johnson.wang@mediatek.com> writes:
> The Cache Coherent Interconnect (CCI) is the management of cache
> coherency by hardware. CCI DEVFREQ is DVFS driver for power saving by
> scaling clock frequency and supply voltage of CCI. CCI uses the same
> input clock source and power rail as LITTLE CPUs on Mediatek SoCs.
Tested-by: Kevin Hilman <khilman@baylibre.com>
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@kernel.org>
To: Johnson Wang <johnson.wang@mediatek.com>,
cw00.choi@samsung.com, krzk+dt@kernel.org, robh+dt@kernel.org,
kyungmin.park@samsung.com
Cc: djakov@kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, jia-wei.chang@mediatek.com,
Project_Global_Chrome_Upstream_Group@mediatek.com,
Johnson Wang <johnson.wang@mediatek.com>
Subject: Re: [PATCH v7 0/2] Introduce MediaTek CCI devfreq driver
Date: Wed, 08 Jun 2022 02:32:45 -0700 [thread overview]
Message-ID: <7hr13z7b5u.fsf@baylibre.com> (raw)
In-Reply-To: <20220607140556.6278-1-johnson.wang@mediatek.com>
Johnson Wang <johnson.wang@mediatek.com> writes:
> The Cache Coherent Interconnect (CCI) is the management of cache
> coherency by hardware. CCI DEVFREQ is DVFS driver for power saving by
> scaling clock frequency and supply voltage of CCI. CCI uses the same
> input clock source and power rail as LITTLE CPUs on Mediatek SoCs.
Tested-by: Kevin Hilman <khilman@baylibre.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-08 9:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220607140711epcas1p1aca32de28831fae8a6fd3b890b26f7ac@epcas1p1.samsung.com>
2022-06-07 14:05 ` [PATCH v7 0/2] Introduce MediaTek CCI devfreq driver Johnson Wang
2022-06-07 14:05 ` Johnson Wang
2022-06-07 14:05 ` Johnson Wang
2022-06-07 14:05 ` [PATCH v7 1/2] dt-bindings: interconnect: Add MediaTek CCI dt-bindings Johnson Wang
2022-06-07 14:05 ` Johnson Wang
2022-06-07 14:05 ` Johnson Wang
2022-06-10 10:43 ` AngeloGioacchino Del Regno
2022-06-10 10:43 ` AngeloGioacchino Del Regno
2022-06-10 10:43 ` AngeloGioacchino Del Regno
2022-06-27 8:11 ` Krzysztof Kozlowski
2022-06-27 8:11 ` Krzysztof Kozlowski
2022-06-07 14:05 ` [PATCH v7 2/2] PM / devfreq: mediatek: Introduce MediaTek CCI devfreq driver Johnson Wang
2022-06-07 14:05 ` Johnson Wang
2022-06-07 14:05 ` Johnson Wang
2022-06-10 10:44 ` AngeloGioacchino Del Regno
2022-06-10 10:44 ` AngeloGioacchino Del Regno
2022-06-10 10:44 ` AngeloGioacchino Del Regno
2022-06-08 2:00 ` [PATCH v7 0/2] " Chanwoo Choi
2022-06-08 2:00 ` Chanwoo Choi
2022-06-08 2:00 ` Chanwoo Choi
2022-06-08 9:32 ` Kevin Hilman [this message]
2022-06-08 9:32 ` Kevin Hilman
2022-06-08 9:32 ` Kevin Hilman
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=7hr13z7b5u.fsf@baylibre.com \
--to=khilman@kernel.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=jia-wei.chang@mediatek.com \
--cc=johnson.wang@mediatek.com \
--cc=krzk+dt@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@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.