From: Richard Weinberger <richard@sigma-star.at>
To: Andri Yngvason <andri.yngvason@marel.com>
Cc: linux-can@vger.kernel.org, mkl@pengutronix.de, wg@grandegger.com,
sigurbjorn.narfason@marel.com, hrafnkell.eiriksson@marel.com,
patric.thysell@br-automation.com
Subject: Re: [PATCH v2 1/3] can: cc770: Remove redundant IRQ ack
Date: Mon, 12 Feb 2018 20:41:48 +0100 [thread overview]
Message-ID: <2795059.IeN8S1rsHy@blindfold> (raw)
In-Reply-To: <20180130165649.22732-1-andri.yngvason@marel.com>
Andri,
Am Dienstag, 30. Januar 2018, 17:56:47 CET schrieb Andri Yngvason:
> This has been reported to cause stalls on rt-linux.
>
> Signed-off-by: Andri Yngvason <andri.yngvason@marel.com>
> ---
> drivers/net/can/cc770/cc770.c | 15 ---------------
> 1 file changed, 15 deletions(-)
>
> diff --git a/drivers/net/can/cc770/cc770.c b/drivers/net/can/cc770/cc770.c
> index 1e37313..9fed163 100644
> --- a/drivers/net/can/cc770/cc770.c
> +++ b/drivers/net/can/cc770/cc770.c
> @@ -447,15 +447,6 @@ static netdev_tx_t cc770_start_xmit(struct sk_buff
> *skb, struct net_device *dev)
>
> stats->tx_bytes += dlc;
>
> -
> - /*
> - * HM: We had some cases of repeated IRQs so make sure the
> - * INT is acknowledged I know it's already further up, but
> - * doing again fixed the issue
> - */
> - cc770_write_reg(priv, msgobj[mo].ctrl0,
> - MSGVAL_UNC | TXIE_UNC | RXIE_UNC | INTPND_RES);
> -
> return NETDEV_TX_OK;
> }
>
> @@ -684,12 +675,6 @@ static void cc770_tx_interrupt(struct net_device *dev,
> unsigned int o) /* Nothing more to send, switch off interrupts */
> cc770_write_reg(priv, msgobj[mo].ctrl0,
> MSGVAL_RES | TXIE_RES | RXIE_RES | INTPND_RES);
> - /*
> - * We had some cases of repeated IRQ so make sure the
> - * INT is acknowledged
> - */
> - cc770_write_reg(priv, msgobj[mo].ctrl0,
> - MSGVAL_UNC | TXIE_UNC | RXIE_UNC | INTPND_RES);
>
> stats->tx_packets++;
> can_get_echo_skb(dev, 0);
I saw that stalls too.
But instead of just removing these writes I suggest adding a quirk for the can
card where they cause trouble.
Maybe Wolfgang can give more details why they are here.
Thanks,
//richard
--
sigma star gmbh - Eduard-Bodem-Gasse 6 - 6020 Innsbruck - Austria
ATU66964118 - FN 374287y
next prev parent reply other threads:[~2018-02-12 19:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 16:56 [PATCH v2 1/3] can: cc770: Remove redundant IRQ ack Andri Yngvason
2018-01-30 16:56 ` [PATCH v2 2/3] can: cc770: Stop queue on NETDEV_TX_BUSY Andri Yngvason
2018-02-12 19:40 ` Richard Weinberger
2018-02-12 20:37 ` Wolfgang Grandegger
2018-02-12 20:44 ` Wolfgang Grandegger
2018-02-12 20:55 ` Richard Weinberger
2018-02-12 21:28 ` Wolfgang Grandegger
2018-02-12 21:36 ` Wolfgang Grandegger
2018-02-13 10:32 ` Andri Yngvason
2018-02-13 16:30 ` Wolfgang Grandegger
2018-02-16 14:22 ` Marc Kleine-Budde
2018-02-16 15:20 ` Wolfgang Grandegger
2018-01-30 16:56 ` [PATCH v2 3/3] can: cc770: Fix queue stall & dropped RTR reply Andri Yngvason
2018-02-12 19:45 ` Richard Weinberger
2018-02-12 19:41 ` Richard Weinberger [this message]
[not found] ` <151851733257.10946.11726494714017260046@maxwell>
2018-02-13 10:35 ` [PATCH v2 1/3] can: cc770: Remove redundant IRQ ack Richard Weinberger
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=2795059.IeN8S1rsHy@blindfold \
--to=richard@sigma-star.at \
--cc=andri.yngvason@marel.com \
--cc=hrafnkell.eiriksson@marel.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=patric.thysell@br-automation.com \
--cc=sigurbjorn.narfason@marel.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;
as well as URLs for NNTP newsgroup(s).