From: Dong Aisheng <b29396@freescale.com>
To: Varka Bhadram <varkabhadram@gmail.com>
Cc: linux-can@vger.kernel.org, wg@grandegger.com,
socketcan@hartkopp.net, mkl@pengutronix.de,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
mark.rutland@arm.com
Subject: Re: [PATCH v5 2/2] can: m_can: add Bosch M_CAN controller support
Date: Wed, 16 Jul 2014 18:38:54 +0800 [thread overview]
Message-ID: <20140716103852.GA20184@shlinux1.ap.freescale.net> (raw)
In-Reply-To: <53C64CB1.3050204@gmail.com>
On Wed, Jul 16, 2014 at 03:28:09PM +0530, Varka Bhadram wrote:
> On 07/16/2014 03:00 PM, Dong Aisheng wrote:
> >The patch adds the basic CAN TX/RX function support for Bosch M_CAN controller.
> >For TX, only one dedicated tx buffer is used for sending data.
> >For RX, RXFIFO 0 is used for receiving data to avoid overflow.
> >Rx FIFO 1 and Rx Buffers are not used currently, as well as Tx Event FIFO.
> >
> >Due to the message ram can be shared by multi m_can instances
> >and the fifo element is configurable which is SoC dependant,
> >the design is to parse the message ram related configuration data from device
> >tree rather than hardcode define it in driver which can make the message
> >ram sharing fully transparent to M_CAN controller driver,
> >then we can gain better driver maintainability and future features upgrade.
> >
> >M_CAN also supports CANFD protocol features like data payload up to 64 bytes
> >and bitrate switch at runtime, however, this patch still does not add the
> >support for these features.
> >
> >Cc: Wolfgang Grandegger <wg@grandegger.com>
> >Cc: Marc Kleine-Budde <mkl@pengutronix.de>
> >Cc: Mark Rutland <mark.rutland@arm.com>
> >Cc: Oliver Hartkopp <socketcan@hartkopp.net>
> >Cc: Varka Bhadram <varkabhadram@gmail.com>
> >Signed-off-by: Dong Aisheng <b29396@freescale.com>
> >---
> >changes since v4:
> >some minor changes:
> >- introduce m_can_fifo_write and is_lec_err functin
> >- define macro M_CAN_FIFO_XXX for FIFO
> >- move m_can_of_table before platform_driver
> >- a few indent fix
> >
> >Changes since v3:
> >A few minor changes:
> >- use the updated name of bosch,mram-cfg
> >- remove .owner = THIS_MODULE
> >- add a line comment for mram_cfg structure
> >
> >Changes since v2:
> >- fix checkpatch warnings
> >- handle CAN_CTRLMODE_BERR_REPORTING properly that disable LEC error
> > interrupts (Bus error) if no CAN_CTRLMODE_BERR_REPORTING.
> >- introduce struct mram_cfg array to store message ram configuration data
> > for each fifo
> >- fix txb offset calculate wrong issue(should not plus mram_off again)
> >- check return for clk_prepare_enable
> >- split doc part into a separate patch
> >
> >Changes since v1:
> >Addressed all comments from Mark Rutland, Hartkopp and Marc Kleine-Budde
> >- merge three patches into one
> >- create directory drivers/net/can/m_can
> >- improve binding doc
> >- make sure using valid pointer before netif_receive_skb(skb)
> >- remove debug info a bit
> >- let the stats are updated even if alloc_can_err_skb() fails
> >- other small fixes
> >---
> > drivers/net/can/Kconfig | 2 +
> > drivers/net/can/Makefile | 1 +
> > drivers/net/can/m_can/Kconfig | 4 +
> > drivers/net/can/m_can/Makefile | 7 +
> > drivers/net/can/m_can/m_can.c | 1202 ++++++++++++++++++++++++++++++++++++++++
> > 5 files changed, 1216 insertions(+), 0 deletions(-)
> > create mode 100644 drivers/net/can/m_can/Kconfig
> > create mode 100644 drivers/net/can/m_can/Makefile
> > create mode 100644 drivers/net/can/m_can/m_can.c
> >
> >
> This series addressed all of my comments ...Thanks :-)
>
> Reviewed-by: Varka Bhadram <varkabhadram@gmail.com>
>
Thanks for the review! :-)
Regards
Dong Aisheng
> --
> Regards,
> Varka Bhadram.
>
next prev parent reply other threads:[~2014-07-16 10:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 9:30 [PATCH v5 1/2] can: m_can: add device tree binding documentation Dong Aisheng
2014-07-16 9:30 ` [PATCH v5 2/2] can: m_can: add Bosch M_CAN controller support Dong Aisheng
2014-07-16 9:58 ` Varka Bhadram
2014-07-16 10:38 ` Dong Aisheng [this message]
2014-07-16 10:05 ` [PATCH v5 1/2] can: m_can: add device tree binding documentation Marc Kleine-Budde
2014-07-16 10:40 ` Dong Aisheng
2014-07-25 11:53 ` Dong Aisheng
2014-07-30 11:52 ` Marc Kleine-Budde
2014-08-14 9:30 ` Dong Aisheng
2014-08-14 9:56 ` 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=20140716103852.GA20184@shlinux1.ap.freescale.net \
--to=b29396@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mkl@pengutronix.de \
--cc=socketcan@hartkopp.net \
--cc=varkabhadram@gmail.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).