From: Matthias Brugger <matthias.bgg@gmail.com>
To: Rex-BC Chen <rex-bc.chen@mediatek.com>
Cc: chunkuang.hu@kernel.org, jitao.shi@mediatek.com,
xinlei.lee@mediatek.com, angelogioacchino.delregno@collabora.com,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH v2,0/2] Add mmsys reset control for MT8186
Date: Tue, 1 Mar 2022 16:20:03 +0100 [thread overview]
Message-ID: <53df3112-869c-e05c-4b6e-0c6db60a536d@gmail.com> (raw)
In-Reply-To: <31507af7c67640fa8161b13a4f279fea1a050f55.camel@mediatek.com>
Hi Rex,
On 01/03/2022 12:13, Rex-BC Chen wrote:
> Hello Matthias,
>
> Thanks for accepting my patches, but I didn't see this patch [1]
> in v5.17-next/soc.
> There will be build error if [1] is not included while [2] is applied.
> The sw0_rst_offset is declared in [2].
>
> If I have mistake, please let me know.
Thanks for the info. That was actually my mistake. Should be fixed by now.
Thanks a lot!
Matthias
> Thanks!
>
> [1]:
> https://patchwork.kernel.org/project/linux-mediatek/patch/20220217082626.15728-2-rex-bc.chen@mediatek.com/
>
> [2]:
> https://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git/commit/?h=v5.17-next/soc&id=831785f0e5b919c29e1bc5f9a74e9ebd38289e24
>
> BRs,
> Rex
> On Tue, 2022-03-01 at 08:35 +0100, Matthias Brugger wrote:
>>
>> On 17/02/2022 09:26, Rex-BC Chen wrote:
>>> v2:
>>> 1. Change variable type from unsigned int to u16.
>>>
>>> v1:
>>> 1. Add a new variable in mmsys driver data to control different
>>> register
>>> offset for different SoCs.
>>> 2. Add MT8183 reset register offset.
>>> 3. Add mmsys reset control for MT8186.
>>>
>>> This series is based on mmsys patch for MT8186 on [1].
>>> [1]:
>>> https://urldefense.com/v3/__https://patchwork.kernel.org/project/linux-mediatek/patch/20220216084831.14883-4-rex-bc.chen@mediatek.com/__;!!CTRNKA9wMg0ARbw!wp2uW6phbST6ySpYRlb7iwmATAVkkCL1JBau9dCwhXj8KRasrAWnLd1EUT9gLE-oF9Yq$
>>>
>>>
>>> Rex-BC Chen (2):
>>> soc: mediatek: mmsys: add sw0_rst_offset in mmsys driver data
>>> soc: mediatek: mmsys: add mmsys reset control for MT8186
>>>
>>> drivers/soc/mediatek/mt8183-mmsys.h | 2 ++
>>> drivers/soc/mediatek/mt8186-mmsys.h | 2 ++
>>> drivers/soc/mediatek/mtk-mmsys.c | 7 +++++--
>>> drivers/soc/mediatek/mtk-mmsys.h | 3 +--
>>> 4 files changed, 10 insertions(+), 4 deletions(-)
>>>
>>
>> Series applied, thanks!
>
prev parent reply other threads:[~2022-03-01 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 8:26 [PATCH v2,0/2] Add mmsys reset control for MT8186 Rex-BC Chen
2022-02-17 8:26 ` [PATCH v2,1/2] soc: mediatek: mmsys: add sw0_rst_offset in mmsys driver data Rex-BC Chen
2022-02-17 10:22 ` AngeloGioacchino Del Regno
2022-02-17 8:26 ` [PATCH v2,2/2] soc: mediatek: mmsys: add mmsys reset control for MT8186 Rex-BC Chen
2022-03-01 7:35 ` [PATCH v2,0/2] Add " Matthias Brugger
2022-03-01 11:13 ` Rex-BC Chen
2022-03-01 15:20 ` Matthias Brugger [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=53df3112-869c-e05c-4b6e-0c6db60a536d@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=jitao.shi@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=rex-bc.chen@mediatek.com \
--cc=xinlei.lee@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).