From: Frederic Konrad <konrad.frederic@yahoo.fr>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: hw/display/xlinx-dp: fixing comment
Date: Sun, 27 Aug 2023 13:58:16 +0000 (UTC) [thread overview]
Message-ID: <750471950.1150401.1693144696776@mail.yahoo.com> (raw)
In-Reply-To: <2f63a7b2-e70f-42a4-a0c7-346e7e00ebda@tls.msk.ru>
[-- Attachment #1: Type: text/plain, Size: 1454 bytes --]
Hi,
Yes that comment makes sense thanks.
Best Regards,Fred
Le samedi 26 août 2023 à 12:20:35 UTC+2, Michael Tokarev <mjt@tls.msk.ru> a écrit :
Hi!
Hopefully this address still works. If not, let's just commit Peter's comment.
Back in 2016, this commit introduced xlinx-dp.c:
commit 58ac482a66de09a7590f705e53fc6a3fb8a055e8
Author: Frederic Konrad <konrad.frederic@yahoo.fr>
Date: Tue Jun 14 15:59:15 2016 +0100
introduce xlnx-dp
This is the implementation of the DisplayPort.
It has an aux-bus to access dpcd and edid.
This commit has the following comment in it:
+static void xlnx_dp_audio_callback(void *opaque, int avail)
+{
+ /*
+ * Get some data from the DPDMA and compute these datas.
+ * Then wait for QEMU's audio subsystem to call this callback.
+ */
As it is, the commit is difficult to understand and has spelling
error in it (datas). Is the following interpretation by Peter
Maydell correct?
/*
* Get the individual left and right audio streams from
* the DPDMA, and fill the output buffer with the
* combined stereo audio data adjusted by the volume
* controls.
* QEMU's audio subsystem will call this callback
* repeatedly; we return it the data from the output
* buffer until it is emptied, and then we will read
* data from the DPDMA again.
*/
Thanks,
/mjt
[-- Attachment #2: Type: text/html, Size: 3552 bytes --]
prev parent reply other threads:[~2023-08-27 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 10:20 hw/display/xlinx-dp: fixing comment Michael Tokarev
2023-08-27 13:58 ` Frederic Konrad [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=750471950.1150401.1693144696776@mail.yahoo.com \
--to=konrad.frederic@yahoo.fr \
--cc=mjt@tls.msk.ru \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).