From: Sean Young <sean@mess.org>
To: Oliver Neukum <oneukum@suse.com>
Cc: linux-media@vger.kernel.org, mchehab@kernel.org
Subject: Re: [PATCH] imon_raw: respect DMA coherency
Date: Tue, 17 May 2022 11:45:13 +0100 [thread overview]
Message-ID: <YoN8uWKZ6n2r/ntD@gofer.mess.org> (raw)
In-Reply-To: <a9d957ce-4c20-bbb1-028f-73b4a905d0a8@suse.com>
On Tue, May 17, 2022 at 10:28:35AM +0200, Oliver Neukum wrote:
> sorry for being a bit obnoxious about this, but there is a slight issue.
Pointing out potential issues is the opposite of obnoxious :)
> This is the old code:
>
> static void imon_ir_data(struct imon *imon)
> {
> struct ir_raw_event rawir = {};
> u64 data = be64_to_cpu(imon->ir_buf);
> u8 packet_no = data & 0xff;
> int offset = 40;
> int bit;
>
> if (packet_no == 0xff)
> return;
>
> dev_dbg(imon->dev, "data: %*ph", 8, &imon->ir_buf);
That should be imon->ir_buf (not &imon->ir_buf) after your changes.
> The dev_dbg() logs the data as it is in the buffer. If you use
> be64_to_cpup() instead of be64_to_cpu() you reverse
> the buffer on a little endian CPU and hence the debug
> output will be changed.
I'm confused. be64_to_cpup() does not do an in-place byte swap on little
endian.
I've just tested and the debug message still works fine (barring the issue
above).
> The actual driver code is unaffected, because the
> buffer is never used again, so this is not a big deal.
>
> The error is mine by changing the type of imon->ir_buf
> But the fix is not quite the best.
Your change is good.
Sean
prev parent reply other threads:[~2022-05-17 10:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 13:03 [PATCH] imon_raw: respect DMA coherency Oliver Neukum
2022-05-12 17:59 ` kernel test robot
2022-05-12 19:02 ` kernel test robot
2022-05-13 4:40 ` kernel test robot
2022-05-13 16:23 ` Sean Young
2022-05-16 11:00 ` Oliver Neukum
2022-05-16 16:40 ` Sean Young
2022-05-17 7:34 ` Oliver Neukum
2022-05-17 7:42 ` Sean Young
2022-05-17 8:28 ` Oliver Neukum
2022-05-17 10:45 ` Sean Young [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=YoN8uWKZ6n2r/ntD@gofer.mess.org \
--to=sean@mess.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=oneukum@suse.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