From: Marek Vasut <marex@denx.de>
To: Heiko Schocher <hs@denx.de>, linux-can@vger.kernel.org
Cc: Markus Marb <markus@marb.org>,
netdev@vger.kernel.org, Marc Kleine-Budde <mkl@pengutronix.de>,
linux-kernel@vger.kernel.org,
Wolfgang Grandegger <wg@grandegger.com>
Subject: Re: [PATCH 2/2] net, can, ifi: loopback Tx message in IFI block
Date: Tue, 6 Feb 2018 13:50:21 +0100 [thread overview]
Message-ID: <0b802cb7-c972-a0fe-dde9-24cb399ccb95@denx.de> (raw)
In-Reply-To: <20180206120235.15167-2-hs@denx.de>
On 02/06/2018 01:02 PM, Heiko Schocher wrote:
> Current ifi driver reads first Rx messages, than loopback
> the Tx message, if the IFI_CANFD_INTERRUPT_TXFIFO_REMOVE
> bit is set. This can lead into the case, that Rx messages
> overhelm Tx messages!
>
> Fixed this in the following way:
>
> Set in the IFI_CANFD_TXFIFO_DLC register the FN value to
> 1, so the IFI block loopsback itself the Tx message when
> sended correctly on the canfd bus. Only the IFI block can
> insert the Tx message in the correct place.
>
> The linux driver now needs only to free the skb, when
> the Tx message was sended correctly.
>
> Signed-off-by: Heiko Schocher <hs@denx.de>
> ---
>
> drivers/net/can/ifi_canfd/ifi_canfd.c | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/can/ifi_canfd/ifi_canfd.c b/drivers/net/can/ifi_canfd/ifi_canfd.c
> index 05feb8177936..0d36cb8659ae 100644
> --- a/drivers/net/can/ifi_canfd/ifi_canfd.c
> +++ b/drivers/net/can/ifi_canfd/ifi_canfd.c
> @@ -211,6 +211,7 @@ struct ifi_canfd_priv {
> struct napi_struct napi;
> struct net_device *ndev;
> void __iomem *base;
> + unsigned int tx_len;
> };
>
> static void ifi_canfd_irq_enable(struct net_device *ndev, bool enable)
> @@ -617,8 +618,10 @@ static irqreturn_t ifi_canfd_isr(int irq, void *dev_id)
>
> /* TX IRQ */
> if (isr & IFI_CANFD_INTERRUPT_TXFIFO_REMOVE) {
> - stats->tx_bytes += can_get_echo_skb(ndev, 0);
> + can_free_echo_skb(ndev, 0);
> + stats->tx_bytes += priv->tx_len;
> stats->tx_packets++;
> + priv->tx_len = 0;
> can_led_event(ndev, CAN_LED_EVENT_TX);
> }
>
> @@ -889,6 +892,7 @@ static netdev_tx_t ifi_canfd_start_xmit(struct sk_buff *skb,
> }
>
> txdlc = can_len2dlc(cf->len);
> + priv->tx_len = txdlc;
> if ((priv->can.ctrlmode & CAN_CTRLMODE_FD) && can_is_canfd_skb(skb)) {
> txdlc |= IFI_CANFD_TXFIFO_DLC_EDL;
> if (cf->flags & CANFD_BRS)
> @@ -898,6 +902,12 @@ static netdev_tx_t ifi_canfd_start_xmit(struct sk_buff *skb,
> if (cf->can_id & CAN_RTR_FLAG)
> txdlc |= IFI_CANFD_TXFIFO_DLC_RTR;
>
> + /*
> + * set FNR to 1, so we get our Tx Message looped back
> + * into RxFIFO
> + */
Nit, you can make this into a single-line comment ;-)
Otherwise,
Reviewed-by: Marek Vasut <marex@denx.de>
> + txdlc += (1 << IFI_CANFD_TXFIFO_DLC_FNR_OFFSET);
> +
> /* message ram configuration */
> writel(txid, priv->base + IFI_CANFD_TXFIFO_ID);
> writel(txdlc, priv->base + IFI_CANFD_TXFIFO_DLC);
>
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2018-02-06 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 12:02 [PATCH 1/2] net, can, ifi: fix "write buffer full" error Heiko Schocher
2018-02-06 12:02 ` [PATCH 2/2] net, can, ifi: loopback Tx message in IFI block Heiko Schocher
2018-02-06 12:50 ` Marek Vasut [this message]
2018-02-06 12:48 ` [PATCH 1/2] net, can, ifi: fix "write buffer full" error Marek Vasut
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=0b802cb7-c972-a0fe-dde9-24cb399ccb95@denx.de \
--to=marex@denx.de \
--cc=hs@denx.de \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@marb.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--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®