From: "Jonas Mark (BT-FIR/ENG1-Grb)" <Mark.Jonas@de.bosch.com>
To: "Jonas Mark (BT-FIR/ENG1-Grb)" <mark.jonas@de.bosch.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"RUAN Tingquan (BT-FIR/ENG1-Zhu)" <Tingquan.Ruan@cn.bosch.com>
Subject: AW: [PATCH] gpu: ipu-v3: Fix dev_dbg frequency output
Date: Mon, 14 Feb 2022 16:44:46 +0000 [thread overview]
Message-ID: <PAXPR10MB540528C7049118472B4F190EAD339@PAXPR10MB5405.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20220207151411.5009-1-mark.jonas@de.bosch.com>
Hi,
> From: Leo Ruan <tingquan.ruan@cn.bosch.com>
>
> This commit corrects the printing of the IPU clock error percentage if it is
> between -0.1% to -0.9%. For example, if the pixel clock requested is 27.2
> MHz but only 27.0 MHz can be achieved the deviation is -0.8%.
> But the fixed point math had a flaw and calculated error of 0.2%.
>
> Before:
> Clocks: IPU 270000000Hz DI 24716667Hz Needed 27200000Hz
> IPU clock can give 27000000 with divider 10, error 0.2%
> Want 27200000Hz IPU 270000000Hz DI 24716667Hz using IPU,
> 27000000Hz
>
> After:
> Clocks: IPU 270000000Hz DI 24716667Hz Needed 27200000Hz
> IPU clock can give 27000000 with divider 10, error -0.8%
> Want 27200000Hz IPU 270000000Hz DI 24716667Hz using IPU,
> 27000000Hz
>
> Signed-off-by: Leo Ruan <tingquan.ruan@cn.bosch.com>
> Signed-off-by: Mark Jonas <mark.jonas@de.bosch.com>
> ---
> drivers/gpu/ipu-v3/ipu-di.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/ipu-v3/ipu-di.c b/drivers/gpu/ipu-v3/ipu-di.c index
> b4a31d506fcc..74eca68891ad 100644
> --- a/drivers/gpu/ipu-v3/ipu-di.c
> +++ b/drivers/gpu/ipu-v3/ipu-di.c
> @@ -451,8 +451,9 @@ static void ipu_di_config_clock(struct ipu_di *di,
>
> error = rate / (sig->mode.pixelclock / 1000);
>
> - dev_dbg(di->ipu->dev, " IPU clock can give %lu with divider
> %u, error %d.%u%%\n",
> - rate, div, (signed)(error - 1000) / 10, error % 10);
> + dev_dbg(di->ipu->dev, " IPU clock can give %lu with divider
> %u, error %c%d.%d%%\n",
> + rate, div, error < 1000 ? '-' : '+',
> + abs(error - 1000) / 10, abs(error - 1000) % 10);
>
> /* Allow a 1% error */
> if (error < 1010 && error >= 990) {
Is there anything I can do to help getting this patch mainline?
Cheers,
Mark
Mark Jonas
Building Technologies, Panel Software Fire (BT-FIR/ENG1-Grb)
Bosch Sicherheitssysteme GmbH | Postfach 11 11 | 85626 Grasbrunn | GERMANY | www.boschsecurity.com
Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart HRB 23118
Aufsichtsratsvorsitzender: Christian Fischer; Geschäftsführung: Thomas Quante, Peter Löffler, Henrik Siegle
next prev parent reply other threads:[~2022-02-14 16:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 15:14 [PATCH] gpu: ipu-v3: Fix dev_dbg frequency output Mark Jonas
2022-02-14 16:44 ` Jonas Mark (BT-FIR/ENG1-Grb) [this message]
2022-02-14 17:24 ` Lucas Stach
2022-02-16 16:09 ` Philipp Zabel
2022-03-25 18:01 ` AW: " Jonas Mark (BT-FIR/ENG1-Grb)
2022-03-29 16:42 ` Philipp Zabel
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=PAXPR10MB540528C7049118472B4F190EAD339@PAXPR10MB5405.EURPRD10.PROD.OUTLOOK.COM \
--to=mark.jonas@de.bosch.com \
--cc=Tingquan.Ruan@cn.bosch.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.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;
as well as URLs for NNTP newsgroup(s).