From: Lukasz Majewski <lukma@denx.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: Teresa Remmet <t.remmet@phytec.de>,
u-boot@lists.denx.de, Tom Rini <trini@konsulko.com>,
Benjamin Hahn <B.Hahn@phytec.de>, Cem Tenruh <c.tenruh@phytec.de>,
Martyn Welch <martyn.welch@collabora.com>,
Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH 2/2] config: Adjust Phytec imx8mm module config to support NVME disk
Date: Thu, 1 Aug 2024 16:42:16 +0200 [thread overview]
Message-ID: <20240801164216.40eec3ec@wsk> (raw)
In-Reply-To: <CAOMZO5CqQtUOt1zgL7x8goSaH=HeFwQkg3-CJtY=ynyHgg7=bA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 655 bytes --]
Hi Fabio,
> Hi Lukasz,
>
> On Thu, Aug 1, 2024 at 9:54 AM Lukasz Majewski <lukma@denx.de> wrote:
>
> > +CONFIG_CYCLIC_MAX_CPU_TIME_US=1000
>
> Please explain why this option was added.
It must have been slipped in...
Default value is 5000 for this SoM.
IMHO it would be safe to remove it (and use default value) - I will
prepare v2 without it. Thanks for spotting it.
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-08-01 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 12:54 [PATCH 1/2] config: Add 'update_bootimg' command to update flash.bin on Phytec's imx8mm Lukasz Majewski
2024-08-01 12:54 ` [PATCH 2/2] config: Adjust Phytec imx8mm module config to support NVME disk Lukasz Majewski
2024-08-01 14:31 ` Fabio Estevam
2024-08-01 14:42 ` Lukasz Majewski [this message]
2024-08-01 13:13 ` [PATCH 1/2] config: Add 'update_bootimg' command to update flash.bin on Phytec's imx8mm Fabio Estevam
2024-08-01 21:16 ` Tom Rini
2024-08-02 8:50 ` Benjamin Hahn
2024-08-02 10:31 ` Lukasz Majewski
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=20240801164216.40eec3ec@wsk \
--to=lukma@denx.de \
--cc=B.Hahn@phytec.de \
--cc=c.tenruh@phytec.de \
--cc=festevam@gmail.com \
--cc=martyn.welch@collabora.com \
--cc=sjg@chromium.org \
--cc=t.remmet@phytec.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