From: "Gadiyar, Anand" <gadiyar@ti.com>
To: "Davis, Andrew" <afd@ti.com>,
Denys Dmytriyenko <denys@konsulko.com>,
"Eatmon, Ryan" <reatmon@ti.com>,
"meta-ti@lists.yoctoproject.org" <meta-ti@lists.yoctoproject.org>
Subject: RE: [meta-ti][dunfell][PATCH 2/2] optee-os: Lower log level for AM62x
Date: Thu, 1 Sep 2022 19:39:59 +0000 [thread overview]
Message-ID: <eaf0b3e408724b3982ff04cb47f3d764@ti.com> (raw)
In-Reply-To: <f71a1fe4-92e3-0e82-e2bd-07b5a32fd86a@ti.com>
> From: Davis, Andrew <afd@ti.com>
>
> On 8/26/22 2:16 PM, Andrew Davis wrote:
> > During resume from low power mode suspend OP-TEE prints some messages
> > on the UART. It seems this UART is not powered at this point in the
> > sequence breaking suspend/resume. We should track down the exact
> > prints and quiet them. Until we get that fix upstream, lets lower
> > the log level for this platform to unblock the LPM work.
> >
> > Signed-off-by: Andrew Davis <afd@ti.com>
> > ---
> > recipes-security/optee/optee-os_%.bbappend | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/recipes-security/optee/optee-os_%.bbappend b/recipes-
> security/optee/optee-os_%.bbappend
> > index 4081b324..3cda8559 100644
> > --- a/recipes-security/optee/optee-os_%.bbappend
> > +++ b/recipes-security/optee/optee-os_%.bbappend
> > @@ -6,7 +6,7 @@ DEPENDS_append_ti-soc = " python3-cryptography-native"
> >
> > EXTRA_OEMAKE_append_k3 = "${@ 'CFG_CONSOLE_UART='+ d.getVar('OPTEE_K3_USART') if d.getVar('OPTEE_K3_USART') else ''}"
> >
> > -EXTRA_OEMAKE_append_am62xx-evm = " CFG_WITH_SOFTWARE_PRNG=y"
> > +EXTRA_OEMAKE_append_am62xx-evm = " CFG_WITH_SOFTWARE_PRNG=y CFG_TEE_CORE_LOG_LEVEL=1"
>
>
> ping.
>
> Looks like there is now a merge conflict for this, easy enough to
> fix, add CFG_TEE_CORE_LOG_LEVEL=1 to the new am62xx-lp-evm also.
>
> If you want me to re-send let me know.
>
> Andrew
Probably best to resend - I thought I had added it for am62xx-lp-evm
when I sent it out but it seems I did not. Sorry.
next prev parent reply other threads:[~2022-09-01 19:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 19:16 [meta-ti][dunfell][PATCH 1/2] optee-os: Upgrade to upstream 3.18.0 Andrew Davis
2022-08-26 19:16 ` [meta-ti][dunfell][PATCH 2/2] optee-os: Lower log level for AM62x Andrew Davis
2022-08-26 19:37 ` Gadiyar, Anand
2022-09-01 18:56 ` Andrew Davis
2022-09-01 19:39 ` Gadiyar, Anand [this message]
2022-08-26 22:30 ` [meta-ti][dunfell][PATCH 1/2] optee-os: Upgrade to upstream 3.18.0 Bajjuri, Praneeth
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=eaf0b3e408724b3982ff04cb47f3d764@ti.com \
--to=gadiyar@ti.com \
--cc=afd@ti.com \
--cc=denys@konsulko.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=reatmon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.