From: Nishanth Menon <nm@ti.com>
To: Christian Gmeiner <christian.gmeiner@gmail.com>,
Tom Rini <trini@konsulko.com>
Cc: <u-boot@lists.denx.de>, Michael Liebert <liebert@ibv-augsburg.de>,
Dave Gerlach <d-gerlach@ti.com>,
Aswath Govindraju <a-govindraju@ti.com>,
Keerthy <j-keerthy@ti.com>
Subject: Re: [PATCH] arm: mach-k3: am642_init: Unlock MCU PADCFG regs
Date: Fri, 14 Jan 2022 13:27:50 -0600 [thread overview]
Message-ID: <20220114192645.ccw54dfwr3prxyva@repeal> (raw)
In-Reply-To: <20211215151430.102388-1-christian.gmeiner@gmail.com>
On 16:14-20211215, Christian Gmeiner wrote:
> From: Michael Liebert <liebert@ibv-augsburg.de>
>
> Currently only the PADCFG registers of the main domain are unlocked.
> Also unlock PADCFG registers of MCU domain, so MCU pin muxing can be configured by u-boot or Linux.
>
> Signed-off-by: Michael Liebert <liebert@ibv-augsburg.de>
> Tested-by: Christian Gmeiner <christian.gmeiner@gmail.com>
> ---
> arch/arm/mach-k3/am642_init.c | 3 +++
> arch/arm/mach-k3/include/mach/am64_hardware.h | 2 ++
> 2 files changed, 5 insertions(+)
>
> diff --git a/arch/arm/mach-k3/am642_init.c b/arch/arm/mach-k3/am642_init.c
> index 533905daeb..958fa05af4 100644
> --- a/arch/arm/mach-k3/am642_init.c
> +++ b/arch/arm/mach-k3/am642_init.c
> @@ -37,6 +37,9 @@ static void ctrl_mmr_unlock(void)
> mmr_unlock(CTRL_MMR0_BASE, 3);
> mmr_unlock(CTRL_MMR0_BASE, 5);
> mmr_unlock(CTRL_MMR0_BASE, 6);
> +
> + /* Unlock all MCU_PADCFG_MMR1 module registers */
> + mmr_unlock(MCU_PADCFG_MMR1_BASE, 1);
> }
>
> /*
> diff --git a/arch/arm/mach-k3/include/mach/am64_hardware.h b/arch/arm/mach-k3/include/mach/am64_hardware.h
> index 96383437d5..e06e1f9532 100644
> --- a/arch/arm/mach-k3/include/mach/am64_hardware.h
> +++ b/arch/arm/mach-k3/include/mach/am64_hardware.h
> @@ -12,6 +12,8 @@
>
> #define PADCFG_MMR1_BASE 0xf0000
>
> +#define MCU_PADCFG_MMR1_BASE 0x04080000
> +
> #define MAIN_DEVSTAT_PRIMARY_BOOTMODE_MASK 0x00000078
> #define MAIN_DEVSTAT_PRIMARY_BOOTMODE_SHIFT 3
>
Acked-by: Nishanth Menon <nm@ti.com>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2022-01-14 19:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 15:14 [PATCH] arm: mach-k3: am642_init: Unlock MCU PADCFG regs Christian Gmeiner
2022-01-14 19:27 ` Nishanth Menon [this message]
2022-01-17 18:36 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2021-12-15 15:10 Christian Gmeiner
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=20220114192645.ccw54dfwr3prxyva@repeal \
--to=nm@ti.com \
--cc=a-govindraju@ti.com \
--cc=christian.gmeiner@gmail.com \
--cc=d-gerlach@ti.com \
--cc=j-keerthy@ti.com \
--cc=liebert@ibv-augsburg.de \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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