From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Vivek Yadav <vivek.2311@samsung.com>
Cc: rcsekar@samsung.com, wg@grandegger.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
pankaj.dubey@samsung.com, ravi.patel@samsung.com,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] can: mcan: Add support for handling DLEC error on CAN FD
Date: Fri, 14 Oct 2022 09:11:14 +0200 [thread overview]
Message-ID: <20221014071114.a6ls5ay56xk4cin3@pengutronix.de> (raw)
In-Reply-To: <20221014050332.45045-1-vivek.2311@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 2484 bytes --]
On 14.10.2022 10:33:32, Vivek Yadav wrote:
> When a frame in CAN FD format has reached the data phase, the next
> CAN event (error or valid frame) will be shown in DLEC.
>
> Utilizes the dedicated flag (Data Phase Last Error Code: DLEC flag) to
> determine the type of last error that occurred in the data phase
> of a CAN FD frame and handle the bus errors.
>
> Signed-off-by: Vivek Yadav <vivek.2311@samsung.com>
> ---
> This patch is dependent on following patch from Marc:
> [1]: https://lore.kernel.org/all/20221012074205.691384-1-mkl@pengutronix.de/
>
> drivers/net/can/m_can/m_can.c | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/can/m_can/m_can.c b/drivers/net/can/m_can/m_can.c
> index 18a138fdfa66..8cff1f274aab 100644
> --- a/drivers/net/can/m_can/m_can.c
> +++ b/drivers/net/can/m_can/m_can.c
> @@ -156,6 +156,7 @@ enum m_can_reg {
> #define PSR_EW BIT(6)
> #define PSR_EP BIT(5)
> #define PSR_LEC_MASK GENMASK(2, 0)
> +#define PSR_DLEC_MASK GENMASK(8, 10)
>
> /* Interrupt Register (IR) */
> #define IR_ALL_INT 0xffffffff
> @@ -876,8 +877,16 @@ static int m_can_handle_bus_errors(struct net_device *dev, u32 irqstatus,
> if (cdev->can.ctrlmode & CAN_CTRLMODE_BERR_REPORTING) {
> u8 lec = FIELD_GET(PSR_LEC_MASK, psr);
>
> - if (is_lec_err(lec))
> + if (is_lec_err(lec)) {
> work_done += m_can_handle_lec_err(dev, lec);
> + } else {
In case of high interrupt latency there might be lec and dlec errors
pending. As this is error handling and not the hot path, please check
for both, i.e.:
if (is_lec_err(lec))
work_done += m_can_handle_lec_err(dev, lec);
if (is_lec_err(dlec))
work_done += m_can_handle_lec_err(dev, dlec);
> + u8 dlec = FIELD_GET(PSR_DLEC_MASK, psr);
> +
> + if (is_lec_err(dlec)) {
> + netdev_dbg(dev, "Data phase error detected\n");
If you add a debug, please add one for the Arbitration phase, too.
> + work_done += m_can_handle_lec_err(dev, dlec);
> + }
> + }
> }
>
> /* handle protocol errors in arbitration phase */
regards,
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:[~2022-10-14 7:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20221014053017epcas5p359d337008999640fa140c691f47bc79c@epcas5p3.samsung.com>
2022-10-14 5:03 ` Vivek Yadav
2022-10-14 7:11 ` Marc Kleine-Budde [this message]
2022-10-14 11:23 ` Vivek Yadav
2022-10-14 11:36 ` 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=20221014071114.a6ls5ay56xk4cin3@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pankaj.dubey@samsung.com \
--cc=ravi.patel@samsung.com \
--cc=rcsekar@samsung.com \
--cc=vivek.2311@samsung.com \
--cc=wg@grandegger.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
all inboxes | Powered by JetHome®