From: Andrew Davis <afd@ti.com>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: <u-boot@lists.denx.de>, Tom Rini <trini@konsulko.com>,
Emanuele Ghidoli <emanuele.ghidoli@toradex.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Francesco Dolcini <francesco.dolcini@toradex.com>
Subject: Re: [PATCH v1 1/3] arm: k3: Fix ft_system_setup so it can be enabled on any SoC
Date: Wed, 12 Jul 2023 09:38:33 -0500 [thread overview]
Message-ID: <ff20c651-9093-e65e-5adc-1eaf5ade7145@ti.com> (raw)
In-Reply-To: <ZK65foLwinHydjaF@francesco-nb.int.toradex.com>
On 7/12/23 9:32 AM, Francesco Dolcini wrote:
> On Wed, Jul 12, 2023 at 09:15:21AM -0500, Andrew Davis wrote:
>> On 7/12/23 8:47 AM, Francesco Dolcini wrote:
>>> From: Emanuele Ghidoli <emanuele.ghidoli@toradex.com>
>>>
>>> ft_system_setup cannot be enabled on SoC without msmc sram otherwise
>>> fdt_fixup_msmc_ram function fails causing system reset.
>>>
>>> Fix by calling fdt_fixup_msmc_ram only on these specific SoC:
>>> - J721S2
>>> - AM654
>>> - J721E
>>>
>>> This change was verified to not change anything on any existing board
>>> (all the J721S2, AM654 and J721E boards requires it,
>>> none of the remaining k3 boards require it).
>>>
>>> Fixes: 30e96a240156 ("arm: mach-k3: Move MSMC fixup to SoC level")
>>> Signed-off-by: Emanuele Ghidoli <emanuele.ghidoli@toradex.com>
>>> Signed-off-by: Francesco Dolcini <francesco.dolcini@toradex.com>
>>> ---
>>> arch/arm/mach-k3/common.c | 20 ++++++++++++--------
>>> 1 file changed, 12 insertions(+), 8 deletions(-)
>>>
>>> diff --git a/arch/arm/mach-k3/common.c b/arch/arm/mach-k3/common.c
>>> index 34737a43aa08..f86ccaedc94f 100644
>>> --- a/arch/arm/mach-k3/common.c
>>> +++ b/arch/arm/mach-k3/common.c
>>> @@ -433,14 +433,18 @@ int fdt_fixup_msmc_ram(void *blob, char *parent_path, char *node_name)
>>> #if defined(CONFIG_OF_SYSTEM_SETUP)
>>> int ft_system_setup(void *blob, struct bd_info *bd)
>>
>> How about we rename this function to something like ft_msmc_sram_setup(), then only
>> call it from board_setup for the platforms that needed it.
>
> This is partially reverting what you did in commit
> 30e96a240156 ("arm: mach-k3: Move MSMC fixup to SoC level").
>
> Is this fixup going to be required if tomorrow we have a new board using
> the AM654 SoC (for example) or not? Depending on this answer we can
> decide if ft_board_setup or ft_system_setup is the right function to use.
>
Maybe the issue is that we have a common ft_system_setup() function for all
of K3, when these should be specific to each SoC.. They could call into
common functions for common tasks like MSMC fixup, but no need to have
one big ft_system_setup() for all K3.
Andrew
next prev parent reply other threads:[~2023-07-12 14:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 13:47 [PATCH v1 0/3] arm: mach-k3: am62: Add core number autodetection and fix fdt Francesco Dolcini
2023-07-12 13:47 ` [PATCH v1 1/3] arm: k3: Fix ft_system_setup so it can be enabled on any SoC Francesco Dolcini
2023-07-12 14:15 ` Andrew Davis
2023-07-12 14:32 ` Francesco Dolcini
2023-07-12 14:38 ` Andrew Davis [this message]
2023-07-13 6:17 ` Francesco Dolcini
2023-07-12 13:47 ` [PATCH v1 2/3] arm: mach-k3: am62: Add CTRLMMR_WKUP_JTAG_DEVICE_ID register definition Francesco Dolcini
2023-07-12 14:18 ` Andrew Davis
2023-07-12 14:25 ` Francesco Dolcini
2023-07-12 13:47 ` [PATCH v1 3/3] arm: mach-k3: am62: Fixup CPU core counts in fdt Francesco Dolcini
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=ff20c651-9093-e65e-5adc-1eaf5ade7145@ti.com \
--to=afd@ti.com \
--cc=emanuele.ghidoli@toradex.com \
--cc=francesco.dolcini@toradex.com \
--cc=francesco@dolcini.it \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.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