Expected driver behavior on Frame not asked (and other errors)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: linux-can@xxxxxxxxxxxxxxx
Subject: Expected driver behavior on Frame not asked (and other errors)
From: kernel@xxxxxxxxxxxxxxxx
Date: Sun, 16 Dec 2018 12:30:59 +0100

Hi!

What is the expected behavior of a can controller driver in case
of the following detected situations?
* TX-NOACK?
* TX-BIT1 (CAN_ERR_PROT_BIT1)
* TX-BIT0 (CAN_ERR_PROT_BIT0)

Should these mean immediately a BUS off or similar?

Thanks,
	Martin

Follow-Ups:
- Re: Expected driver behavior on Frame not asked (and other errors)
  - From: Wolfgang Grandegger

Prev by Date: Re: [PATCH] dt-bindings: can: rcar_can: Add r8a774c0 support
Next by Date: [PATCH] can: m_can: fix overly indented if statement
Previous by thread: [PATCH] can: usb: Kconfig: Remove duplicate menu entry
Next by thread: Re: Expected driver behavior on Frame not asked (and other errors)
Index(es):
- Date
- Thread

[Index of Archives] [Automotive Discussions] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Security] [Bugtraq] [Linux] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API] [CAN Bus]

Powered by Linux