From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Yassine Oudjana <yassine.oudjana@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Tinghan Shen <tinghan.shen@mediatek.com>,
"Garmin.Chang" <Garmin.Chang@mediatek.com>,
MandyJH Liu <mandyjh.liu@mediatek.com>
Cc: Yassine Oudjana <y.oudjana@protonmail.com>,
devicetree@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] soc: mediatek: pm-domains: Add support for MT6735
Date: Thu, 2 Mar 2023 16:32:28 +0100 [thread overview]
Message-ID: <c15c9766-4a46-04fc-ab42-2396d0a6750f@collabora.com> (raw)
In-Reply-To: <20230302122708.73848-3-y.oudjana@protonmail.com>
Il 02/03/23 13:27, Yassine Oudjana ha scritto:
> From: Yassine Oudjana <y.oudjana@protonmail.com>
>
> Add support for SCPSYS power domains of MT6735. All non-CPU power domains
For the CPU power domains, I was cooking something locally.... but then I
stopped for some other higher priority stuff.
I'll make sure to ping you when ready, as I think you'll be interested to that.
> are added except for MD2 (C2K modem), which is left out due to issues
> with powering it on.
>
> Signed-off-by: Yassine Oudjana <y.oudjana@protonmail.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
prev parent reply other threads:[~2023-03-02 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 12:27 [PATCH v2 0/2] MediaTek MT6735 SCPSYS support Yassine Oudjana
2023-03-02 12:27 ` [PATCH v2 1/2] dt-bindings: power: Add binding for MediaTek MT6735 power controller Yassine Oudjana
2023-03-02 15:26 ` AngeloGioacchino Del Regno
2023-03-08 19:00 ` Krzysztof Kozlowski
2023-03-02 12:27 ` [PATCH v2 2/2] soc: mediatek: pm-domains: Add support for MT6735 Yassine Oudjana
2023-03-02 15:32 ` AngeloGioacchino Del Regno [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=c15c9766-4a46-04fc-ab42-2396d0a6750f@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=Garmin.Chang@mediatek.com \
--cc=devicetree@vger.kernel.org \
--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=mandyjh.liu@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=tinghan.shen@mediatek.com \
--cc=y.oudjana@protonmail.com \
--cc=yassine.oudjana@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).