From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Tzung-Bi Shih <tzungbi@google.com>
Cc: ohad@wizery.com, matthias.bgg@gmail.com,
linux-mediatek@lists.infradead.org,
linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH] remoteproc/mediatek: change MT8192 CFG register base
Date: Thu, 10 Dec 2020 11:02:17 -0600 [thread overview]
Message-ID: <X9JUmRarnxPaXtrZ@builder.lan> (raw)
In-Reply-To: <20201210054109.587795-1-tzungbi@google.com>
On Wed 09 Dec 23:41 CST 2020, Tzung-Bi Shih wrote:
> The correct MT8192 CFG register base is 0x20000 off. Changes the
> registers accordingly.
>
> Fixes: fd0b6c1ff85a ("remoteproc/mediatek: Add support for mt8192 SCP")
> Signed-off-by: Tzung-Bi Shih <tzungbi@google.com>
I presume there's an associated DT change with this?
I'm okay with taking this, but would like to have Matthias ack on the
fact that we're breaking backwards compatibility with older DTS.
(Or I could ack this and Matthias can take it together with the DT
change, to reduce the breakage gap in the git history?)
Regards,
Bjorn
> ---
> drivers/remoteproc/mtk_common.h | 26 +++++++++++++-------------
> 1 file changed, 13 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/remoteproc/mtk_common.h b/drivers/remoteproc/mtk_common.h
> index b3397d327786..fb022ff93dc1 100644
> --- a/drivers/remoteproc/mtk_common.h
> +++ b/drivers/remoteproc/mtk_common.h
> @@ -32,22 +32,22 @@
> #define MT8183_SCP_CACHESIZE_8KB BIT(8)
> #define MT8183_SCP_CACHE_CON_WAYEN BIT(10)
>
> -#define MT8192_L2TCM_SRAM_PD_0 0x210C0
> -#define MT8192_L2TCM_SRAM_PD_1 0x210C4
> -#define MT8192_L2TCM_SRAM_PD_2 0x210C8
> -#define MT8192_L1TCM_SRAM_PDN 0x2102C
> -#define MT8192_CPU0_SRAM_PD 0x21080
> -
> -#define MT8192_SCP2APMCU_IPC_SET 0x24080
> -#define MT8192_SCP2APMCU_IPC_CLR 0x24084
> +#define MT8192_L2TCM_SRAM_PD_0 0x10C0
> +#define MT8192_L2TCM_SRAM_PD_1 0x10C4
> +#define MT8192_L2TCM_SRAM_PD_2 0x10C8
> +#define MT8192_L1TCM_SRAM_PDN 0x102C
> +#define MT8192_CPU0_SRAM_PD 0x1080
> +
> +#define MT8192_SCP2APMCU_IPC_SET 0x4080
> +#define MT8192_SCP2APMCU_IPC_CLR 0x4084
> #define MT8192_SCP_IPC_INT_BIT BIT(0)
> -#define MT8192_SCP2SPM_IPC_CLR 0x24094
> -#define MT8192_GIPC_IN_SET 0x24098
> +#define MT8192_SCP2SPM_IPC_CLR 0x4094
> +#define MT8192_GIPC_IN_SET 0x4098
> #define MT8192_HOST_IPC_INT_BIT BIT(0)
>
> -#define MT8192_CORE0_SW_RSTN_CLR 0x30000
> -#define MT8192_CORE0_SW_RSTN_SET 0x30004
> -#define MT8192_CORE0_WDT_CFG 0x30034
> +#define MT8192_CORE0_SW_RSTN_CLR 0x10000
> +#define MT8192_CORE0_SW_RSTN_SET 0x10004
> +#define MT8192_CORE0_WDT_CFG 0x10034
>
> #define SCP_FW_VER_LEN 32
> #define SCP_SHARE_BUFFER_SIZE 288
> --
> 2.29.2.576.ga3fc446d84-goog
>
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2020-12-10 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 5:41 [PATCH] remoteproc/mediatek: change MT8192 CFG register base Tzung-Bi Shih
2020-12-10 17:02 ` Bjorn Andersson [this message]
2020-12-10 17:09 ` Tzung-Bi Shih
2020-12-10 19:13 ` Bjorn Andersson
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=X9JUmRarnxPaXtrZ@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=ohad@wizery.com \
--cc=tzungbi@google.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).