[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6BFE13A3-6A42-455E-BDF7-CD285CC6C66D@fw-web.de>
Date: Thu, 29 Jul 2021 07:53:58 +0200
From: Frank Wunderlich <linux@...web.de>
To: Hsin-Yi Wang <hsinyi@...omium.org>
CC: "moderated list:ARM/Mediatek SoC support"
<linux-mediatek@...ts.infradead.org>, CK Hu <ck.hu@...iatek.com>,
Matthias Brugger <matthias.bgg@...il.com>,
Enric Balletbo i Serra <enric.balletbo@...labora.com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>,
lkml <linux-kernel@...r.kernel.org>, stable@...r.kernel.org,
Frank Wunderlich <frank-w@...lic-files.de>
Subject: Re: [PATCH] soc: mmsys: mediatek: add mask to mmsys routes
Am 29. Juli 2021 07:47:03 MESZ schrieb Hsin-Yi Wang <hsinyi@...omium.org>:
>On Thu, Jul 29, 2021 at 1:40 PM Frank Wunderlich <linux@...web.de>
>wrote:
>>
>
>>
> struct mtk_mmsys_routes {
> u32 from_comp;
> u32 to_comp;
> u32 addr;
> + u32 mask;
> u32 val;
> };
>mask is not the last element, and mmsys_mt8183_routing_table = {
> {
> DDP_COMPONENT_OVL0, DDP_COMPONENT_OVL_2L0,
> MT8183_DISP_OVL0_MOUT_EN, MT8183_OVL0_MOUT_EN_OVL0_2L
> }
>...
>so the mask and val will be wrong. CK, do you know what mask we should
>set for mt8183? Or can we just set a dummy 0 mask.
Ahhh...mt8183 has own mmsys-table and
i had only changed the default one,so
value is now missing because value is now the mask. I have used same order as
CK to avoid confusion and make it easier
to review.
Afaik you could use same value as value to reset same bits...did this in default routing table too.
regards Frank
Powered by blists - more mailing lists