From: Marc Kleine-Budde <mkl@pengutronix.de>
To: AnilKumar Ch <anilkumar@ti.com>
Cc: wg@grandegger.com, linux-can@vger.kernel.org, anantgole@ti.com,
nsekhar@ti.com
Subject: Re: [PATCH 1/3] can: c_can: fix "BUG! echo_skb is occupied!" during transmit
Date: Tue, 24 Apr 2012 09:55:25 +0200 [thread overview]
Message-ID: <4F965C6D.6030303@pengutronix.de> (raw)
In-Reply-To: <1334915862-29810-1-git-send-email-anilkumar@ti.com>
[-- Attachment #1: Type: text/plain, Size: 2949 bytes --]
On 04/20/2012 11:57 AM, AnilKumar Ch wrote:
> This patch fixes an issue with transmit routine, which causes
> "can_put_echo_skb: BUG! echo_skb is occupied!" messgae when
> using "cansequence -p" on D_CAN controller.
>
> In c_can driver, while transmitting packets tx_echo flag holds
> the no of can frames put for transmission into the hardware.
>
> As the comment above c_can_do_tx() indicates, if we find any packet
> which is not transmitted then we should stop looking for more.
> In the current implementation this is not taken care of causing the
> said message.
>
> Also, fix the condition used to find if the packet is transmitted
> or not. Current code skips the first tx message object and ends up
> checking one extra invalid object.
The two above listed issues can occur with the c_can hardware, too?
Please split into two separate patches. These should go to the stable
kernel, too. Can someone with a c_can hardware test these patches.
> While at it, fix the comment on top of c_can_do_tx() to use the
> terminology "packet" instead of "package" since it is more
> standard.
Add this to one of the above patches.
> Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
> ---
> drivers/net/can/c_can/c_can.c | 6 ++++--
> 1 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/can/c_can/c_can.c b/drivers/net/can/c_can/c_can.c
> index 536bda0..9ac28df 100644
> --- a/drivers/net/can/c_can/c_can.c
> +++ b/drivers/net/can/c_can/c_can.c
> @@ -686,7 +686,7 @@ static int c_can_get_berr_counter(const struct net_device *dev,
> *
> * We iterate from priv->tx_echo to priv->tx_next and check if the
> * packet has been transmitted, echo it back to the CAN framework.
> - * If we discover a not yet transmitted package, stop looking for more.
> + * If we discover a not yet transmitted packet, stop looking for more.
> */
> static void c_can_do_tx(struct net_device *dev)
> {
> @@ -698,7 +698,7 @@ static void c_can_do_tx(struct net_device *dev)
> for (/* nix */; (priv->tx_next - priv->tx_echo) > 0; priv->tx_echo++) {
> msg_obj_no = get_tx_echo_msg_obj(priv);
> val = c_can_read_reg32(priv, &priv->regs->txrqst1);
> - if (!(val & (1 << msg_obj_no))) {
> + if (!(val & (1 << (msg_obj_no - 1)))) {
> can_get_echo_skb(dev,
> msg_obj_no - C_CAN_MSG_OBJ_TX_FIRST);
> stats->tx_bytes += priv->read_reg(priv,
> @@ -706,6 +706,8 @@ static void c_can_do_tx(struct net_device *dev)
> & IF_MCONT_DLC_MASK;
> stats->tx_packets++;
> c_can_inval_msg_object(dev, 0, msg_obj_no);
> + } else {
> + break;
> }
> }
>
regards, Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-04-24 7:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 9:57 [PATCH 1/3] can: c_can: fix "BUG! echo_skb is occupied!" during transmit AnilKumar Ch
2012-04-24 7:55 ` Marc Kleine-Budde [this message]
2012-04-24 11:24 ` AnilKumar, Chimata
2012-04-24 11:28 ` Marc Kleine-Budde
2012-04-24 11:53 ` AnilKumar, Chimata
2012-04-24 13:11 ` 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=4F965C6D.6030303@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=anantgole@ti.com \
--cc=anilkumar@ti.com \
--cc=linux-can@vger.kernel.org \
--cc=nsekhar@ti.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