From: Matthias Brugger <matthias.bgg@gmail.com>
To: Chen-Yu Tsai <wenst@chromium.org>,
Rex-BC Chen <rex-bc.chen@mediatek.com>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
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 0/3] Support MediaTek devapc for MT8186
Date: Thu, 2 Jun 2022 16:27:37 +0200 [thread overview]
Message-ID: <c5022150-a2b4-07b9-d8ec-789147134d85@gmail.com> (raw)
In-Reply-To: <CAGXv+5E9s3c0j501fHZxhwsHSeK0vG+GEqLMhtZMvtvC=+etjQ@mail.gmail.com>
On 02/06/2022 09:48, Chen-Yu Tsai wrote:
> On Wed, May 4, 2022 at 7:55 PM Rex-BC Chen <rex-bc.chen@mediatek.com> wrote:
>>
>> This series is for supporting devapc implementation in MT8186.
>>
>> V2:
>> - Add a patch to separate register offsets from mtk_devapc_data.
>>
>> V1:
>> - Add dt-binding and add devapc data for MT8186.
>>
>> Rex-BC Chen (3):
>> dt-bindings: soc: mediatek: devapc: Add bindings for MT8186
>> soc: mediatek: devapc: Separate register offsets from mtk_devapc_data
>> soc: mediatek: devapc: Add support for MT8186
>
> Applied this on next-20220602 (with a few fixes for other section mismatch
> errors), booted and got:
>
> [ 1.948483] mtk-devapc 10207000.devapc: Read Violation
> [ 1.948488] mtk-devapc 10207000.devapc: Bus ID:0x100, Dom ID:0x0,
> Vio Addr:0x13000000
> [ 1.948520] mtk-devapc 10207000.devapc: Read Violation
> [ 1.948523] mtk-devapc 10207000.devapc: Bus ID:0x200, Dom ID:0x0,
> Vio Addr:0x140001a0
> [ 1.948537] mtk-devapc 10207000.devapc: Read Violation
> [ 1.948540] mtk-devapc 10207000.devapc: Bus ID:0x200, Dom ID:0x0,
> Vio Addr:0x140001a0
> [ 1.948555] mtk-devapc 10207000.devapc: Read Violation
> [ 1.948558] mtk-devapc 10207000.devapc: Bus ID:0x200, Dom ID:0x0,
> Vio Addr:0x14000100
> [ 1.948573] mtk-devapc 10207000.devapc: Read Violation
> [ 1.948576] mtk-devapc 10207000.devapc: Bus ID:0x200, Dom ID:0x0,
> Vio Addr:0x14000100
> [ 1.948590] mtk-devapc 10207000.devapc: Read Violation
> [ 1.948593] mtk-devapc 10207000.devapc: Bus ID:0x200, Dom ID:0x0,
> Vio Addr:0x14000100
> [ 1.948607] mtk-devapc 10207000.devapc: Read Violation
> [ 1.948610] mtk-devapc 10207000.devapc: Bus ID:0x200, Dom ID:0x0,
> Vio Addr:0x14000100
> [ 1.948624] mtk-devapc 10207000.devapc: Read Violation
> [ 1.948627] mtk-devapc 10207000.devapc: Bus ID:0x200, Dom ID:0x0,
> Vio Addr:0x14000100
>
> during the boot process. So I think this works well. Manually reading a
> known secure address also triggers it:
>
> root@hayato:~# busybox devmem 0x1000e000
> 0x00000000
> [ 135.069121] mtk-devapc 10207000.devapc: Read Violation
> [ 135.069132] mtk-devapc 10207000.devapc: Bus ID:0x482, Dom ID:0x0,
> Vio Addr:0x1000e000
>
> So,
>
> Tested-by: Chen-Yu Tsai <wenst@chromium.org>
>
Whole series applied to v5.19-next/soc
> BTW, looks like MT8186 support in mainline is shaping up real good.
> SCP firmware is still missing, so video codec stuff won't work.
prev parent reply other threads:[~2022-06-02 14:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 11:54 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
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 [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=c5022150-a2b4-07b9-d8ec-789147134d85@gmail.com \
--to=matthias.bgg@gmail.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=rex-bc.chen@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=runyang.chen@mediatek.com \
--cc=wenst@chromium.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
all inboxes | Powered by JetHome®