From: sbabic@denx.de
To: Andrey Zhizhikin <andrey.zhizhikin@leica-geosystems.com>,
U-Boot@lists.denx.de
Subject: [PATCH] arm: imx: imx8mm: clock: make debug output more descriptive
Date: Wed, 9 Jun 2021 15:44:23 +0200 (CEST) [thread overview]
Message-ID: <20210609134423.D0BD882FDC@phobos.denx.de> (raw)
In-Reply-To: <20210503080210.705-1-andrey.zhizhikin@leica-geosystems.com>
> Clock initialization functionality has ambitious debug messages, which are
> printed out when failures are triggered during execution:
> - Separate frequency table lookup functions have the the same output that
> makes it impossible to understand which function failed and produced the
> output
> - PLL decoding routine has a generic debug statement printed, which does
> not state the actual value failed to be found
> Extend the output for both cases with prefixing table lookup functions
> output with function name, and report the failed value in PLL decoding
> routine.
> Signed-off-by: Andrey Zhizhikin <andrey.zhizhikin@leica-geosystems.com>
> Cc: Stefano Babic <sbabic@denx.de>
> Cc: Fabio Estevam <festevam@gmail.com>
> Cc: "NXP i.MX U-Boot Team" <uboot-imx@nxp.com>
> Cc: Peng Fan <peng.fan@nxp.com>
> Cc: Simon Glass <sjg@chromium.org>
> Cc: Ye Li <ye.li@nxp.com>
> Reviewed-by: Fabio Estevam <festevam@gmail.com>
Applied to u-boot-imx, master, thanks !
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================
prev parent reply other threads:[~2021-06-09 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 8:02 [PATCH] arm: imx: imx8mm: clock: make debug output more descriptive Andrey Zhizhikin
2021-05-03 10:54 ` Fabio Estevam
2021-06-09 13:44 ` sbabic [this message]
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=20210609134423.D0BD882FDC@phobos.denx.de \
--to=sbabic@denx.de \
--cc=U-Boot@lists.denx.de \
--cc=andrey.zhizhikin@leica-geosystems.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