From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
linux-can@vger.kernel.org, Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Robert Nawrath <mbro1689@gmail.com>
Subject: Re: [RFC PATCH 00/14] can: netlink: add CAN XL
Date: Mon, 11 Nov 2024 16:32:51 +0100 [thread overview]
Message-ID: <23c914cf-0af2-4619-9f83-e4b6339ef65f@hartkopp.net> (raw)
In-Reply-To: <a9d8eb65-c88d-4bc9-b0c2-c0e0799ea5bd@wanadoo.fr>
On 11.11.24 16:17, Vincent Mailhol wrote:
> On 11/11/2024 at 23:08, Oliver Hartkopp wrote:
>> Hello Vincent!
>>
>> Very impressive! Thanks for the effort.
>> Together with the example in the dummyxl driver it should become quite
>> easy to integrate the netlink API into my XCANB driver hack for testing.
>>
>> Picking up the dummyxl driver I wonder if it would make sense to
>> mainline this driver probably as can_nltest driver?!?
>> Of course this driver should be disabled or combined with some kernel
>> testing Kconfig stuff. But is it a great testing tool.
>
> Thanks. I do not recall similar things in the netdev subtree. I wonder
> what would be the idiomatic way to introduce such netlink test driver.
>
> @Marc, any thoughts on this?
>
>> From what I can see with the bitrate and tdc configurations the
>> extension for CAN XL is ok.
>>
>> If you take a look at this manual
>>
>> https://github.com/linux-can/can-doc/blob/master/x_can/
>> xcan_user_manual_v350.pdf
>>
>> on page 268/304 you will find the PWM configuration which consists of
>> three values with 6 bits each. I assume this to be similar in all CAN
>> XL controllers.
>>
>> The PWM feature switches the physical layer for a CAN XL transceiver
>> in the CAN XL data phase. This is a weird feature to do some PWM on
>> the controllers' TX data pin to be able to switch the physical layer
>> while maintaining the CAN transceiver package with 8 pin layout.
>>
>> Additionally to this PWM configuration register, the PWM CAN XL
>> transceiver switch feature has to be enabled similar to the way we
>> enable 'fd on' or 'xl on' today.
>>
>> You can see this bit called XLTR in the Operating Mode section on page
>> 269/304 and 270/304 .
>>
>> E.g. that might be named 'xltrx [on|off]' (default off)
> Thanks for the information and the link to the documentation. I will
> also try to see what ISO 11898-1:2024 has to say on the topic. Just be
> patient on this and do not worry if I give no signal for a couple weeks.
No problem! I will give some feedback when I managed to integrate the
extended netlink API to my driver.
Maybe Robert also gets his hands on this, so that we can continue to
discuss things even when you are busy for some time.
Best regards,
Oliver
next prev parent reply other threads:[~2024-11-11 15:33 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-10 15:55 [RFC PATCH 00/14] can: netlink: add CAN XL Vincent Mailhol
2024-11-10 15:55 ` [RFC PATCH 01/14] can: dev: add struct data_bittiming_params to group FD parameters Vincent Mailhol
2024-11-10 15:55 ` [RFC PATCH 02/14] can: netlink: replace tabulation by space in assignement Vincent Mailhol
2024-11-10 15:55 ` [RFC PATCH 03/14] can: bittiming: rename CAN_CTRLMODE_TDC_MASK into CAN_CTRLMODE_FD_TDC_MASK Vincent Mailhol
2024-11-10 15:55 ` [RFC PATCH 04/14] can: bittiming: rename can_tdc_is_enabled() into can_fd_tdc_is_enabled() Vincent Mailhol
2024-11-10 15:55 ` [RFC PATCH 05/14] can: netlink: can_changelink(): rename tdc_mask into fd_tdc_flag_provided Vincent Mailhol
2024-11-10 15:55 ` [RFC PATCH 06/14] can: netlink: make can_tdc_changelink() FD agnostic Vincent Mailhol
2024-11-10 15:55 ` [RFC PATCH 07/14] can: netlink: add can_dtb_changelink() Vincent Mailhol
2024-11-10 15:55 ` [RFC PATCH 08/14] can: netlink: add can_validate_tdc() Vincent Mailhol
2024-11-10 15:55 ` [RFC PATCH 09/14] can: netlink: make can_tdc_get_size() FD agnostic Vincent Mailhol
2024-11-10 15:55 ` [RFC PATCH 10/14] can: netlink: make can_tdc_fill_info() " Vincent Mailhol
2024-11-10 15:56 ` [RFC PATCH 11/14] can: netlink: document which symbols are FD specific Vincent Mailhol
2024-11-10 15:56 ` [RFC PATCH 12/14] can: netlink: add CAN XL support Vincent Mailhol
2024-11-12 8:09 ` Marc Kleine-Budde
2024-11-12 8:31 ` Vincent Mailhol
2024-11-12 8:41 ` Marc Kleine-Budde
2024-12-04 10:56 ` Oliver Hartkopp
2024-12-04 11:15 ` Marc Kleine-Budde
2024-12-04 11:35 ` Oliver Hartkopp
2024-12-04 11:44 ` Marc Kleine-Budde
2024-12-05 8:16 ` Oliver Hartkopp
2024-12-05 9:15 ` Marc Kleine-Budde
2024-12-09 13:13 ` Oliver Hartkopp
2024-12-10 11:58 ` Marc Kleine-Budde
2024-12-15 8:05 ` Vincent Mailhol
2024-11-10 15:56 ` [RFC PATCH 13/14] can: netlink: add userland error messages Vincent Mailhol
2024-11-10 15:56 ` [RFC PATCH 14/14] !!! DO NOT MERGE !!! can: add dummyxl driver Vincent Mailhol
2024-11-11 14:08 ` [RFC PATCH 00/14] can: netlink: add CAN XL Oliver Hartkopp
2024-11-11 15:17 ` Vincent Mailhol
2024-11-11 15:32 ` Oliver Hartkopp [this message]
2024-11-21 20:10 ` Oliver Hartkopp
2024-12-01 11:32 ` Oliver Hartkopp
2024-12-03 9:45 ` Vincent Mailhol
2024-12-04 7:56 ` Oliver Hartkopp
2024-12-15 9:21 ` Vincent Mailhol
2024-12-17 9:53 ` Oliver Hartkopp
2024-12-17 18:17 ` Vincent Mailhol
2024-12-17 20:03 ` Oliver Hartkopp
2024-12-18 9:13 ` Oliver Hartkopp
2025-01-30 5:42 ` Vincent Mailhol
2025-01-30 7:34 ` Marc Kleine-Budde
2024-11-12 8:53 ` Marc Kleine-Budde
2024-11-12 9:24 ` Vincent Mailhol
2024-11-12 10:12 ` 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=23c914cf-0af2-4619-9f83-e4b6339ef65f@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mbro1689@gmail.com \
--cc=mkl@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