From: Michal Simek <michal.simek@amd.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>,
Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>,
Naga Sureshkumar Relli <naga.sureshkumar.relli@xilinx.com>,
linux-can <linux-can@vger.kernel.org>,
Michal Simek <michal.simek@xilinx.com>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>, <hsweeten@visionengravers.com>
Subject: Re: xlinix_can: bug when sending two RTR frames
Date: Thu, 16 Feb 2023 12:18:57 +0100 [thread overview]
Message-ID: <ea15524a-1ed9-0dbb-9511-c333a66a2555@amd.com> (raw)
In-Reply-To: <a2256c85-4253-dff5-fa8e-00fc02916095@hartkopp.net>
Hi,
On 2/9/23 18:53, Oliver Hartkopp wrote:
>
> + Michael Simek
>
> Missed Michael when checking the responsible people with
> scripts/get_maintainer.pl
>
> Best regards,
> Oliver
>
> On 2/7/23 21:45, 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.
I read that thread and I am missing details about Zynq board.
Are you using any custom zynq board or any xilinx standard evaluation board?
Can you please c&p dt fragment you use?
You are using 5.4 kernel which is quite old. Can you please switch to the latest
upstream or 5.15 xilinx?
Thanks,
Michal
next prev parent reply other threads:[~2023-02-16 11:19 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
2023-02-09 17:53 ` Oliver Hartkopp
2023-02-16 11:18 ` Michal Simek [this message]
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=ea15524a-1ed9-0dbb-9511-c333a66a2555@amd.com \
--to=michal.simek@amd.com \
--cc=appana.durga.rao@xilinx.com \
--cc=hsweeten@visionengravers.com \
--cc=linux-can@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=mkl@pengutronix.de \
--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