From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
"Matthias Brugger" <matthias.bgg@gmail.com>
Cc: kernel@collabora.com, Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v2 1/2] arm64: dts: mediatek: cherry: Describe CPU supplies
Date: Wed, 10 Jan 2024 15:32:02 +0100 [thread overview]
Message-ID: <e325a4d4-0df7-499c-9d55-7da093b744ea@collabora.com> (raw)
In-Reply-To: <20240110142305.755367-2-nfraprado@collabora.com>
Il 10/01/24 15:23, Nícolas F. R. A. Prado ha scritto:
> Describe in each CPU node the regulator supplying it.
>
> Fixes: 260c04d425eb ("arm64: dts: mediatek: cherry: Enable MT6315 regulators on SPMI bus")
> Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
next prev parent reply other threads:[~2024-01-10 14:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 14:23 [PATCH v2 0/2] Fixes for hang on MT8195-Tomato during mediatek-cpufreq-hw init Nícolas F. R. A. Prado
2024-01-10 14:23 ` [PATCH v2 1/2] arm64: dts: mediatek: cherry: Describe CPU supplies Nícolas F. R. A. Prado
2024-01-10 14:32 ` AngeloGioacchino Del Regno [this message]
2024-02-29 20:23 ` Nícolas F. R. A. Prado
2024-03-01 8:52 ` AngeloGioacchino Del Regno
2024-03-01 14:29 ` Nícolas F. R. A. Prado
2024-01-10 14:23 ` [PATCH v2 2/2] cpufreq: mediatek-hw: Wait for CPU supplies before probing Nícolas F. R. A. Prado
2024-01-10 14:31 ` AngeloGioacchino Del Regno
2024-01-22 8:38 ` Matthias Brugger
2024-01-23 6:09 ` Viresh Kumar
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=e325a4d4-0df7-499c-9d55-7da093b744ea@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=nfraprado@collabora.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=viresh.kumar@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox