From: Peng Fan <peng.fan@oss.nxp.com>
To: Fedor Ross <fedorross@gmail.com>, u-boot@lists.denx.de
Subject: Re: [PATCH] ARM: imx: Fix parsing of ROM log event IDs on iMX8M
Date: Thu, 20 Apr 2023 20:47:08 +0800 [thread overview]
Message-ID: <4eb3e3e1-e1fb-26ae-de68-ce9f43a4f41b@oss.nxp.com> (raw)
In-Reply-To: <CAEGWRBBUis_xzzyW3PYwGuYV5R_dak6b_yCnhDiLj=mQzNfCcw@mail.gmail.com>
Hi,
Marek pointed me this thread. I admitted I overlooked this patch.
Will check internally and back.
Regards,
Peng.
On 4/15/2022 2:00 AM, Fedor Ross wrote:
> Hello Peng,
>
> can you please check the parameter of event 0x82 internally? The AN12853
> doesn't mention a parameter for ID 0x82, but we see something else coming
> out of the bootrom of iMX8MN.
>
> Best regards,
> Fedor
>
> Am Do., 14. Apr. 2022 um 18:37 Uhr schrieb <fedorross@gmail.com>:
>>
>> From: Fedor Ross <fedor.ross@ifm.com>
>>
>> It seems like the ROM log events for the iMX8M are not fully covered by
>> AN12853 i.MX ROMs Log Events, Rev. 0, May 2020. On iMX8M the ROM event
>> ID 0x82 seems to use parameter0 which stops the parsing because the end
>> of list is detected too early.
>>
>> This patch adds ROM event ID 0x82 and skips the next word if ID 0x82 is
>> parsed.
>>
>>
>> Fixes: a5ee05cf71 ("ARM: imx: Pick correct eMMC boot partition from ROM
> log")
>>
>> Signed-off-by: Fedor Ross <fedor.ross@ifm.com>
>> Cc: Fabio Estevam <festevam@gmail.com>
>> Cc: Marek Vasut <marex@denx.de>
>> Cc: Peng Fan <peng.fan@nxp.com>
>> Cc: Stefano Babic <sbabic@denx.de>
>> ---
>> arch/arm/mach-imx/imx8m/soc.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/arch/arm/mach-imx/imx8m/soc.c b/arch/arm/mach-imx/imx8m/soc.c
>> index 8171631db1..4df57cb150 100644
>> --- a/arch/arm/mach-imx/imx8m/soc.c
>> +++ b/arch/arm/mach-imx/imx8m/soc.c
>> @@ -677,6 +677,7 @@ int spl_mmc_emmc_boot_partition(struct mmc *mmc)
>> /* Log entries with 1 parameter, skip 1 */
>> case 0x80: /* Start to perform the device initialization
> */
>> case 0x81: /* The boot device initialization completes */
>> + case 0x82: /* Starts to execute boot device driver
> pre-config */
>> case 0x8f: /* The boot device initialization fails */
>> case 0x90: /* Start to read data from boot device */
>> case 0x91: /* Reading data from boot device completes */
>> --
>> 2.20.1
>>
next prev parent reply other threads:[~2023-04-20 12:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 16:36 [PATCH] ARM: imx: Fix parsing of ROM log event IDs on iMX8M fedorross
2022-04-14 18:00 ` Fedor Ross
2022-05-06 15:17 ` Fedor Ross
2023-01-25 18:47 ` Fedor Ross
2023-04-20 12:47 ` Peng Fan [this message]
2023-04-24 9:19 ` Peng Fan
2023-05-21 17:12 ` sbabic
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=4eb3e3e1-e1fb-26ae-de68-ce9f43a4f41b@oss.nxp.com \
--to=peng.fan@oss.nxp.com \
--cc=fedorross@gmail.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