From: b29396@freescale.com (Dong Aisheng)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 2/3] can: m_can: update to support CAN FD features
Date: Tue, 18 Nov 2014 19:22:03 +0800 [thread overview]
Message-ID: <20141118112201.GA28032@shlinux1.ap.freescale.net> (raw)
In-Reply-To: <5465CA47.4020802@pengutronix.de>
On Fri, Nov 14, 2014 at 10:24:23AM +0100, Marc Kleine-Budde wrote:
> On 11/13/2014 05:56 PM, Oliver Hartkopp wrote:
> > On 11/13/2014 11:10 AM, Marc Kleine-Budde wrote:
> >> On 11/07/2014 09:45 AM, Dong Aisheng wrote:
> >
> >>>
> >>> - if (id & RX_BUF_RTR) {
> >>> + if (id & RX_BUF_ESI) {
> >>> + cf->flags |= CANFD_ESI;
> >>> + netdev_dbg(dev, "ESI Error\n");
> >>> + }
> >>> +
> >>> + if (!(dlc & RX_BUF_EDL) && (id & RX_BUF_RTR)) {
> >>> cf->can_id |= CAN_RTR_FLAG;
> >>
> >> I just noticed, that you don't set the cf->dlc (or cf->len) in the RTR
> >> case. Please create a separate patch that fixes this problem.
> >>
> >>> } else {
> >>> id = m_can_fifo_read(priv, fgi, M_CAN_FIFO_DLC);
> >>> - cf->can_dlc = get_can_dlc((id >> 16) & 0x0F);
> >>> - *(u32 *)(cf->data + 0) = m_can_fifo_read(priv, fgi,
> >>> - M_CAN_FIFO_DATA(0));
> >>> - *(u32 *)(cf->data + 4) = m_can_fifo_read(priv, fgi,
> >>> - M_CAN_FIFO_DATA(1));
> >>> + if (dlc & RX_BUF_EDL)
> >>> + cf->len = can_dlc2len((id >> 16) & 0x0F);
> >>> + else
> >>> + cf->len = get_can_dlc((id >> 16) & 0x0F);
> >>> +
> >
> > Grr. I missed that one too :-(
> >
> > Thanks for catching it.
> >
> > As you committed patch 1 & 3 you expect a new single patch containing the
> > (fixed) content of this patch 2, right?
>
> No, please make it two patches:
>
> First the Bugfix: One setting the cf->dlc in the RTR case, too.
> Then the new feature: The other one adding CAN-FD support.
>
Thanks for finding this.
Will do a patch soon as you said.
Regards
Dong Aisheng
> 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 |
>
next prev parent reply other threads:[~2014-11-18 11:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 8:45 [PATCH V4 1/3] can: add can_is_canfd_skb() API Dong Aisheng
2014-11-07 8:45 ` [PATCH V4 2/3] can: m_can: update to support CAN FD features Dong Aisheng
2014-11-13 10:10 ` Marc Kleine-Budde
2014-11-13 16:56 ` Oliver Hartkopp
2014-11-14 9:24 ` Marc Kleine-Budde
2014-11-18 11:22 ` Dong Aisheng [this message]
2014-11-07 8:45 ` [PATCH V4 3/3] can: m_can: add missing message RAM initialization Dong Aisheng
2014-11-07 10:30 ` Marc Kleine-Budde
2014-11-07 10:21 ` Dong Aisheng
2014-11-07 11:53 ` Oliver Hartkopp
2014-11-13 10:04 ` [PATCH V4 1/3] can: add can_is_canfd_skb() API 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=20141118112201.GA28032@shlinux1.ap.freescale.net \
--to=b29396@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).