From: Pankaj Bansal <pankaj.bansal@nxp.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: UART Baud rate change code flow
Date: Tue, 29 Aug 2017 08:19:49 +0000 [thread overview]
Message-ID: <DBXPR04MB1446FFB6EE7F991D2AD16F6F19F0@DBXPR04MB144.eurprd04.prod.outlook.com> (raw)
Hello Edk2 team,
We are trying to change the UART Baud rate dynamically from UEFI shell using "sermode" command in our ARM64 based platform.
I see the code flow of sermode call as below :
ShellCommandRunSerMode() -> SerialSetAttributes() -> SerialPortSetAttributes()
SerialSetAttributes() <-
TerminalDriverBindingStart() -> SerialSetAttributes() -> SerialPortSetAttributes()
TerminalDriverBindingStart() <- SerialSetAttributes() <-
TerminalConInReset() -> SerialReset () -> SerialPortInitialize()
TerminalConInReset() <- SerialReset() <-
TerminalConInTimerHandler() -> SerialSetAttributes() -> SerialPortSetAttributes()
TerminalConInTimerHandler() <- SerialSetAttributes()
ShellCommandRunSerMode() <-
I am not able to understand why SerialSetAttributes and SerialReset are being called, while the first call to SerialSetAttributes has not yet completed.
Is this code flow right ? am I missing something ?
Thanks & Regards,
Pankaj Bansal
reply other threads:[~2017-08-29 8:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-list 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=DBXPR04MB1446FFB6EE7F991D2AD16F6F19F0@DBXPR04MB144.eurprd04.prod.outlook.com \
--to=devel@edk2.groups.io \
/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