From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Rex-BC Chen <rex-bc.chen@mediatek.com>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
matthias.bgg@gmail.com
Cc: runyang.chen@mediatek.com, linux-mediatek@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH v2 2/3] soc: mediatek: devapc: Separate register offsets from mtk_devapc_data
Date: Fri, 6 May 2022 10:19:18 +0200 [thread overview]
Message-ID: <7a4e7d71-4460-21f4-35fa-d3b11559785b@collabora.com> (raw)
In-Reply-To: <20220504115501.3490-3-rex-bc.chen@mediatek.com>
Il 04/05/22 13:55, Rex-BC Chen ha scritto:
> The register offsets is the same between MT6779 and MT8186. To reuse the
> register offsets, we move these register offsets to another structure
> "mtk_devapc_regs_ofs".
>
> Signed-off-by: Rex-BC Chen <rex-bc.chen@mediatek.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
next prev parent reply other threads:[~2022-05-06 8:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 11:54 [PATCH v2 0/3] Support MediaTek devapc for MT8186 Rex-BC Chen
2022-05-04 11:54 ` [PATCH v2 1/3] dt-bindings: soc: mediatek: devapc: Add bindings " Rex-BC Chen
2022-05-04 11:55 ` [PATCH v2 2/3] soc: mediatek: devapc: Separate register offsets from mtk_devapc_data Rex-BC Chen
2022-05-06 8:19 ` AngeloGioacchino Del Regno [this message]
2022-05-07 15:35 ` Chun-Kuang Hu
2022-05-04 11:55 ` [PATCH v2 3/3] soc: mediatek: devapc: Add support for MT8186 Rex-BC Chen
2022-05-06 8:19 ` AngeloGioacchino Del Regno
2022-05-07 15:36 ` Chun-Kuang Hu
2022-05-18 2:51 ` [PATCH v2 0/3] Support MediaTek devapc " Rex-BC Chen
2022-06-02 7:48 ` Chen-Yu Tsai
2022-06-02 14:27 ` Matthias Brugger
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=7a4e7d71-4460-21f4-35fa-d3b11559785b@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=Project_Global_Chrome_Upstream_Group@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=matthias.bgg@gmail.com \
--cc=rex-bc.chen@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=runyang.chen@mediatek.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).