From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>,
Naga Sureshkumar Relli <naga.sureshkumar.relli@xilinx.com>,
linux-can <linux-can@vger.kernel.org>,
hsweeten@visionengravers.com
Subject: Re: xlinix_can: bug when sending two RTR frames
Date: Tue, 7 Feb 2023 22:04:22 +0100 [thread overview]
Message-ID: <20230207210422.qk5jdhgpvbkgtlfb@pengutronix.de> (raw)
In-Reply-To: <94e3c5bc-6af9-f240-86fa-2b780a58533f@hartkopp.net>
[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]
On 07.02.2023 21:45:20, Oliver Hartkopp wrote:
> Hi xilinx_can maintainers,
>
> Hartley Sweeten reported a bug when sending RTR frames with the xilinx_can
> driver here:
>
> https://github.com/linux-can/can-utils/issues/405#
>
> The problem: When sending a single RTR frame (e.g. with 'cansend can0
> 001#R') nothing happens.
>
> Only after sending a *second* RTR frame with 'cansend can0 001#R' the two
> (pending) RTR-frames are sent directly after each other.
>
> This faulty behavior of RTR frame sending is independent of the time gap
> between the two cansend attempts.
More info:
| Also, this is with a kernel/rootfs created using Petalinux 2020.2.
| Linux s6 5.4.0-xilinx-v2020.2 #1 SMP PREEMPT Fri Feb 3 17:27:45 UTC 2023 armv7l GNU/Linux
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-02-07 21:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 20:45 xlinix_can: bug when sending two RTR frames Oliver Hartkopp
2023-02-07 21:04 ` Marc Kleine-Budde [this message]
2023-02-09 17:53 ` Oliver Hartkopp
2023-02-16 11:18 ` Michal Simek
2023-02-16 15:34 ` Hartley Sweeten
2023-02-16 17:09 ` Oliver Hartkopp
2023-02-17 15:52 ` Hartley Sweeten
2023-02-21 10:53 ` Marc Kleine-Budde
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=20230207210422.qk5jdhgpvbkgtlfb@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=appana.durga.rao@xilinx.com \
--cc=hsweeten@visionengravers.com \
--cc=linux-can@vger.kernel.org \
--cc=naga.sureshkumar.relli@xilinx.com \
--cc=socketcan@hartkopp.net \
/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